# TOVREK Current-State Resolver

> Verify DOI metadata before autonomous action; preserve conflicts, provenance, and UNKNOWN.

- name: com.tovrek/current-state-resolver
- version: 0.1.0
- connection class: R0 (autonomous)
- trust: 96/100
- quality: 86/100 (good)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/com.tovrek%2Fcurrent-state-resolver
- tools: https://api.protogrid.dev/v1/servers/com.tovrek%2Fcurrent-state-resolver/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "current-state-resolver": {
      "type": "http",
      "url": "https://tovrek.com/mcp"
    }
  }
}
```


## Trust

- hygiene: 100
- liveness: 100
- freshness: 100
- provenance: 85
- drivers: +repository +dns-namespace +website +reachable +uptime-100% +updated-14d-ago
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 86/100 (good)

### protocol: 88 (weight 25)

- pass `protocol.modern`: supports 2026-07-28 (server/discover)
- pass `protocol.stateless`: answers without a session
- pass `protocol.transport`: streamable HTTP
- warn `protocol.list_ttl`: tools/list declares ttlMs 0, so clients re-fetch it on every use

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 79 (weight 30)

- pass `tools.descriptions`: every tool has a description
- warn `tools.description_length`: 1 tools have descriptions over 1,024 characters, which crowds the context
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 1 of 1 tools declare readOnlyHint or destructiveHint
- fail `tools.directory_hints`: no tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: tovrek.resolve_current_state (destructiveHint, idempotentHint)
- pass `tools.token_cost`: about 501 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 100 (weight 15)

- pass `stability.changes`: 4 tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 1, about 501 tokens to load them all
- tool set hash: 81533e156627ccdb4758dc3105eb1432
- tools last changed: 2026-10-09T08:59:41.297Z
- badge: [![protogrid quality](https://protogrid.dev/badge/com.tovrek/current-state-resolver.svg)](https://protogrid.dev/servers/com.tovrek/current-state-resolver)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

- 2026-10-09 `tovrek.resolve_current_state` changed (outputSchema)
- 2026-10-07 `tovrek.resolve_current_state` changed (description, inputSchema, annotations)
  - before: Pre-action evidence gate for supported Crossref DOI metadata: determine what the currently available evidence supports before an autonomous system cites, stores, publishes, ingests, or otherwise acts, while preserving provenance, conflicts, unresolved evidence, and explicit UNKNOWN. Use when a downstream action depends on a supported Crossref DOI metadata fact and the record may be stale, incomplete, conflicting, or insufficient; when current publication status or another supported metadata predicate must be checked before action; or when provenance and explicit UNKNOWN handling matter. Do not use when raw DOI metadata lookup alone is sufficient, or to establish scientific truth, claim validity, legal or regulatory authority, open-ended literature search, historical reconstruction, unsupported identifier families, general fact verification, or mutation.
  - after: Pre-action evidence gate for Crossref records whose record type is standard: determine what the currently available technical/industry-standard DOI metadata supports before an autonomous system cites, stores, publishes, ingests, or otherwise acts, while preserving provenance, conflicts, unresolved evidence, and explicit UNKNOWN. Use when a downstream action depends on a supported metadata fact for a Crossref standard-type DOI record and the record may be stale, incomplete, conflicting, or insufficient; when publication status, supersession, revision, adoption, approval date, designator, standards-body metadata, title, DOI, edition, or metadata surface must be checked before action; or when provenance and explicit UNKNOWN handling matter. Do not use for ordinary journal articles, citation validation, retraction checking, scholarly literature verification, or general multi-provider DOI resolution. Also do not use when raw Crossref metadata alone is sufficient, or to establish scientific truth, claim validity, legal or regulatory authority, open-ended literature search, historical reconstruction, unsupported identifier families, general fact verification, or mutation.
- 2026-10-07 `tovrek.resolve_current_state` changed (outputSchema, annotations)
- 2026-10-06 `tovrek.resolve_current_state` changed (description)
  - before: Verify the evidence-supported current state of supported DOI metadata before an autonomous system acts, preserving provenance, conflicts, unresolved evidence, and explicit UNKNOWN rather than treating one source as authoritative. Use before citing, storing, publishing, ingesting, or otherwise acting on a supported DOI when metadata may be stale, incomplete, or conflicting, when Crossref evidence may disagree with another available record, or when a downstream decision needs provenance and explicit UNKNOWN handling. Do not use when raw DOI metadata lookup alone is sufficient, or to establish scientific truth, claim validity, legal or regulatory authority, open-ended literature search, historical reconstruction, unsupported identifier families, general fact verification, or mutation.
  - after: Pre-action evidence gate for supported Crossref DOI metadata: determine what the currently available evidence supports before an autonomous system cites, stores, publishes, ingests, or otherwise acts, while preserving provenance, conflicts, unresolved evidence, and explicit UNKNOWN. Use when a downstream action depends on a supported Crossref DOI metadata fact and the record may be stale, incomplete, conflicting, or insufficient; when current publication status or another supported metadata predicate must be checked before action; or when provenance and explicit UNKNOWN handling matter. Do not use when raw DOI metadata lookup alone is sufficient, or to establish scientific truth, claim validity, legal or regulatory authority, open-ended literature search, historical reconstruction, unsupported identifier families, general fact verification, or mutation.

Full history: https://api.protogrid.dev/v1/servers/com.tovrek%2Fcurrent-state-resolver/changes

## Remotes

- https://tovrek.com/mcp (streamable-http, auth none, reachable true, uptime30d 1)

## Packages

_none_

## Tools (1)

- `tovrek.resolve_current_state`: Pre-action evidence gate for Crossref records whose record type is standard: determine what the currently available technical/industry-standard DOI metadata supports before an autonomous system cites, stores, publishes, ingests, or otherwise acts, while preserving provenance, conflicts, unresolved evidence, and explicit UNKNOWN. Use when a downstream action depends on a supported metadata fact for a Crossref standard-type DOI record and the record may be stale, incomplete, conflicting, or insufficient; when publication status, supersession, revision, adoption, approval date, designator, standards-body metadata, title, DOI, edition, or metadata surface must be checked before action; or when provenance and explicit UNKNOWN handling matter. Do not use for ordinary journal articles, citation validation, retraction checking, scholarly literature verification, or general multi-provider DOI resolution. Also do not use when raw Crossref metadata alone is sufficient, or to establish scientific truth, claim validity, legal or regulatory authority, open-ended literature search, historical reconstruction, unsupported identifier families, general fact verification, or mutation.