Is the Kali123411 K402 MCP server down?

mcp-registry/io.github.kali123411/k402 · v1.28.1

As of 2026-10-22 19:54 UTC, the Kali123411 K402 MCP server is up with a Glimind reliability score of 86/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 13 outages in 90 days, with a median recovery of 2 minutes.

Agent-payable APIs on Kaspa: LLMs, chain data, covenants, zk proofs — pay per call, no API key

claude mcp add --transport http kali123411-k402-mcp-server https://x402-compute.68cxgfyr0.workers.dev/mcp

{
  "mcpServers": {
    "kali123411-k402-mcp-server": {
      "type": "http",
      "url": "https://x402-compute.68cxgfyr0.workers.dev/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: D (69/100)

What to fix (4)

Auto-fix: 16 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 29 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.kali123411%2Fk402/fixes

{
  "name": "channel_status",
  "description": "Status of a kaspa-channel by its channel id (covenant id): funded value, amount spent via\n    vouchers, remaining, expiry, and whether it has been closed on-chain. Free.",
  "inputSchema": {
    "type": "object",
    "title": "channel_statusArguments",
    "required": [
      "channel_id"
    ],
    "properties": {
      "channel_id": {
        "type": "string",
        "title": "Channel Id"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

{
  "name": "covenant_address",
  "description": "Derive the covenant P2SH address for a compiled script on 'mainnet' or 'testnet-10'.\n    Paid (~$0.0003).",
  "inputSchema": {
    "type": "object",
    "title": "covenant_addressArguments",
    "required": [
      "script_hex"
    ],
    "properties": {
      "network": {
        "type": "string",
        "title": "Network",
        "default": "mainnet"
      },
      "script_hex": {
        "type": "string",
        "title": "Script Hex"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}

{
  "name": "covenant_check",
  "description": "Local txscript pre-verify of a signed covenant tx BEFORE broadcast — catches script failures\n    that would otherwise cost you a broadcast. 'entries' are the spent UTXOs (covenant_utxos output\n    plugs in directly). Returns {all_ok, inputs:[{index, ok, error?}]}. Paid (~$0.0005).",
  "inputSchema": {
    "type": "object",
    "title": "covenant_checkArguments",
    "required": [
      "transaction",
      "entries"
    ],
    "properties": {
      "entries": {
        "type": "array",
        "items": {},
        "title": "Entries"
      },
      "transaction": {
        "type": "object",
        "title": "Transaction",
        "additionalProperties": true
      }
    }
  },
  "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.kali123411/k402"],"email":"[email protected]"}'

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

Passed

• Every tool has a well-formed, typed input schema.
• No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
• Compact tool list (~4,597 tokens).
• Tool names are unique and portable across clients.
• Speaks MCP 2025-06-18.
• 99.84% uptime over 30 days.
• No breaking contract changes in 30 days.

Largest tool definitions

• covenant_build ~262 tokens
• pay_per_call ~258 tokens
• registry_search ~245 tokens
• generate ~187 tokens
• prove_submit ~181 tokens

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:

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.kali123411%2Fk402.svg)](https://glimind.com/server/mcp-registry%2Fio.github.kali123411%2Fk402?ref=badge)

<a href="https://glimind.com/server/mcp-registry%2Fio.github.kali123411%2Fk402?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.kali123411%2Fk402.svg" alt="MCP agent-readiness"></a>

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.kali123411%2Fk402.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.kali123411%2Fk402?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:515e96b72389f7cc…, first seen 2026-10-17, included at leaf 14664 of 47,845. Version history · verify what your client received.

Tools (36)

• attest_verify
• catalog
• channel_config
• channel_status
• classify
• covenant_address
• covenant_broadcast
• covenant_build
• covenant_check
• covenant_compile
• covenant_utxos
• embed_text
• extract
• generate
• job_result
• job_status
• kaspa_balance
• kaspa_fee_estimate
• kaspa_network
• kaspa_tx_status
• kaspa_utxos
• open_session
• pay_per_call
• payment_options
• prove_guest_upload
• prove_preflight
• prove_submit
• read_url
• registry_provider
• registry_search
• rewrite
• search_index
• search_query
• session_status
• summarize
• use_session

Compare: most reliable security servers · most reliable other servers · most reliable finance servers · most reliable ml servers · most reliable blockchain servers

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

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

FAQ

Is the Kali123411 K402 MCP server down right now?

As of 2026-10-22 19:54 UTC, the Kali123411 K402 MCP server is up with a Glimind reliability score of 86/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 13 outages in 90 days, with a median recovery of 2 minutes.

How many tools does Kali123411 K402 MCP server provide?

Kali123411 K402 MCP server advertises 36 tools, including attest_verify, catalog, channel_config, channel_status, classify.

How do I install Kali123411 K402 MCP server?

Point your MCP client at this streamable-http endpoint: https://x402-compute.68cxgfyr0.workers.dev/mcp

Is the Kali123411 K402 MCP server safe to connect to an AI agent?

Glimind scanned all 36 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 Kali123411 K402 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.