@mhdd_24/api-health-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PROJECT_ROOT | No | Default project/repository root |
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 |
|---|---|
| apihealth_statusB | Show API health defaults. |
| apihealth_checkB | HTTP health check for a URL. |
| apihealth_check_manyC | Check multiple URLs. |
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 3 tools
Each tool has a clearly distinct purpose: showing defaults, checking a single URL, and checking multiple URLs. There is no overlap in scope, so an agent can easily select the correct tool.
All tools follow the consistent 'apihealth_' prefix followed by a verb-like descriptor (status, check, check_many). The naming pattern is uniform and intuitive.
With 3 tools covering the core health-check operations, the count is well-scoped for the server's narrow purpose. It is neither sparse nor excessive.
The toolset covers checking one or multiple URLs and viewing defaults, which covers the primary workflow. A minor gap is the lack of a way to modify defaults, but this is not essential for typical health-check usage.