Is the Chrassy Klanex MCP server down?

mcp-registry/io.github.chrassy/klanex · v0.1.0

Also listed as awesome/chrassy/klanex-mcp, glama/chrassy/klanex-mcp

healthy
Last checked 2026-10-26 17:15 UTC · handshake 220ms

As of 2026-10-26 17:15 UTC, the Chrassy Klanex MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 8 minutes.

uptime (30d checks)
100%
checks observed
4,890
outages (90d)
1
tools
6

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

Point your MCP client at this streamable-http endpoint: https://api.klanexai.com/mcp

Agent-readiness: C (78/100)

C (78/100): 0 error(s), 3 warning(s) across 6 tool(s); ~1,357 tokens of tool definitions.
Scores higher than 14% of 15,769 MCP servers Glimind has audited.
Its tool list costs an agent ~1,357 tokens per session — lighter than 65% of servers.
76 → 78 since 2026-10-17
no tool-poisoning patterns
Schemas82
Descriptions100
Safety hints0
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability100

What to fix (4)

6 of 6 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: execute, get_execution, get_usage, list_connections, list_executions and 1 more

2 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: execute, replay_execution

1 tool(s) have parameters with no type (no type/enum/anyOf/$ref).

Give every parameter a "type" (or "enum"/"anyOf"). Untyped parameters make models guess — strings for numbers, objects for arrays. How to fix →

Tools: execute

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 6 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.chrassy%2Fklanex/fixes

execute 2 changes
{
  "name": "execute",
  "description": "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.\n\nCall 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 he",
  "inputSchema": {
    "type": "object",
    "required": [
      "url"
    ],
    "properties": {
      "url": {
        "type": "string",
        "description": "absolute http(s) URL of the target endpoint"
      },
      "method": {
        "type": "string",
        "description": "HTTP method: GET, POST, PUT, PATCH, or DELETE (default POST)"
      },
      "headers": {
        "type": "object",
        "description": "request headers, typically third-party credentials; encrypted at rest and never readable back. Prefer connection_id so secrets never pass through your context",
        "additionalProperties": {
          "type": "string"
        }
      },
      "payload": {
        "description": "JSON body to send to the target",
        "type": "string"
      },
      "seal_url": {
        "type": "boolean",
        "description": "set true when the URL itself is a secret (webhook URL, presigned URL); it is encrypted and reads back redacted"
      },
      "timeout_ms": {
        "type": "integer",
        "description": "per-attempt timeout in milliseconds (default 30000)"
      },
      "max_attempts": {
        "type": "integer",
        "description": "maximum delivery attempts, 1-10 (default 5)"
      },
      "wait_seconds": {
        "type": "integer",
        "description": "block up to this many seconds (max 55) for a terminal result instead of returning immediately after queueing"
      },
      "connection_id": {
        "type": "string",
        "description": "ID of a stored credential connection (con_...) to authenticate the call; see list_connections"
      },
      "payload_schema": {
        "description": "JSON Schema to validate payload against before anything executes; mismatches are rejected synchronously with a correction hint",
        "type": "string"
      },
      "idempotency_key": {
        "type": "string",
        "description": "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"
      },
      "requires_approval": {
        "type": "boolean",
        "description": "pause for a human approve/reject decision before anything executes; use for destructive or high-stakes actions"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}
get_execution 1 change
{
  "name": "get_execution",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "required": [
      "execution_id"
    ],
    "properties": {
      "execution_id": {
        "type": "string",
        "description": "the execution ID (exe_...)"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}
get_usage 1 change
{
  "name": "get_usage",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "additionalProperties": false,
    "properties": {}
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.chrassy/klanex"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.chrassy/klanex"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.chrassy%2Fklanex.svg)](https://glimind.com/server/mcp-registry%2Fio.github.chrassy%2Fklanex?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.chrassy%2Fklanex?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.chrassy%2Fklanex.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.chrassy%2Fklanex.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.chrassy%2Fklanex?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:2d8276fa91ac1b07…, first seen 2026-10-17, included at leaf 6756 of 74,343. Version history · verify what your client received.

Tools (6)

Compare: most reliable code servers · most reliable other servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Chrassy Klanex MCP server down right now?

As of 2026-10-26 17:15 UTC, the Chrassy Klanex MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 8 minutes.

How many tools does Chrassy Klanex MCP server provide?

Chrassy Klanex MCP server advertises 6 tools, including execute, get_execution, get_usage, list_connections, list_executions.

How do I install Chrassy Klanex MCP server?

Point your MCP client at this streamable-http endpoint: https://api.klanexai.com/mcp

Is the Chrassy Klanex MCP server safe to connect to an AI agent?

Glimind scanned all 6 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Chrassy Klanex MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve