mcpbeat Sign in

TOVREK Current-State Resolver MCP Server

answering

TOVREK Current-State Resolver is answering right now. Last checked 14 min ago. It exposes 1 tools.

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

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 20 days of history · worst day 96%
20 days agonow
100.0%
Uptime 24h
91 of 91 checks
1
Tools
read from the server
273 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 2

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 7 October 2026. No other catalogue keeps this.

7 Oct a tool description was rewritten tovrek.resolve_current_state
7 Oct a tool changed the parameters it asks for tovrek.resolve_current_state

TOVREK Current-State Resolver does not always answer

Over the last week it answered 99.4% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.

run in your terminal
claude mcp add current-state-resolver --transport http https://tovrek.com/mcp
Settings → Connectors → Add custom connector, then paste this address
https://tovrek.com/mcp
~/.codex/config.toml
[mcp_servers.current-state-resolver]
url = "https://tovrek.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "current-state-resolver": {
      "url": "https://tovrek.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "current-state-resolver": {
      "type": "http",
      "url": "https://tovrek.com/mcp"
    }
  }
}

Available tools 1

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

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

Endpoints

URLTransportStateLatencyChecked
https://tovrek.com/mcp streamable-http answering 200 ms 14 min ago

Alternatives to TOVREK Current-State Resolver

same job, measured the same way
T
Trust Gate
by botagram

Merchant trust verification for agentic commerce. Verify any merchant before autonomous payment.

10 installs/wk local only
Retry-outcome resolution dedup proxy
by textforagents

Dedup proxy: claim-before-execute, UNKNOWN resolution, CONFLICT and ESCALATED refusal.

4 tools answering
XAPS MCP Server
by apmc1

Pre-execution audit for autonomous agents. Independent receipt before irreversible actions.

113 installs/wk local only
Merchant Context
by ihint

Resolve sourced merchant facts and safe actions before an agent acts.

9 tools answering
Behind the Watt
by ykorets

Verified behind-the-meter data center power, announcements, and provenance receipts.

4 tools answering
Rithmo
by rithmo

AI agent governance with resolved business context, current decisions, provenance, and supersession.

answering
Delta Witness
by 15998194110

Paid Capture and Guard tools for public-source observations before autonomous actions.

40 installs/wk local only
Remove AI Watermarks
by wiltodelta

Identify and remove AI watermarks and provenance metadata from your own images and video.

4 337 installs/wk local only

TOVREK Current-State Resolver — questions

Answers built from our own checks of this server.

What can TOVREK Current-State Resolver do?
It exposes 1 tools, read directly from the server on our last check. Among them: tovrek.resolve_current_state. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is TOVREK Current-State Resolver working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 273 ms. The bar chart above shows every period we have measured.
Is TOVREK Current-State Resolver still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect TOVREK Current-State Resolver?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does TOVREK Current-State Resolver need an API key?
No. TOVREK Current-State Resolver completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 1 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is TOVREK Current-State Resolver?
It answers our handshake in 273 ms on average, which is faster than 61% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.