API Health Check 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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_api_healthA | Check if the GET localhost:8080/api/ticket endpoint is up or down |
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 between tools.
The single tool uses a clear snake_case naming convention, so no inconsistency exists.
A single tool that checks only one hardcoded endpoint is trivial for a health check server, which would typically need multiple endpoints or generic checks.
The tool surface is severely incomplete, as it only covers checking one specific endpoint, lacking support for other endpoints or dynamic health checks.