@mhdd_24/api-latency-mcp
by Mhdd-24
README.md
# @mhdd_24/api-latency-mcp
Analyze endpoint response times.
Same architecture as [@mhdd_24/sublime-mcp](https://github.com/Mhdd-24/Sublime-MCP).
**Full documentation:** [docs/WIKI.md](./docs/WIKI.md)
---
## How it works (30 seconds)
```
You (chat) → MCP client → api-latency-mcp → API Latency APIs / CLIs / local tools
```
---
## Prerequisites
| Requirement | Notes |
|-------------|--------|
| **Node.js 18+** | ESM TypeScript MCP server |
| **Credentials / CLIs** | See environment variables below |
---
## Install
### Option A — npm (after publish)
```bash
npm install -g @mhdd_24/api-latency-mcp
```
### Option B — npx
```bash
npx @mhdd_24/api-latency-mcp
```
### Option C — clone and build
```bash
git clone https://github.com/Mhdd-24/API-Latency-MCP.git
cd API-Latency-MCP
npm install
npm run build
node dist/index.js
```
---
## Configure Cursor
Edit `~/.cursor/mcp.json`:
```json
{
"mcpServers": {
"apilatency": {
"command": "npx",
"args": ["-y", "@mhdd_24/api-latency-mcp"],
"env": {
"PROJECT_ROOT": "..."
}
}
}
}
```
**Local development:**
```json
{
"command": "node",
"args": ["/absolute/path/to/API-Latency-MCP/dist/index.js"]
}
```
---
## Environment variables
| Variable | Description |
|----------|-------------|
| `PROJECT_ROOT` | Default project/repository root |
---
## Tools
| Tool | Description |
|------|-------------|
| `apilatency_status` | Health check for API Latency MCP. |
| `apilatency_probe` | Measure latency for a URL (N requests). |
| `apilatency_compare` | Compare latency of two URLs. |
---
## License
ISC
TDQS
B3.4/5.0
Scored across 3 tools
Disambiguation5/5
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.
Naming Consistency5/5
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.
Tool Count5/5
Three tools is well-scoped for a focused latency measurement server. Each tool serves a necessary purpose without unnecessary bloat.
Completeness4/5
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.
Maintenance
ActivityMaintained
ResponsivenessNo issues