mcp-registry
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_mcp_serversA | List MCP servers from the MCP Registry with pagination support. |
| search_mcp_serversB | Search for MCP servers by name or keywords. |
| get_mcp_serverA | Get detailed information about a specific MCP server by name. |
| get_server_versionsA | Get all available versions for a specific MCP server. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| health_check | Check the health status of the MCP Registry API. Returns: A dict with health status information. |
TDQS
Scored across 4 tools
Each tool has a distinct purpose: get details, get versions, list all, and search by keywords. No overlap in functionality.
All tools follow a consistent verb_noun pattern in snake_case (e.g., get_mcp_server, list_mcp_servers), making naming predictable.
With 4 tools covering listing, searching, details, and versions, the count is well-scoped for a registry query service.
The tool surface covers essential registry operations (list, search, get, versions) with no obvious gaps for the intended domain.