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) |
Capabilities
Features and capabilities supported by this server
| 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 | |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/agents-registry-com/mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server