Tool-Call Origin Attestation
Server Details
Dispatch-boundary attestation: prove a tool call was issued for its exact arguments.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2024-11-05
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 6 tools
attestation_check and verdict_lookup both return attestation-related judgements and their boundary rests only on differing input keys (execution/attestation vs framework/version/patch_state/surface), which an agent could easily conflate. dispatch and probe are distinguishable (execute vs test), but 'receipts' is vague enough to overlap with verdict/attestation outputs.
Names mix bare verbs (dispatch, probe), bare nouns (receipts), noun_verb (attestation_check), verb_noun (register_issuer), and noun_noun (verdict_lookup) with no predictable pattern. Each name is individually readable, but the set follows no single convention.
Six tools is a sensible, well-scoped size for an attestation service and none look redundant at the count level. The only bloat is descriptive noise (pricing text) rather than extra tools.
Core lifecycle is present (register issuer, issue/check attestation, dispatch, probe, look up verdict, inspect receipts), but issuer management is one-way: no list/revoke/rotate issuer operations, and bundle/fleet entities mentioned in billing have no tools. These gaps would force agents into dead ends for admin workflows.
Available Tools
6 toolsattestation_checkDInspect
Attestation check {execution, attestation} — $0.01 x402 / bundle / fleet included (same billing as HTTP)
Inputs: execution (required), attestation.
dispatchCInspect
PEP dispatch {execution, attestation} — executes ONLY on ATTESTED
Inputs: execution (required), attestation.
probeCInspect
Forged-shape probe suite {framework, version, patch_state, surface, target_url} — legs dispatched at the target; $4.99 / first free per operator ever (proven wallet required)
Inputs: surface (required), version (required), framework (required), patch_state (required), +3 more.
register_issuerCInspect
Register an issuer {issuer_id, issuer_class, public_key} — 409 on re-register
Inputs: issuer_id (required), public_key (required), issuer_class (required).
verdict_lookupDInspect
Verdict by {framework, version, patch_state, surface}
Inputs: surface (required), version (required), framework (required), patch_state (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
A witness layer for AI agent tool calls.
Bounded authorization and independently verifiable execution evidence for agents.
Post-quantum, tamper-evident receipts for agent actions. Ed25519 + ML-DSA-65, offline verify.
Hash-chained HMAC-signed audit log MCP for A2A (agent-to-agent) calls. Every tool-call, agent-ha...
Related MCP Servers
- AlicenseBqualityCmaintenancePrivacy-first, tamper-evident receipts for MCP tool calls. It hashes and signs arguments/results so you can verify what ran, when, without storing raw payloads.2MIT
- AlicenseBqualityBmaintenanceEnforces consensus-hardened tool approval with HMAC-signed receipts, policy gates, and host-bound argument checks for MCP clients.1228 npmMIT
- AlicenseNot gradedqualityBmaintenanceTamper-evident audit trail for AI agent tool calls. Cryptographically signed, hash-chained records that prove what your agents did.329 npmMIT

Affixio MCPofficial
AlicenseAqualityBmaintenanceEnables agents to locally attest actions and gate privileged tool calls with signed allow/deny decisions, using privacy-preserving hashing and offline ML-DSA-65 verification.318 npm1Apache 2.0
Glama MCP Gateway
Add one secure layer between your agents and this server.