QA Engineering MCP 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
} |
| logging | {} |
| prompts | {
"listChanged": true
} |
| resources | {
"subscribe": false,
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| hub_healthA | Return local server readiness; do not probe future providers. |
| hub_capabilitiesB | Return implemented and planned capabilities without overstating support. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| qa_hub_orientation | Orient a client to truthful QA Hub capability reporting. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| hub_status | Local Milestone 00 health and capability status. |
TDQS
Scored across 2 tools
hub_health (readiness/liveness) and hub_capabilities (feature inventory) are conceptually separable and the descriptions reinforce the split. They are still both metadata-only introspection calls, so an agent may occasionally grab one when it wanted the other.
Both tools use a clean, identical `hub_<noun>` snake_case pattern. There is no mixing of verbs, casing, or prefixes.
Two tools is very thin for something billed as a 'QA Engineering MCP Hub' — it is a stub surface rather than a scoped toolset. Both tools earn their place, but the count is far below what the stated purpose implies.
The surface covers only self-introspection; there are no QA-engineering operations at all (no test discovery, run, results, coverage, or reporting). An agent reaching for this hub for its advertised domain hits an immediate dead end.