MCP stdio toolkit for IOWAP — curated agent tools over the IOWAP node CLI
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":"iowap-client-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.
# iowap-client-mcp MCP toolkit for IOWAP: run a curated IOWAP toolset from any MCP-speaking agent — without teaching every agent the node CLI's pitfalls. ## The problem IOWAP is a distributed capability mesh: the [relay](https://github.com/iowap-org/iowap-server) routes tasks, [nodes](https://github.com/iowap-org/iowap-node) execute them. Today, an AI agent that wants to use IOWAP shells out to `node-cli --json`. That works, but every agent has to relearn the same pitfalls itself: response envelopes that must be unwrapped, node IDs vs. names, the global flag position, which commands are safe and which mutate the node. Knowledge ends up in one agent's skill file instead of in code. ## The answer `iowap-mcp` is an MCP stdio server that wraps `node-cli` behind a small, curated toolset: | Tool | Purpose | |------|---------| | `relay_status` | Relay health, queue depth, task counters | | `node_list` | Fleet overview (IDs, status, capabilities, load) | | `capabilities_list` | What the relay can do — including input schemas **and** the node IDs that own each capability | | `task_submit` | Submit a task against a capability (optional short wait) | | `task_result` | Poll a task result | | `artifact_download` | Fetch a task artifact to a local path | | `docs` | Read the live relay documentation | The node CLI remains the source of truth for authentication and execution — the server adds zero credential handling of its own. Destructive commands (register, update, daemon control, capability publishing) are deliberately not exposed. **Trust model:** whoever can launch `iowap-mcp` on the host acts with the host's node identity — an MCP client spawning this server is a trusted executor. Environment filtering of the stdio subprocess is host behavior; the package relies on the node's on-disk identity and enforces none of it itself. **Narrowable execution:** operators can restrict which capabilities `task_submit` may fire with `IOWAP_ALLOW_CAPS=cap.one,cap.two` (csv env, un…
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.