A
licenseA
qualityD
maintenanceEnables AI agents to discover, register, and rate services in a decentralized agent-to-agent directory.
7
17 PyPI
MIT
verantis-mcp
Related Servers
Alternatives to verantis-mcp
No user-submitted related servers found.
Related Servers
Voidpay Marketplaceofficial
AlicenseNot gradedqualityAmaintenanceLets AI agents search a marketplace of agent services, read seller storefronts, and prepare a checkout link that a human owner approves and pays in their browser. The agent never holds keys or signs.1Apache 2.0- FlicenseNot gradedqualityAmaintenanceEnables agents to discover and verify paid agent services through x402 payment validation and release gate checks.-
- AlicenseNot gradedqualityDmaintenanceEnables agents to discover and pay for AI services per call via USDC on Solana, supporting marketplace search, listing details, on-chain reputation, wallet info, and paid calls.30 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP-compatible agents to discover and call x402 paid services from a directory of over 2,000 APIs.Apache 2.0
AgentBodega MCPofficial
AlicenseAqualityFmaintenanceEnables agents to search and inspect live service offerings, generate x402 payment snippets, and understand blockchain-only balance policies.440 npm3MIT
TDQS
A4/5.0
Scored across 4 tools
Disambiguation4/5
The four tools have distinct purposes: get_service retrieves a single service's unified record, find_paid_service searches the directory, directory_stats provides index-level statistics, and check_wallet is a pre-payment guard. There is slight overlap between get_service and find_paid_service (both return service records), but the descriptions clarify that one is for a specific host and the other is for search.
Naming Consistency4/5
Tool names follow a consistent verb_noun pattern: get_service, find_paid_service, directory_stats, check_wallet. The pattern is mostly consistent, though directory_stats uses a noun_noun structure rather than a verb_noun one, which is a minor deviation.
Tool Count4/5
With 4 tools, the server is well-scoped for its purpose of querying service reputation and wallet safety. The count is slightly on the lower end but each tool serves a distinct function, and the domain is narrow enough that 4 tools feel appropriate.
Completeness3/5
The tool surface covers the core workflows: searching services, getting detailed records, checking wallets, and viewing index stats. However, there are no tools for actions like registering a service, updating reputation, or managing verification, which could be gaps if the server is meant to support the full lifecycle. For a read-only query server, the coverage is adequate.
Maintenance
ActivitySlowing
ResponsivenessUnresponsive