mcpbeat Sign in

Retry-outcome resolution dedup proxy MCP Server

answering

Retry-outcome resolution dedup proxy is answering right now. Last checked 6 min ago. It exposes 4 tools.

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

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

Retry-outcome resolution dedup proxy does not always answer

Over the last week it answered 99.2% 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 6 min ago.

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

Available tools 4

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

dedup
dedup_execute
Claim-before-execute a side-effecting tool call: semantic-identity claim, CONFLICT refusal, UNKNOWN resolved by status query, ESCALATED refusal for no-status providers. $0.001/claim after the one-time 100-claim trial; included on Operator/Fleet plans.
dedup_receipt
Read your stored claim/receipt for a semantic identity (per-tenant scoped).
dedup_resolve
Manual status check closing an ESCALATED claim (committed verdict only).
guard
guard_census
Per-server guard census: SELF_GUARDED_VERIFIED only with a checkable status endpoint; invisible guards read NO_VISIBLE_GUARD.

Endpoints

URLTransportStateLatencyChecked
https://textforagents.com/products/retry-outcome-resolution-dedup-proxy/mcp streamable-http answering 322 ms 6 min ago

Alternatives to Retry-outcome resolution dedup proxy

same job, measured the same way
TOVREK Current-State Resolver
by tovrek

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

1 tools answering
MOVA MCP Connector
by mova-compact

Thin MOVA MCP proxy for bindings, transport resolution, and upstream tools/call execution.

local only
Public
by dsght

Read-only MCP access to DSGHT.ai published foresight and country-grounded claim resolution.

12 tools answering
Agentvet
by mukundakatta

Validate tool-call args before execution. Returns LLM-friendly retry hints.

15 installs/wk local only
Factum
by factum-project

Auditable memory for AI agents: provenance, cascade retraction, conflict refusal

local only
Safeagent
by azender1

Exactly-once execution guard for AI agents. Prevents duplicate payments and webhooks on retry.

220 installs/wk local only
Safeprompt
by safeprompt

Detect prompt injection, jailbreaks, and code injection in untrusted text before it reaches an LLM.

12 installs/wk local only
POSTFACT — Resolve Ambiguous Side Effects Before Retry
by gsterlingpress

Resolve whether an uncertain side-effecting action completed before software retries it.

1 tools answering

Retry-outcome resolution dedup proxy — questions

Answers built from our own checks of this server.

What can Retry-outcome resolution dedup proxy do?
It exposes 4 tools, read directly from the server on our last check. Among them: dedup_execute, dedup_receipt, dedup_resolve, guard_census. 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 Retry-outcome resolution dedup proxy 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 320 ms. The bar chart above shows every period we have measured.
How do I connect Retry-outcome resolution dedup proxy?
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 Retry-outcome resolution dedup proxy need an API key?
No. Retry-outcome resolution dedup proxy completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Retry-outcome resolution dedup proxy?
It answers our handshake in 320 ms on average, which is faster than 51% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.