MCP2ANP Bridge Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ANP_TIMEOUT | No | HTTP request timeout in seconds | |
| ANP_LOG_LEVEL | No | Log level (DEBUG, INFO, WARNING, ERROR) | INFO |
| ANP_MAX_RETRIES | No | Maximum number of retries |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| anp.setAuthA | 设置 DID 认证上下文。使用本地 DID 文档和私钥文件建立认证,后续的 fetchDoc 和 invokeOpenRPC 调用将自动使用这些凭证。 |
| anp.fetchDocA | 抓取并解析 ANP 文档,提取可跟进的链接。这是访问 ANP 生态系统中 URL 的唯一允许方法。返回文档内容、类型信息和发现的链接。 |
| anp.invokeOpenRPCC | 使用 JSON-RPC 2.0 协议调用 OpenRPC 端点上的方法。此工具处理与暴露 OpenRPC 接口的 ANP 智能体的结构化交互。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
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.
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.
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.
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.