Channel-bound delegation receipts
Server Details
Binds delegated results to their arrival channel: provenance grades plus a grounded truth tier.
- 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
cbdr_info and verify_receipt are reasonably distinct, but channel_verdict and grounded_verification carry nearly identical boilerplate descriptions ('Paid work: refused over MCP'), so an agent cannot tell what each actually does or when to choose one over the other. Their boundaries are unclear despite different names.
All names use snake_case, which is superficially consistent, but the patterns are mixed: cbdr_info is an acronym-prefixed noun, channel_verdict and grounded_verification are noun phrases, and only verify_receipt follows a verb_noun action pattern. Readable, but not a predictable scheme an agent can rely on.
Four tools is a plausible count for a niche receipts/verification server, but two of them (channel_verdict, grounded_verification) are explicitly non-operational over MCP, leaving only two usable tools. The effective surface is borderline thin.
There is no tool to issue, create, or consume a delegation receipt, and the two core paid operations (verdict, grounded verification) are refused over MCP, forcing agents off-protocol. verify_receipt inspects only the envelope without settling or consuming the nonce, so primary workflows cannot complete within MCP.
Available Tools
4 toolscbdr_infoBInspect
Prices, grading ranks, and tier-boundary wording (free, informational).
Inputs: no named parameters.
channel_verdictBInspect
Paid work: refused over MCP — payments collect on the HTTP x402 surface (POST /verdict).
Inputs: no named parameters.
grounded_verificationCInspect
Paid work: refused over MCP — payments collect on the HTTP x402 surface (POST /grounded).
Inputs: no named parameters.
verify_receiptBInspect
Receipt envelope inspection (signature/expiry/channel; does not consume the nonce, settles nothing).
Inputs: receipt.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
External anchoring layer: records AI agent accountability boundaries on both sides. Content-blind.
Route tasks by measured judgment quality: third-party-verified, Brier-based calibration records.
Grade MCP elicitation destinations against the approved set before consent.
Compiles source-agent outputs into validated, receiver-ready handoff packages.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables agents to classify every claim into evidence tiers (FACT/INFERENCE/SPECULATION/UNVERIFIED) with attached evidence, forcing deterministic, evidence-gated reporting without LLM or network calls.25 PyPIMIT
- AlicenseAqualityCmaintenanceAI agent provenance, trust, and auditability layer. VERITAS multi-gate scoring, Cortex approval gates, S.E.A.L. hash-chain audit ledger, and semantic RAG with cryptographic provenance tracking for every decision an agent makes.275MIT
- AlicenseNot gradedqualityBmaintenanceEnables agents to route one goal across multiple independent APIs, reject invalid or disagreeing evidence, and return a verified outcome with a tamper-evident receipt that can be independently checked.MIT
- FlicenseNot gradedqualityDmaintenanceEnables structured role-to-role handoffs and merge gating for multi-agent collaboration. It persists evidence and computes approval gates without invoking LLMs.-
Glama MCP Gateway
Add one secure layer between your agents and this server.