klanex
REMOTE · API.KLANEXAI.COM · 2 COMPONENTS · SCANNED AUG 3
Reliable async execution for agent tool calls: schema gating, retries, idempotency, audit trail.
Available components
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. How we score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · api.klanexai.com
claude mcp add --transport http chrassy-klanex https://api.klanexai.com/mcp
[mcp_servers.chrassy-klanex] url = "https://api.klanexai.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"chrassy-klanex": {
"type": "remote",
"url": "https://api.klanexai.com/mcp",
"enabled": true
}
}
} openclaw mcp add chrassy-klanex --url https://api.klanexai.com/mcp --transport streamable-http
mcp_servers:
chrassy-klanex:
url: "https://api.klanexai.com/mcp" {
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Aug 26 +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.
- 1 Aug 26 +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.
- 31 Jul 26 −1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +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.
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 63
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Probed https://api.klanexai.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.klanexai.com | CN=WR3,O=Google Trust Services,C=US | 18 Jul 2026 | 16 Oct 2026 | RSA 2048 | SHA256-RSA | 3e20987b13ecf8cd09c850318c90bdb9 |
| SANs: api.klanexai.com | ||||||
| CN=WR3,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a91568d63abc22861684aa4b5a |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
DNSSEC insecure
Validation of api.klanexai.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| klanexai.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.klanexai.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.klanexai.com/mcp | HTTPS enforced | 301 | https://api.klanexai.com:443/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
execute ~459
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 |
No output schema declared.
No examples provided.
get_execution ~96
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.
| Name | Type | Req | Description |
|---|---|---|---|
| execution_id | string | yes | the execution ID (exe_...) |
No output schema declared.
No examples provided.
get_usage ~50
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_connections ~56
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_executions ~143
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
replay_execution ~93
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).
| Name | Type | Req | Description |
|---|---|---|---|
| execution_id | string | yes | the execution ID (exe_...) |
No output schema declared.
No examples provided.