Retry-outcome resolution dedup proxy

Name: Retry-outcome resolution dedup proxy
Author: com.textforagents

MCP serverMCP

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

by com.textforagentshomepage ↗v1.0.0

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"retry-outcome-resolution-dedup-proxy","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability10/10 checks ok

30 days ago

when	check	result	http	latency	detail
3 h ago	mcp initialize	ok	200	241 ms	server retry-outcome-resolution-dedup-proxy 1.0.0 · protocol 2025-03-26 · 4 tools
10 h ago	mcp initialize	ok	200	266 ms	server retry-outcome-resolution-dedup-proxy 1.0.0 · protocol 2025-03-26 · 4 tools
16 h ago	mcp initialize	ok	200	258 ms	server retry-outcome-resolution-dedup-proxy 1.0.0 · protocol 2025-03-26 · 4 tools
23 h ago	mcp initialize	ok	200	229 ms	server retry-outcome-resolution-dedup-proxy 1.0.0 · protocol 2025-03-26 · 4 tools
30 h ago	mcp initialize	ok	200	241 ms	server retry-outcome-resolution-dedup-proxy 1.0.0 · protocol 2025-03-26 · 4 tools
2 d ago	mcp initialize	ok	200	281 ms	server retry-outcome-resolution-dedup-proxy 1.0.0 · protocol 2025-03-26 · 4 tools
2 d ago	mcp initialize	ok	200	236 ms	server retry-outcome-resolution-dedup-proxy 1.0.0 · protocol 2025-03-26 · 4 tools
2 d ago	mcp initialize	ok	200	257 ms	server retry-outcome-resolution-dedup-proxy 1.0.0 · protocol 2025-03-26 · 4 tools
2 d ago	mcp initialize	ok	200	110 ms	server retry-outcome-resolution-dedup-proxy 1.0.0 · protocol 2025-03-26 · 4 tools
3 d ago	mcp initialize	ok	200	85 ms	server retry-outcome-resolution-dedup-proxy 1.0.0 · protocol 2025-03-26 · 4 tools

Tools observed via MCP handshake

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 pr
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_census — Per-server guard census: SELF_GUARDED_VERIFIED only with a checkable status endpoint; invisible guards read NO_VISIBLE_GUARD.

Declared by sources

What the publisher says

Attributed to the source that supplied each field. Treated as claims, not facts.

No long description beyond the summary.

kind Official MCP Registry

name Official MCP Registry

summary Official MCP Registry

version Official MCP Registry

description Official MCP Registry

homepageUrl Official MCP Registry

publisherName Official MCP Registry

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registrycom.textforagents/retry-outcome-resolution-dedup-proxy

first seen 3 d ago · fetched 3 d agoopen ↗

Field history (6 recent events)

3 d ago · declared · summary → "Dedup proxy: claim-before-execute, UNKNOWN resolution, CONFLICT and ESCALATED refusal."
3 d ago · declared · description → "Dedup proxy: claim-before-execute, UNKNOWN resolution, CONFLICT and ESCALATED refusal."
3 d ago · declared · publisherName → "com.textforagents"
3 d ago · declared · homepageUrl → "https://textforagents.com/products/retry-outcome-resolution-dedup-proxy/"
3 d ago · declared · version → "1.0.0"
3 d ago · declared · protocols → ["mcp"]

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from