mcpbeat

klanex MCP Server

io.github.chrassy/klanex
answering

klanex is answering right now. Last checked 13 min ago. 49 installs a week from npm. It exposes 6 tools. Last commit 22 Jul 2026.

Reliable async execution for agent tool calls: schema gating, retries, idempotency, audit trail.

Installs per day peak 113 · avg 7 · -71% w/w
a month agotoday
Uptime history 40 hours of history
40 hours agonow
100.0%
Uptime 24h
91 of 91 checks
6
Tools
read from the server
152 ms
Response time
average over 24h
49
Installs / week
npm and PyPI

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 13 min ago.

run in your terminal
claude mcp add klanex --transport http https://api.klanexai.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "klanex": {
      "url": "https://api.klanexai.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.klanex]
url = "https://api.klanexai.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "klanex": {
      "url": "https://api.klanexai.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "klanex": {
      "url": "https://api.klanexai.com/mcp"
    }
  }
}

Available tools 6

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

connections
list_connections
List 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.
execute
execute
Submit 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.
execution
get_execution
Fetch 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.
executions
list_executions
List 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
replay_execution
Re-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).
usage
get_usage
Report 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.

Endpoints

URLTransportStateLatencyChecked
https://api.klanexai.com/mcp streamable-http answering 189 ms 13 min ago

klanex — questions

Answers built from our own checks of this server.

What can klanex do?
It exposes 6 tools, read directly from the server on our last check. Among them: execute, get_execution, get_usage, list_connections, list_executions, replay_execution. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is klanex working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 152 ms. The bar chart above shows every period we have measured.
How do I connect klanex?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does klanex need an API key?
No. klanex completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 6 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is klanex?
It answers our handshake in 152 ms on average, which is faster than 73% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use klanex?
The npm package klanex-mcp was installed 49 times in the last week. Week over week that is -71%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is klanex open source?
Yes — it is published under the MIT licence, written in JavaScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.