mcp-registry-interface
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | No | GitHub personal access token for higher API rate limits (60 req/h without, 5000 with). Optional. |
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 |
|---|---|
| registry_search_serversA | Search for MCP servers from GitHub repositories and registries |
| registry_get_server_detailsB | Get detailed information about a specific MCP server |
| registry_list_categoriesA | List server categories from GitHub data |
| registry_refresh_dataA | Refresh server data from GitHub (bypasses cache) |
| helpA | Get comprehensive documentation for all registry-interface functions |
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 5 tools
Each tool has a clearly distinct purpose: searching, retrieving details, listing categories, refreshing data, and getting help. There is no overlap or ambiguity between them.
All tool names follow a consistent verb_noun pattern with lowercase and underscores (e.g., registry_search_servers, registry_get_server_details). 'help' is a minor deviation but is a conventional verb-like exception in many toolkits.
With exactly 5 tools, the set is well-scoped for a registry interface. Each tool covers a needed function without redundancy or bloat.
The core read and maintenance operations (search, get details, list categories, refresh) are all present. A list-all servers function could be considered missing, but search likely covers that use case adequately.