vantic-mcpofficial
A
licenseNot graded
qualityC
maintenanceEnables MCP hosts to verify agent spending mandates and receipts, providing stateless tools for authorization, chain verification, credential verification, and DID resolution.
Apache 2.0
@forestrie/mcp-resolve
by forestrie
Related Servers
Alternatives to @forestrie/mcp-resolve
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityAmaintenanceEnables querying and verifying signed receipts of static inspections of public agent skills via read-only tools such as search_receipts, get_receipt, and get_verification_material.1-
- AlicenseNot gradedqualityAmaintenanceEnables agents and users to query the Telegraph network through a hosted MCP endpoint, with tools to ask miners, request specific miners, retrieve intents/recipes, and verify signal hashes on-chain.MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to query cryptographically verified facts with zero-knowledge proofs, selective disclosure, and tamper-evident provenance.192 npm1Apache 2.0
smart-read-mcpofficial
AlicenseNot gradedqualityFmaintenanceProvides a universal read path for agents to extract facts, metadata, and provenance from local files and guarded remote URLs without using generative LLMs.MIT
corpus.333.ecoofficial
AlicenseNot gradedqualityBmaintenanceEnables agents to search, retrieve, and list open-licensed documents with verifiable provenance, attaching sha256, DOI, and OpenTimestamps proof to every response.1,986 npmCreative Commons Zero v1.0 Universal
TDQS
A4.1/5.0
Scored across 6 tools
Disambiguation4/5
Most tools target distinct resources: configuration, registration status, receipt, genesis, accumulator, and verification. The only overlap is fetch_receipt and verify_fetched_receipt, where the latter fetches and verifies the same receipt, but descriptions clarify the distinction.
Naming Consistency4/5
All names use lower snake_case with an action_entity pattern. The verbs vary (fetch, query, verify) appropriately, though fetch_ is used for four of six tools, making the pattern mostly predictable.
Tool Count5/5
Six tools is well-scoped for a resolver/verifier that fetches SCITT configuration, registration status, receipts, genesis, accumulators, and verifies receipts. Each tool has a clear, non-redundant role.
Completeness3/5
The surface covers core fetch and verify operations, but notable gaps exist for a transparency verifier: there is no tool to fetch checkpoints/signed tree heads, public keys (keyXy), or log entries by index. These are referenced as trust roots or verification inputs, so agents may hit dead ends.