Python client for the Nukez MCP server — connect, list tools, and call Nukez agent-native storage and verification tools over streamable HTTP JSON-RPC.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"nukez-nukez-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# nukez-mcp Python client for the **Nukez MCP server** — agent-native persistent storage with cryptographic verification on Solana. The Nukez MCP is a streamable HTTP JSON-RPC server that wraps the Nukez gateway. It is **keyless**: the server never holds a wallet or signing key. Clients execute payments externally, sign Ed25519 operation envelopes locally, and pass those envelopes through MCP tool arguments. This package provides a simple class around an HTTP library with a method for connecting to the server, listing its tools, and calling them. ## Install ```bash pip install nukez-mcp ``` ## Quickstart ```python from nukez_mcp import NukezMCP with NukezMCP() as mcp: info = mcp.connect() print(info["serverInfo"]) # server name and version tools = mcp.list_tools() print(f"{len(tools)} tools registered") status = mcp.call_tool("nukez_status") print(status["capabilities"]["payment_rails"]) ``` The default endpoint is the production server: ``` https://mcp.nukez.xyz/mcp ``` Pass a different `endpoint=` to the constructor to target another deployment. ## The tool surface The production server registers 15 tools: | Group | Tools | |-------|-------| | Payment & setup | `nukez_quote`, `nukez_pay`, `nukez_provision`, `nukez_setup` | | Files | `nukez_create_file`, `nukez_store`, `nukez_confirm`, `nukez_upload_chunk`, `nukez_retrieve`, `nukez_delete` | | Proof & freshness | `nukez_status`, `nukez_verify`, `nukez_recompute_verify` | | Memory | `nukez_remember`, `nukez_recall` | The canonical flow is `nukez_quote` → external chain transfer → `nukez_pay` → `nukez_provision`, after which mutating and payer-authorized operations — store, confirm, delete, remember, attest push, recompute-verify — require client-signed envelopes. Reads such as retrieve, recall, status, and structural verify need only the `receipt_id`. ## Signed envelopes and payments Envelope signing and payment execution are deliberately **not** part of this pack…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.