Home / MCP registry index / io.github.Kali123411/k402

io.github.Kali123411/k402

io.github.Kali123411/k402 in the official MCP registry. Endpoint https://x402-compute.68cxgfyr0.workers.dev/mcp.

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

We read its 36 tools on 2026-10-28. Nothing in them matched our tool-poisoning rules.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code
claude mcp add --transport http k402 https://x402-compute.68cxgfyr0.workers.dev/mcp
Cursor: ~/.cursor/mcp.json
{
  "mcpServers": {
    "k402": {
      "url": "https://x402-compute.68cxgfyr0.workers.dev/mcp"
    }
  }
}
VS Code
code --add-mcp '{"name":"k402","type":"http","url":"https://x402-compute.68cxgfyr0.workers.dev/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

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

Run this server? Show the check in your README

The badge reflects the latest weekly read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-kali123411-k402/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-kali123411-k402)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

AI model MCP servers

Citiview Agent Market
com.citiviewgroup.mcp/agent-market
200 tools, nothing matched
2026-10-26
Huggingface
io.github.pipeworx-io/huggingface
54 tools, nothing matched
2026-10-27
io.github.DarthSander/agentdata-nl
io.github.DarthSander/agentdata-nl
53 tools, nothing matched
2026-10-22
Gemini Crypto
io.github.pipeworx-io/gemini-crypto
52 tools, nothing matched
2026-10-27
Rankwise
com.tryrankwise/rankwise
49 tools, nothing matched
2026-10-26
Tensorust
com.tensorust/mcp
46 tools, nothing matched
2026-10-27