Health Check AI MCP vs Kortex
A side-by-side look at the Health Check AI MCP and Kortex MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
K
KortexMonitoringWhich x402 service actually works: uptime, valid 402, and settlements proven on-chain.12EmergingAuth: not declaredVerdict: choose Health Check AI MCP for monitoring work as a local process; choose Kortex for monitoring. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Health Check AI MCP when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | K Kortex | |
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 39/100 · Fair | 12/100 · Emerging |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | — |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Health Check AI MCP | View Kortex |
Tools & capabilities
Health Check AI MCP tools
No tool names declared yet. Check the project README from the listing page.
Kortex tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Health Check AI MCP
{
"mcpServers": {
"health-check-ai-mcp": {
"command": "npx",
"args": [
"-y",
"meok-setup"
]
}
}
}
Kortex
No confirmed install command for Kortex yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Health Check AI MCP is categorized under Monitoring and uses a local stdio subprocess. Kortex belongs to Monitoring and uses an install path we have not confirmed yet. Pick Health Check AI MCP for monitoring work and Kortex for monitoring.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Kortex has no confirmed install command yet — follow its own setup instructions.
Health Check AI MCP has no declared pricing — check the project's own site. Kortex has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add health-check-ai-mcp and kortex as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Health Check AI MCP has a quality signal of 39/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Kortex has 12/100 (Emerging) with 0 views, 0 installs and 0 GitHub stars.