Skip to content

klanex MCP server

io.github.chrassy/klanexchrassystreamable-httpv0.1.0Scanned

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

6 tools: 2 change things and 4 only read.

Tools: 0 delete, 0 irreversible, 2 write, 4 read.
  • Reads private data · 2
  • Reads text others write · 0
  • Can send data out · 1
  • 5 findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the klanex MCP server can do

The klanex MCP server is published by the GitHub account chrassy. It has 6 tools. It can create or change data (2 tools: execute and replay_execution), but cannot delete data. 4 tools only read.

2 tools read private data (get_usage and list_connections); 1 tool can send data out of your system (execute).

The fixed checks matched 5 findings (credentials-mention). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 16, 2026, version 0.1.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

6 tools

Changes things 2Claude Code: ask
  • executeSubmit an HTTP call to a third-party API for reliable asynchronous execution.Can send data out3 findings

    Why it is in this group

    • The name "execute" says "execute": a word for a change.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "...ionally against payload_schema), stores credentials encrypted, executes with automatic retr..."

      What this check looks for
    • Info

      The input schema at properties.headers.description mentions "credentials".

      Matched text

      inputSchema.properties.headers.description: "request headers, typically third-party credentials; encrypted at rest and never readable b..."

      What this check looks for
    • Info

      The input schema at properties.connection_id.description mentions "credential".

      Matched text

      inputSchema.properties.connection_id.description: "ID of a stored credential connection (con_...) to authenticate th..."

      What this check looks for
    Description, as the server wrote it
    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.
  • 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.1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "...yte-exact original payload, same sealed credentials, fresh attempt counter. This is the out..."

      What this check looks for
    Description, as the server wrote it
    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).
Only reads 4Show 4 read-only tools
  • get_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 o…No findings

    Why it is in this group

    • The name "get_execution" says "get": a word for reading.
    Description, as the server wrote it
    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.
  • get_usageReport the account's plan and execution usage for the current calendar month: used, included_executions, remaining, and whether overage is allowed.Reads private dataNo findings

    Why it is in this group

    • The name "get_usage" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "calendar": it reads calendars.
    Description, as the server wrote it
    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_connectionsList the account's stored credential connections (token vault).Reads private data1 finding

    Why it is in this group

    • The name "list_connections" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "credential": it reads secrets.

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "List the account's stored credential connections (token vault). Reference a..."

      What this check looks for
    Description, as the server wrote it
    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_executionsList this account's executions, newest first, optionally filtered by status or a created_at time range.No findings

    Why it is in this group

    • The name "list_executions" says "list": a word for reading.
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input.

Reads private data2
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:03 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://api.klanexai.com/mcp: tools/list returned 6 tools to an anonymous client, including execute (write), replay_execution (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

5 info
  • The description mentions "credentials".

    Matched text

    description: "...ionally against payload_schema), stores credentials encrypted, executes with automatic retr..."

    What this check looks for
  • The input schema at properties.headers.description mentions "credentials".

    Matched text

    inputSchema.properties.headers.description: "request headers, typically third-party credentials; encrypted at rest and never readable b..."

    What this check looks for
  • The input schema at properties.connection_id.description mentions "credential".

    Matched text

    inputSchema.properties.connection_id.description: "ID of a stored credential connection (con_...) to authenticate th..."

    What this check looks for
  • The description mentions "credential".

    Matched text

    description: "List the account's stored credential connections (token vault). Reference a..."

    What this check looks for
  • The description mentions "credentials".

    Matched text

    description: "...yte-exact original payload, same sealed credentials, fresh attempt counter. This is the out..."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http klanex https://api.klanexai.com/mcp --header 'X-API-Key: <your-x-api-key>'
claude mcp add --transport http klanex https://api.klanexai.com/mcp --header 'X-API-Key: <your-x-api-key>'

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__klanex__get_execution",
      "mcp__klanex__get_usage",
      "mcp__klanex__list_connections",
      "mcp__klanex__list_executions"
    ],
    "ask": [
      "mcp__klanex__execute",
      "mcp__klanex__replay_execution"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as klanex. Review it before you use it.

Capability tags behind 3 rules
  • mcp__klanex__execute outbound
  • mcp__klanex__get_usage private-data
  • mcp__klanex__list_connections private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.chrassy/klanex/verify?hash=3824cb3960ec37ebc03491da349ab5396762e1db75ad0ac538eaca37cb4cd733" | jq -e '.changed == false'

Pinned hash 3824cb3960ec, from Nov 16, 2026, 13:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.chrassy/klanex/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.chrassy/klanex
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.chrassy/klanex.svg)](https://radar.anlyon.com/servers/io.github.chrassy/klanex)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:27 UTC.

klanex MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the klanex MCP server safe?

No scan can promise that. What its definitions show: 6 tools, 2 of which can change, send or delete something, and 5 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the klanex MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the klanex MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the klanex MCP server have?

6 tools: 2 write, 4 read. execute, replay_execution, get_execution, get_usage, list_connections and list_executions.

Does the klanex MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the klanex MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): execute.

Has the klanex MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 16, 2026.