klanex
io.github.chrassy/klanexVersion 0.1.0Reliable async execution for agent tool calls: schema gating, retries, idempotency, audit trail.
Status
Responds73 msAnswered our handshake without sign-in.- Last checked
- Nov 14, 2026, 14:47 UTC
- Latency
- 73 ms
- Remotes responding
- 1 of 1
- Sign-in
- API key
- Hosting
- Hosted outside the EU (detected)
- Registry data as of
- Nov 14, 2026, 21:12 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://api.klanexai.com/mcpResponds73 msNo sign-in
Claude Code
claude mcp add --transport http klanex https://api.klanexai.com/mcp --header 'X-API-Key: <YOUR_X_API_KEY>'Replace <YOUR_X_API_KEY> before running.
Claude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: klanex
Remote MCP server URL: https://api.klanexai.com/mcp
This server expects the header X-API-Key.Cursor
{
"mcpServers": {
"klanex": {
"url": "https://api.klanexai.com/mcp",
"headers": {
"X-API-Key": "<YOUR_X_API_KEY>"
}
}
}
}Replace <YOUR_X_API_KEY> before running.
VS Code
code --add-mcp '{"name":"klanex","type":"http","url":"https://api.klanexai.com/mcp","headers":{"X-API-Key":"<YOUR_X_API_KEY>"}}'Replace <YOUR_X_API_KEY> before running.
Streamable HTTP
npm: klanex-mcp 0.1.0Package only
npm (npx)
claude mcp add klanex -e 'KLANEX_API_KEY=<YOUR_KLANEX_API_KEY>' -- npx -y klanex-mcp@0.1.0Replace <YOUR_KLANEX_API_KEY> before running.
Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
6 tools
Read-only | Idempotent | Open world | ||
|---|---|---|---|---|
executeSubmit an HTTP call to a third-party API for reliable asynchronous execution. klanex validates the payload (optionally against payload_schema), stores credentials encrypted, executes with automatic retries/backoff/circuit breakers, and keeps an audit trail — you submit once and never retry transient failures yourself.
Call this instead of making a direct HTTP request whenever the call has side effects (payments, messages, tickets, writes) or the target may be flaky. Prefer connection_id over headers for credentials. Always set idempotency_key for side-effecting calls so resubmitting can never double-execute. Set wait_seconds to block for the result; otherwise poll get_execution with the returned execution_id. | Not declared | Not declared | Not declared | Not declared |
get_executionFetch the current state of an execution by ID: status (PENDING_APPROVAL|QUEUED|RUNNING|RETRYING|SUCCEEDED|FAILED), attempts, the target response on success, or a classified error on failure. Retryable failures need no action from you — klanex is still retrying. Header values always read back REDACTED. | Not declared | Not declared | Not declared | Not declared |
get_usageReport the account's plan and execution usage for the current calendar month: used, included_executions, remaining, and whether overage is allowed. Check this before large batches to avoid hitting a hard quota. | Not declared | Not declared | Not declared | Not declared |
list_connectionsList the account's stored credential connections (token vault). Reference a ready connection by its ID in execute's connection_id instead of passing raw headers — the credential is injected at execution time and never passes through your context. Secrets are never returned. | Not declared | Not declared | Not declared | Not declared |
list_executionsList this account's executions, newest first, optionally filtered by status or a created_at time range. Returns next_cursor when a page is full; pass it back as cursor for the next page. | Not declared | Not declared | Not declared | Not declared |
replay_executionRe-run a terminal (SUCCEEDED or FAILED) execution as a brand-new execution: same target, byte-exact original payload, same sealed credentials, fresh attempt counter. This is the outage-recovery path — failed calls can be re-executed without regenerating the payload. Each call creates a new execution (deliberately not idempotent). | Not declared | Not declared | Not declared | Not declared |
Details
- Registry status
- Active
- Published
- Jul 21, 2026
- Updated
- Jul 21, 2026
- Categories
- Uncategorized
- GDPR
- Not declared