@mhdd_24/api-health-mcp
by Mhdd-24
README.md
# @mhdd_24/api-health-mcp
Endpoint availability and health checks.
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-health-mcp → API Health 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-health-mcp
```
### Option B — npx
```bash
npx @mhdd_24/api-health-mcp
```
### Option C — clone and build
```bash
git clone https://github.com/Mhdd-24/API-Health-MCP.git
cd API-Health-MCP
npm install
npm run build
node dist/index.js
```
---
## Configure Cursor
Edit `~/.cursor/mcp.json`:
```json
{
"mcpServers": {
"apihealth": {
"command": "npx",
"args": ["-y", "@mhdd_24/api-health-mcp"],
"env": {
"PROJECT_ROOT": "..."
}
}
}
}
```
**Local development:**
```json
{
"command": "node",
"args": ["/absolute/path/to/API-Health-MCP/dist/index.js"]
}
```
---
## Environment variables
| Variable | Description |
|----------|-------------|
| `PROJECT_ROOT` | Default project/repository root |
---
## Tools
| Tool | Description |
|------|-------------|
| `apihealth_status` | Show API health defaults. |
| `apihealth_check` | HTTP health check for a URL. |
| `apihealth_check_many` | Check multiple URLs. |
---
## License
ISC
TDQS
B3.3/5.0
Scored across 3 tools
Disambiguation5/5
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.
Naming Consistency5/5
All tools follow the consistent 'apihealth_' prefix followed by a verb-like descriptor (status, check, check_many). The naming pattern is uniform and intuitive.
Tool Count5/5
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.
Completeness4/5
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.
Maintenance
ActivityMaintained
ResponsivenessNo issues