MCP Hub Tools
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HUB_API_KEY | Yes | API key from MCP Hub (https://www.aimcp.info) required for authentication. Has rate limits of 20 requests per hour. |
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 |
|---|---|
| search_mcp_hubC | Search for MCPs on the MCP Hub |
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 ambiguity or overlap between tools, as there are no other tools to confuse it with. The tool's purpose is clearly defined and distinct by default.
The single tool name follows a consistent verb_noun pattern (search_mcp_hub), and with only one tool, there is no inconsistency to evaluate. The naming is clear and predictable.
One tool is too few for a server named 'MCP Hub Tools', which suggests a broader scope for managing or interacting with MCPs on the hub. A single search tool feels thin and incomplete for this apparent purpose.
The tool surface is severely incomplete for the inferred domain of MCP hub management. With only a search tool, there are obvious gaps such as installing, listing, updating, or removing MCPs, which are likely needed for full functionality.