
klanex MCP server
online · 100% uptimeio.github.chrassy/klanex·v0.1.0Reliable async execution for agent tool calls: schema gating, retries, idempotency, audit trail.
0 stars20 downloads/wk
Reviews
Write oneNobody has reviewed klanex yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
klanex tools (6, 1 write)
write = sends, deletes, buys or postsexecutewrite actionFreeSubmit 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.
get_executionFreeFetch 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.
get_usageFreeReport 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.
list_connectionsFreeList 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.
list_executionsFreeList 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.
replay_executionFreeRe-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).
Public scan report
scanner v0.1.9 · 2026-09-25 · same rubric, same numbers if you re-run it
- Code scan2 source files scanned25/25
- Live reliabilityremote reachable in 1294ms20/20
- Tool poisoning6 tool descriptions checked15/15
- Auth qualityAPI key sent as a header8/15
- Maintenancelast push 7 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How klanex compares
Against every graded AI and agents MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 91/100
- higher than 88% of 4,460 AI and agents servers
- Tools
- 6
- the typical AI and agents server has 6
- Tools that change things
- 17%
- typical: 0%. Fewer write tools means less an agent can break
- Uptime
- 100%
- of our recent checks; the typical remote AI and agents server answers 100%
- Response time
- 428 ms
- faster than 32% of 2,331 AI and agents servers
- Downloads a week
- 20
- more than 6% of 1,538 AI and agents servers with a package
What its tools let an agent do: 5 read · 1 run or deploy
Install klanex in Claude Code, Cursor or VS Code
claude mcp add --transport http klanex https://api.klanexai.com/mcp
What the publisher says
From the klanex repository's README, as published. We do not edit it. Read it on GitHub
klanex MCP server
Reliable execution for agent tool calls, as an MCP server.
klanex is an async execution layer between an agent's tool-use intents and real third-party APIs: it schema-gates hallucinated payloads before anything runs, absorbs rate limits and outages with retries/backoff/circuit breakers, encrypts credentials, keeps an audit trail, and reports back via signed webhooks. With this MCP server, an agent submits a call once — klanex makes sure it lands.
Failures come back written for the model: every error carries an llm_hint telling the agent exactly what to fix (or that klanex is already handling it), so agents self-correct instead of guessing.
Connect (hosted, recommended)
klanex's MCP server is hosted — no install needed if your client supports HTTP transports:
Get an API key at klanexai.com — sandbox keys are free.
Claude Code
claude mcp add --transport http klanex https://api.klanexai.com/mcp \
--header "X-API-Key: klx_live_..."Cursor / Windsurf / VS Code (mcp.json)
{
"mcpServers": {
"klanex": {
"url": "https://api.klanexai.com/mcp",
"headers": { "X-API-Key": "klx_live_..." }
}
}
}Authorization: Bearer klx_... works too, for clients that can only set that header.
Connect (stdio shim)
For clients that only speak stdio (e.g. Claude Desktop), this package proxies stdio to the hosted endpoint:
{
"mcpServers": {
"klanex": {
"command": "npx",
"args": ["-y", "klanex-mcp"],
"env": { "KLANEX_API_KEY": "klx_live_..." }
}
}
}The shim routes by key prefix — klxtest… keys go to the sandbox automatically. Set KLANEXMCPURL to override.
Tools
Why this beats calling APIs directly
- Hallucinated payloads are rejected before they execute — pass payload_schema and mismatches return synchronously with a correction hint.
- Transient failures are not the agent's problem — 429s, timeouts, and 5xxs are retried with backoff behind a circuit breaker; the agent does nothing.
- A network blip can never double-execute a refund — idempotency_key makes submits safe to retry.
- Destructive actions can wait for a human — requires_approval pauses execution for an approve/reject decision (API, dashboard, or Slack buttons).
- Credentials stay out of model context — store them once as a connection; klanex injects them at execution time.
Full API docs: api.klanexai.com/docs
License
MIT
Nothing above is checked by us. What we check is on the safety report.
klanex: common questions
- Is klanex MCP server safe?
- Yes, by our scan: it is graded A (91/100). Read the klanex safety report
- How do I install klanex?
- It runs remotely at api.klanexai.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does klanex need an API key?
- Yes. The registry entry asks for
KLANEX_API_KEY,X-API-Key. - Is klanex maintained?
- The last commit was 47 days ago (2026-09-18). The latest release is v0.1.0.
- Is klanex up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- What can I use instead of klanex?
- Servers from other publishers that do the same job: FireCMS Cloud MCP server, Decionis MCP server and Butterbase AI MCP server.
- How does klanex compare with other AI and agents MCP servers?
- safety score 91/100 (higher than 88% of 4,460 AI and agents servers); tools 6 (the typical AI and agents server has 6); tools that change things 17% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.
Alternatives to klanex
Same job from other publishers: the closest match first, then the best rated.
- FireCMS CloudManage FireCMS Cloud from an AI agent: Firestore data, collections, schemas and users.not reviewedEstablishedA
- DecionisAuthorize consequential AI agent actions before executionnot reviewedEstablishedA
- Butterbase AIButterbase MCP server — manage your backend: schemas, auth, functions, storage, RAG, deploys.not reviewedEstablishedA
- Roast My Design SystemAudit your Design System and serve your Agent the rules that keep AI-written UI on-system.not reviewedEstablishedA
- Roast My Design SystemAudit your Design System and serve your Agent the rules that keep AI-written UI on-system.not reviewedEstablishedA