Connect

8 clients · secrets stay placeholders

JSON (mcpServers)Claude CodeCodexOpenCodeCursorVS CodeGemini CLIGoose

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

claude mcp add --transport http current-state-resolver https://tovrek.com/mcp

[mcp_servers.current-state-resolver]
url = "https://tovrek.com/mcp"

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "current-state-resolver": {
      "type": "remote",
      "url": "https://tovrek.com/mcp",
      "enabled": true
    }
  }
}

{
  "mcpServers": {
    "current-state-resolver": {
      "type": "http",
      "url": "https://tovrek.com/mcp"
    }
  },
  "deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=current-state-resolver&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vdG92cmVrLmNvbS9tY3AifQ%3D%3D"
}

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

{
  "mcpServers": {
    "current-state-resolver": {
      "httpUrl": "https://tovrek.com/mcp"
    }
  }
}

extensions:
  "current-state-resolver":
    enabled: true
    name: "current-state-resolver"
    type: streamable_http
    uri: "https://tovrek.com/mcp"
    timeout: 300

Quality 86 / 100good

protocol88 · weight 25

pass
protocol.modernsupports 2026-07-28 (server/discover)
pass
protocol.statelessanswers without a session
pass
protocol.transportstreamable HTTP
warn
protocol.list_ttltools/list declares ttlMs 0, so clients re-fetch it on every use

authorizationn/a · weight 15

n/a
auth.prm, auth.as_metadata, auth.cimdno remote uses OAuth
n/a
auth.secret_in_urlno templated URL

tool hygiene79 · weight 30

pass
tools.descriptionsevery tool has a description
warn
tools.description_length1 tools have descriptions over 1,024 characters, which crowds the context
pass
tools.schemasevery tool has an object input schema
pass
tools.annotations1 of 1 tools declare readOnlyHint or destructiveHint
fail
tools.directory_hintsno tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: tovrek.resolve_current_state (destructiveHint, idempotentHint)
pass
tools.token_costabout 501 tokens to load every tool
pass
tools.api_dumptools are not a one-to-one API dump

stability100 · weight 15

pass
stability.changes4 tool changes in 30 days
pass
stability.rug_pullno tool changed its meaning under the same name

dependenciesn/a · weight 15

n/a
deps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI package

1 tools, about 501 tokens to load them all · tool set 81533e156627 · tools last changed 2026-10-09 · checked 2026-10-20 09:31 UTC

Tool changes

2026-10-09tovrek.resolve_current_statechangedoutput schema
2026-10-07tovrek.resolve_current_statechangeddescription, input schema, 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 · 71% of words in common
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-07tovrek.resolve_current_statechangedoutput schema, annotations
2026-10-06tovrek.resolve_current_statechangeddescription
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 · 62% of words in common
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: list_changes · trend: quality JSON.

Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.

Trust 96 / 100

provenance85

liveness100

freshness100

hygiene100

+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. How it is computed.

Endpoints

remote	auth	reachable	uptime 30d	p50	protocol	last ok
`https://tovrek.com/mcp` streamable-http	none	yes	100%	287 ms	2026-07-28	2026-10-20

Tools (1)

tovrek.resolve_current_stateread-only 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.

Schemas: list_tools.

Similar MCP servers

Official server.json

{
  "name": "com.tovrek/current-state-resolver",
  "title": "TOVREK Current-State Resolver",
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
  "remotes": [
    {
      "url": "https://tovrek.com/mcp",
      "type": "streamable-http"
    }
  ],
  "version": "0.1.0",
  "repository": {
    "url": "https://github.com/jekaterinavaivade-del/tovrek",
    "source": "github"
  },
  "websiteUrl": "https://tovrek.com/docs",
  "description": "Verify DOI metadata before autonomous action; preserve conflicts, provenance, and UNKNOWN."
}