mcpbeat Sign in

klanex MCP Server

answering

klanex is answering right now. Last checked 6 min ago. 36 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.

Installs per day peak 11 · avg 4 · -21% w/w
a month agotoday
Uptime history 91 days of history · worst day 99%
91 days agonow
100.0%
Uptime 24h
91 of 91 checks
6
Tools
read from the server
169 ms
Response time
average over 24h
36
Installs / week
npm and PyPI

What the code does

We read the source, 3 d ago · tools taken from the live server · rules 995398eba69f

Capabilities

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.

Secret passed into the image build Dockerfile:14
# 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.

This code can reach further than it looks

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.

Three servers free · no card

Connect this server

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

run in your terminal
claude mcp add klanex --transport http https://api.klanexai.com/mcp
Settings → Connectors → Add custom connector, then paste this address
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
{
  "servers": {
    "klanex": {
      "type": "http",
      "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 222 ms 6 min ago

Alternatives to klanex

same job, measured the same way
Quill
by manumarri-sudo

Pre-execution gate for AI-agent tool calls. Touch ID approval. Tamper-evident audit log.

100 installs/wk local only
Guardian MCP
by odingard

Routes agent tool calls through Guardian for ALLOW/ASK/DENY before execution.

1 483 installs/wk local only
Agent Audit MCP
by rumblingb

Immutable audit trail for agent-to-agent interactions

local only
D
DakNode
by subodh103

Email and calendar API tools for agents: inboxes, conversations, availability and reliable booking.

1 545 installs/wk local only
Superagenticmcp
by anamized

MCP-native router and multi-agent control plane: plan, route tool calls, stream execution.

local only
Oakallow
by oakallow

Runtime permission, approval, and audit layer for AI agent tool execution.

answering
Getplexa
by getplexa

Economic-safety tools for trading agents: executable quote + rug/honeypot pretrade check via x402.

89 installs/wk local only
Tripwire
by bonesdefi

Security gateway for MCP agents: blocks prompt-injection-driven tool calls before they execute.

51 installs/wk local only

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 169 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 in the form 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 169 ms on average, which is faster than 78% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. 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 36 times in the last week. Week over week that is -21%. 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?
The code is open source: it is published under the MIT licence, written in JavaScript and 0 stars on GitHub. The licence covers the code in the repository, not the hosted service at api.klanexai.com, which runs on its operator's own terms.