mcp-registry-server
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| retrieve_mcpsC | Performs retrieval from our registry of MCPs. |
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 1 tool
With only one tool, there is no possibility of confusion or overlap between tools. The single tool has a distinct and clear purpose, making disambiguation trivial.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'retrieve_mcps' follows a clear verb_noun pattern, but with no other tools to compare, it sets a consistent baseline.
A single tool for a registry server feels thin and likely insufficient for the domain. Typical registry operations might include search, list, get details, or update, but this server only offers retrieval, which is too limited for the apparent scope.
The tool surface is severely incomplete for a registry domain. Only retrieval is provided, with no capabilities for searching, listing, creating, updating, or deleting MCP entries, which are common operations for a registry, leading to significant gaps.