# klanex (remote · api.klanexai.com)

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

- Trust score: 67/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `api.klanexai.com`: 67/100 (this document), [markdown](https://verifymcp.io/servers/chrassy-klanex/api.md), [page](https://verifymcp.io/servers/chrassy-klanex/api)
- npm · `klanex-mcp`: 35/100, [markdown](https://verifymcp.io/servers/chrassy-klanex/klanex-mcp.md), [page](https://verifymcp.io/servers/chrassy-klanex/klanex-mcp)

## Channel facts

- Endpoint: `https://api.klanexai.com/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 75/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 897 tokens (~149/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http chrassy-klanex https://api.klanexai.com/mcp
```

### Codex

```toml
[mcp_servers.chrassy-klanex]
url = "https://api.klanexai.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "chrassy-klanex": {
      "type": "remote",
      "url": "https://api.klanexai.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add chrassy-klanex --url https://api.klanexai.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  chrassy-klanex:
    url: "https://api.klanexai.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "chrassy-klanex": {
      "type": "http",
      "url": "https://api.klanexai.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 65, −1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 66, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 64, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 63)

First indexed and scored.

## MCP tools (6)

### `execute` (~459 tokens)

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.

Input parameters:

- `connection_id` (string): ID of a stored credential connection (con_...) to authenticate the call; see list_connections
- `headers` (object): request headers, typically third-party credentials; encrypted at rest and never readable back. Prefer connection_id so secrets never pass through your context
- `idempotency_key` (string): stable key (max 255 chars) making this submit safe to retry; the same key returns the original execution instead of creating a new one. Always set this for side-effecting calls
- `max_attempts` (integer): maximum delivery attempts, 1-10 (default 5)
- `method` (string): HTTP method: GET, POST, PUT, PATCH, or DELETE (default POST)
- `payload`: JSON body to send to the target
- `payload_schema`: JSON Schema to validate payload against before anything executes; mismatches are rejected synchronously with a correction hint
- `requires_approval` (boolean): pause for a human approve/reject decision before anything executes; use for destructive or high-stakes actions
- `seal_url` (boolean): set true when the URL itself is a secret (webhook URL, presigned URL); it is encrypted and reads back redacted
- `timeout_ms` (integer): per-attempt timeout in milliseconds (default 30000)
- `url` (string, required): absolute http(s) URL of the target endpoint
- `wait_seconds` (integer): block up to this many seconds (max 55) for a terminal result instead of returning immediately after queueing

### `get_execution` (~96 tokens)

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.

Input parameters:

- `execution_id` (string, required): the execution ID (exe_...)

### `get_usage` (~50 tokens)

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.

### `list_connections` (~56 tokens)

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.

### `list_executions` (~143 tokens)

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.

Input parameters:

- `cursor` (string): opaque next_cursor value from a previous page
- `limit` (integer): page size, 1-100 (default 20)
- `since` (string): only executions created at or after this RFC3339 timestamp
- `status` (string): filter by status: QUEUED, RUNNING, RETRYING, SUCCEEDED, or FAILED
- `until` (string): only executions created before this RFC3339 timestamp

### `replay_execution` (~93 tokens)

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).

Input parameters:

- `execution_id` (string, required): the execution ID (exe_...)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/chrassy-klanex/api#diagnostics

## Score history

- 2026-08-03: 67
- 2026-08-02: 66
- 2026-08-01: 66
- 2026-07-31: 65
- 2026-07-30: 66
- 2026-07-29: 65
- 2026-07-28: 64
- 2026-07-27: 64
- 2026-07-26: 63

## Links

- Remote endpoint: https://api.klanexai.com/mcp
- Authorisation metadata: https://api.klanexai.com/.well-known/oauth-protected-resource/mcp
- Repository: https://github.com/chrassy/klanex-mcp
- Website: https://klanexai.com/
- Changelog RSS feed: https://verifymcp.io/servers/chrassy-klanex/api/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/chrassy-klanex/api/changelog.json
- HTML version of this page: https://verifymcp.io/servers/chrassy-klanex/api