@mhdd_24/api-latency-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 |
|---|---|
| apilatency_statusC | Health check for API Latency MCP. |
| apilatency_probeB | Measure latency for a URL (N requests). |
| apilatency_compareB | Compare latency of two 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 role: status checks service health, probe measures latency for one URL, compare contrasts two URLs. There is no meaningful overlap or ambiguity.
All tool names follow the same consistent pattern: apilatency_ prefix followed by a concise action word. This makes the tool set predictable and easy to navigate.
Three tools is well-scoped for a focused latency measurement server. Each tool serves a necessary purpose without unnecessary bloat.
The core latency workflow is covered: health check, single-target probing, and comparison. A minor gap might be batch/multi-URL analysis, but the current surface is reasonable for the stated purpose.