Service Health MCP 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 |
|---|---|
| check_http_endpointA | Check if an HTTP/HTTPS endpoint is healthy and responsive. This tool will test connectivity, measure response time, and validate status codes. Perfect for monitoring APIs, websites, and web services. |
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 with other tools, making disambiguation perfect.
The single tool name follows a clear verb_noun pattern (check_http_endpoint), and with no other tools to compare, consistency is inherently perfect.
One tool is too few for a server named 'Service Health MCP Server', which suggests broader health monitoring capabilities beyond just HTTP endpoints, such as checking databases, servers, or other services.
The tool surface is severely incomplete for the implied domain of service health monitoring, as it only covers HTTP endpoints and lacks tools for other common health checks like database connectivity, server metrics, or network services.