Kortex vs Health Check AI MCP
A side-by-side look at the Kortex and Health Check AI MCP 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 Kortex for monitoring work; choose Health Check AI MCP for monitoring as a local process. 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 | 12/100 · Emerging | 39/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| 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 | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Kortex | View Health Check AI MCP |
Tools & capabilities
Kortex tools
No tool names declared yet. Check the project README from the listing page.
Health Check AI MCP 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.
Kortex
No confirmed install command for Kortex yet — follow the setup steps linked from its listing page rather than a guessed package name.
Health Check AI MCP
{
"mcpServers": {
"health-check-ai-mcp": {
"command": "npx",
"args": [
"-y",
"meok-setup"
]
}
}
}
Frequently asked questions
Kortex is categorized under Monitoring and uses an install path we have not confirmed yet. Health Check AI MCP belongs to Monitoring and uses a local stdio subprocess. Pick Kortex for monitoring work and Health Check AI MCP 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.
Kortex has no declared pricing — check the project's own site. Health Check AI MCP 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 kortex and health-check-ai-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Kortex has a quality signal of 12/100 (Emerging) with 0 views, 0 installs and 0 GitHub stars. Health Check AI MCP has 39/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.