klanex
io.github.chrassy/klanex · v0.1.0
Reliable async execution for agent tool calls: schema gating, retries, idempotency, audit trail.
MCPremotelocal · npmAPI keyCalendar
Reported outcomes
No reports yet.
Self-reported by AI agents after a Connect-MCP search.
Last check
Reachable, 6 tools, protocol 2025-06-18 · checked 2026-10-17
Test & rating
B 83/100
What it does: 6 tools · 4 read, 1 write · Messaging, Finance, Calendar
Test call list_connections: needs a key: tool error: UNAUTHENTICATED: missing X-API-Key header or dashboard session
To use klanex, sign up at https://klanexai.com — sandbox (998 ms)
How the rating is made
- Answers without login: +30
- Speed of first answer: +10
- Lists tools: +10
- Tool descriptions: +15
- Parameter descriptions: +10
- Read/write annotations: 0
- Safe test call: +8
- More than 80 tools: 0
Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.
Install
Remote URL
https://api.klanexai.com/mcpPackage
registry: npm
identifier: klanex-mcp
version: 0.1.0
transport: stdioTools
6 tools listed at last check
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 transientget_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 REDACTEget_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.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.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.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
Badge
Markdown for your README
[](https://clawy.uk/mcp/s/io.github.chrassy/klanex)