Categories › AI & Agents › Multi-agent, orchestration & workflows
Search a registry of agent skills and MCP servers, then run them for real. No install, traced.
Remote server: your requests and data go to rokha.ai. Claude Code: claude mcp add --transport http rokha https://rokha.ai/mcp/jsonrpc · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
hunt_report — A 402 purchase_required here is Rokha's own price for the call (the pack and your own x402 order), never the target site. Rokha's HUNT: givex_account_audit — Rokha's account auditor: give it any X @handle and get an organic-ness audit — 0–100 score, ORGANIC/MIXED/SMOKE verdict, and the promotionalsend_agent_message — Send a message to a Rokha agent (default 'rokha-agent') and get its reply. With a logged-in identity (Authorization: Bearer <JWT>) the agentregistry_search — Search the public skill and MCP registries at once, plus what builders publish on Rokha (the live count is in GET /api/marketplace/registry/registry_get_skill — Fetch everything an agent needs to adopt a Registry skill: the full SKILL.md (agentskills.io standard — frontmatter name/description + body)rig_search — List YOUR saved rigs, newest first, optionally narrowed by `query` (matches the name/summary). This is how an agent RECOVERS: rig_author retrig_get — Read ONE of your rigs in full — its steps, wiring, guards and stage. Use it before editing so a change is made against what is actually savetrace_search — List your Traces — the durable record of what a run DID, newest first. This is the other half of rig_run: a run reports that it started, andrig_run — RUN a rig, for real, right now. Without this an outside agent could AUTHOR a rig, schedule it and hang a webhook on it — but never run one oskill_author — Author a standard agentskills.io Agent Skill and get back its SKILL.md. A strong skill has: a `name` in kebab-case (lowercase letters, numbeauth_resolve — The AUTH LADDER: classify any MCP server URL — 'open' (no credential), 'key' (paste a token into the vault once), 'tier1' (one-click accountrig_author — Author a multi-step Rig as a graph the runtime executes for real. `nodes` are the steps, `edges` {from, to, guard?} wire them; `structure_tytrace_get — READ one trace in full (input, result, status, timing) by `id`, or a whole run by `run_id` (status, steps with their trace ids, output, everregistry_publish — Publish (or update) YOUR listing in the Rokha Registry so anyone — human or agent — can find and use it. Requires a logged-in identity (Authauth_wallet_challenge — Step 1 of registering (or logging in) a user with a wallet keypair — no browser needed. Returns a challenge message to sign with the wallet'auth_wallet_verify — Step 2: submit the signed challenge. On success returns session_token — a JWT to send as `Authorization: Bearer <token>` on every subsequentstudio_doors — WHAT ROKHA COSTS. Rokha is the Agent Runtime and Marketplace — build tools, run them for real, sell or hire them. No platform payouts. THREEmarket_search — THE MARKET (rokha.ai/market, GET /api/market) — everything you can run on Rokha in one store: Rokha-native rigs, skills, MCP servers, agentsmark_check — A 402 purchase_required here is Rokha's own price for the call (the pack and your own x402 order), never the target site. MARK CHECK — one dpage_me — YOUR page as the logged-in identity sees it. If you haven't claimed one yet, returns { claimed: false, suggested_handle } — follow with pagepage_claim — Claim your public /@handle page (or update it — re-claiming your own handle edits in place; a new handle renames). The page is owned by the registry_adopt — The select → input → run door: materialize YOUR OWN runnable copy of any published rig listing (find provider_id + external_id via registry_free_tier_status — THE FREE TIER — what anyone gets on Rokha each UTC day, read from the one definition the gates enforce. Free, no account: talk to Rokha (10 agent_create — Requires a JWT (sign in headlessly with auth_wallet_challenge → auth_wallet_verify). Creates an agent you own — the same door and the same cproduct_get — Public. Is this item paid, and what does it cost? Name it by product_id, by provider_id + external_id (a registry listing — rig/skill/harnesproduct_checkout — Requires a JWT or an rk_ key. Buy product_id for YOURSELF. rail 'x402' with no signature returns an x402 challenge (accepts: Solana exact USpurchases_mine — Requires a JWT or an rk_ key. Your paid unlocks, passes (period_end) and run packs (runs_left).subscribe — Requires a JWT or an rk_ key (sign in headlessly with auth_wallet_challenge → auth_wallet_verify). Starts the Lab month — $29.99 a month, fusubscription_status — Requires a JWT or an rk_ key. Read-only. Your own access: studio (true = full access), access (rent | holder | house | none …), current_peritools_catalog — tools/list carries the `core` set only; this finds the rest, and every tool is callable whether or not it is listed. No arguments: the toolsNot tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.