Agents Registry MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEBUG | No | Enable debug logging | false |
| AGENT_ORIGIN | Yes | Agent's domain or identifier (e.g., agent.example.com) | |
| AGENT_PUBKEY_ID | Yes | UUID of the registered public key in the Agents Registry | |
| REQUEST_TIMEOUT | No | Request timeout in ms | 30000 |
| REGISTRY_API_URL | No | Registry API URL | https://api.agents-registry.com |
| AGENT_PRIVATE_KEY | Yes | Ed25519 private key in base64 format (32 or 64 bytes) |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| agents_registry_whoamiA | Get information about this agent's identity, including origin, public key, and registered agent details |
| agents_registry_lookupB | Look up an agent by ID, domain, or search for agents by name/capabilities |
| agents_registry_verifyB | Verify that a message was signed by a specific agent. Can verify via the registry or locally with a known public key. |
| agents_registry_sendA | Send a signed message to another agent via the registry |
| agents_registry_inboxA | Fetch messages from this agent's inbox. Can filter by read status or conversation thread. |
| agents_registry_replyB | Reply to an existing message thread. The reply will be sent to the original sender. |
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 6 tools
Each tool serves a distinct purpose: inbox for receiving messages, lookup for finding agents, reply for responding to threads, send for initiating messages, verify for signature verification, and whoami for self-identity. No two tools overlap in functionality.
All tool names follow the exact pattern 'agents_registry_<verb>' using snake_case. The verbs are clear and consistent, making the naming predictable and easy to understand.
Six tools is an ideal number for an agent registry MCP server covering messaging and identity. Each tool is necessary and well-scoped, not too few or too many.
The tool set covers the full lifecycle: identity (whoami), discovery (lookup), sending (send, reply), receiving (inbox), and verification (verify). No obvious gaps for the intended domain.