Retry-outcome resolution dedup proxy
Server Details
Dedup proxy: claim-before-execute, UNKNOWN resolution, CONFLICT and ESCALATED refusal.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-03-26
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: dedup_execute claims and executes, dedup_receipt reads a stored claim/receipt, dedup_resolve closes an escalated claim, and guard_census reports guard status. There is no overlap in action or resource.
All tools use consistent snake_case with a domain prefix (dedup_ or guard_), but the suffixes mix verbs and nouns (execute, receipt, resolve, census), slightly deviating from a pure verb_noun pattern.
Four tools are well-scoped for this specialized dedup proxy, covering each core operation without redundancy or bloat.
The claim lifecycle (execute, read, resolve) and guard census are covered, but there is no tool to list or search multiple claims, which is a minor gap for operational visibility.
Available Tools
4 toolsdedup_executeBInspect
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.
Inputs: args (required), tool (required), scope_fields (required), provider_mode, +1 more.
dedup_receiptCInspect
Read your stored claim/receipt for a semantic identity (per-tenant scoped).
Inputs: args (required), tool (required), scope_fields (required).
dedup_resolveCInspect
Manual status check closing an ESCALATED claim (committed verdict only).
Inputs: args (required), tool (required), scope_fields (required).
guard_censusCInspect
Per-server guard census: SELF_GUARDED_VERIFIED only with a checkable status endpoint; invisible guards read NO_VISIBLE_GUARD.
Inputs: servers (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Personal-lock maintenance isolation for agent infrastructure: hasp-quorum refusal + try-start proof.
Evidence-linked MCP selection and non-executing Safe-Call review; surfaces unknowns.
Look before work, claim it, check a spend, mark the outcome. For agents sharing tasks. No key.
Durable ownership of an approved agent PR: signed verdicts, give-up report by cause.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceMCP server for governing agent actions: an agent can propose a retry but cannot approve it itself. Deterministic policy allows, holds or refuses each typed action, a held action needs a single-use human approval none of the tools can create, and every run leaves a verifiable receipt.1MIT
- AlicenseNot gradedqualityBmaintenanceGives AI coding agents a local, mechanical workflow authority: an agent's issue claim is recorded, every subsequent write and irreversible step (push, merge, tag, release) is re-verified against that record, and review verdicts are bound to exact commit bytes so a later push invalidates them. Refusals report what was read and what to do next, keeping an unreadable tracker distinct from a forbidden action.1MIT
- AlicenseBqualityBmaintenanceEnables coding agents to verify completion and current-state claims by classifying claims, requiring independent evidence/readback, resolving precedence conflicts, and blocking unsafe replays before reporting success.8MIT
- FlicenseAqualityBmaintenanceExactly-once execution for irreversible agent actions: an agent claims the right to run an effect, and a retry after a lost response returns the sealed result instead of charging again. 12 tools over stdio, including a gateway mode where the agent holds a single-use ticket and never the provider key.964 PyPI-
Glama MCP Gateway
Add one secure layer between your agents and this server.