DeepSeek Capability Hub
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| capability_hubA | Search and inspect a compact catalog, enable a trusted MCP only when needed, list its tools, proxy a tool call, or load one skill body. Shortest path: action "call" with name, tool and arguments starts the server by itself; use action "tools" (optionally with a query) first only when you do not know the tool name, and "enable" only to start one deliberately. Long results arrive in pages: continue with action "page" and the cursor printed on the last line. Avoid includeSchema unless you need the argument shape. Third-party proposals require human approval outside this MCP. Available capabilities — demo-echo (mcp): Bundled local MCP used to verify dynamic discovery, enable, tool listing, calls, and disable. | ml-experiment-review (skill): Review an ML experiment as a falsifiable, reproducible evidence package. |
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
There is only one tool, so there is no cross-tool misselection risk. However, capability_hub multiplexes many behaviors behind an action parameter, so the agent must distinguish search, enable, tools, call, page, and skill-loading modes internally.
There is a single tool named capability_hub, using consistent snake_case, and its action values appear to follow a simple lowercase convention. With only one exposed tool, naming consistency is inherently strong.
A one-tool gateway can be intentional for a capability hub that dynamically discovers and proxies other MCPs. Still, exposing all discovery, enablement, listing, invocation, paging, and skill loading through one polymorphic tool feels thin and pushes complexity into parameters.
The tool covers discovery, inspection, deliberate enablement, tool listing, proxied calls, pagination, and skill loading, which is broad lifecycle coverage for a hub. Minor gaps remain, such as no explicit disable action despite the demo-echo capability mentioning disable verification.