klanex is answering right now. Last checked 6 min ago. 24 installs a week from npm. It exposes 6 tools. Last commit 18 Sep 2026.
Reliable async execution for agent tool calls: schema gating, retries, idempotency, audit trail.
We read the source, 10 h ago · tools taken from the live server · rules 3dff92dd89df
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
# klx_test_ prefix routes to the sandbox endpoint; overridable at runtime. ENV KLANEX_API_KEY=klx_test_placeholder
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 6 min ago.
claude mcp add klanex --transport http https://api.klanexai.com/mcp
{
"mcpServers": {
"klanex": {
"url": "https://api.klanexai.com/mcp"
}
}
}
[mcp_servers.klanex]
url = "https://api.klanexai.com/mcp"
{
"mcpServers": {
"klanex": {
"url": "https://api.klanexai.com/mcp"
}
}
}
{
"mcpServers": {
"klanex": {
"url": "https://api.klanexai.com/mcp"
}
}
}
This one needs environment variables set before it will start:
KLANEX_API_KEY (klanex API key; klx_test_... keys route to the sandbox automatically).
The author declared them in the registry entry; get the values from the project itself.
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
list_connections
execute
get_execution
list_executions
replay_execution
get_usage
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://api.klanexai.com/mcp | streamable-http | answering | 236 ms | 6 min ago |
Pre-execution gate for AI-agent tool calls. Touch ID approval. Tamper-evident audit log.
Verifiable execution for AI agents: Ed25519-signed work contracts and audit trails.
Identity, authorization, audit trails, and revocable permissions for AI agents accessing MCP tools.
Immutable audit trail for agent-to-agent interactions
Market regime, execution-cost, bar-QC and backtest-audit tools for agents. Pay per call via x402.
Cross-session idempotency, URLs as schema-validated JSON, and a record of missing capabilities.
MCP-native router and multi-agent control plane: plan, route tool calls, stream execution.
Runtime permission, approval, and audit layer for AI agent tool execution.
Answers built from our own checks of this server.