A
licenseNot graded
qualityD
maintenanceConnects MCP-powered AI agents to the decentralized Agent Network Protocol (ANP) for DID-based identity, agent discovery, and secure agent-to-agent communication.
MIT
MCP2ANP Bridge Server
Related Servers
Alternatives to MCP2ANP Bridge Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityFmaintenanceBridges Agent Communication Protocol (ACP) agents with Model Context Protocol (MCP) applications, allowing MCP clients such as Claude Desktop to discover and invoke ACP agents as tools and resources.36Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables Claude Desktop and other MCP clients to interact with any OAuth2-authenticated OpenAPI-based API through automatic tool generation from OpenAPI specifications, with built-in token management and authentication handling.6 npm3MIT
- AlicenseAqualityDmaintenanceProvides browser automation, audio transcription, and LLM chat as MCP tools for any agent.7MIT
- AlicenseNot gradedqualityDmaintenanceDynamically generates MCP tools from OpenAPI specifications, enabling AI assistants to interact with any REST API through natural language. Supports multiple APIs with authentication, parameter validation, and integration with Claude Desktop and LangChain.1MIT
- AlicenseBqualityFmaintenanceExposes OpenClaw tools (web search, page fetching, browser automation, PDF analysis, messaging, inter-agent communication, Canvas) as MCP tools for ACP agents.7-
TDQS
A3.7/5.0
Scored across 3 tools
Disambiguation5/5
Each tool has a clearly distinct purpose: fetchDoc retrieves and parses documents, invokeOpenRPC handles structured RPC calls, and setAuth manages authentication. There is no overlap in functionality, and the descriptions make their unique roles explicit.
Naming Consistency5/5
All tools follow a consistent 'anp.verbNoun' pattern (anp.fetchDoc, anp.invokeOpenRPC, anp.setAuth), using snake_case for multi-word names. This predictable naming scheme enhances readability and agent usability.
Tool Count4/5
With only 3 tools, the server feels slightly thin but reasonable for its bridging purpose. It covers core operations (fetch, invoke, auth) without bloat, though additional utilities might be expected in a bridge server. The count is appropriate but minimal.
Completeness4/5
The tools provide essential coverage for interacting with ANP ecosystems: fetching documents, invoking RPC methods, and setting authentication. Minor gaps might include tools for managing sessions or handling errors, but the core workflow is well-supported without dead ends.
Maintenance
ActivityInactive
ResponsivenessNo issues