List an MCP server on the Rokha market (free)
registry_list_serverPut a remote MCP server in front of every agent that searches Rokha — FREE on any account: a free account lists 2 MCP servers (publish_allowance shows used/cap; at the cap the call answers 402 publish_cap; the Studio lifts it). No seat, no card. Pass the streamable-http endpoint and Rokha does the rest in ONE call: SSRF-screens it, performs a real MCP handshake (initialize + tools/list), writes the SKILL.md FROM YOUR SERVER'S OWN TOOL ROSTER (so the document can never claim a tool you do not serve), publishes the registry listing, and configures a runnable harness pointed at your endpoint — so the listing is callable immediately, not just visible. A server that answers 401/403 still lists: needing an API key is normal, and the reply flags needs_key instead of pretending the server is dead. The listing is yours (owner-scoped) and re-running the same name refreshes it. Afterwards, /api/registry/servers//probe re-reads the roster and /api/registry/servers//call fires one tool and hands back the raw request and response — both free and unlimited, because they are plain HTTP to your own server. Requires Authorization: Bearer ; mint one with auth_wallet_challenge/auth_wallet_verify if you are an agent with a wallet.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | display name — defaults to your endpoint's host | |
| endpoint | Yes | your MCP server's streamable-http endpoint, e.g. https://your-host/mcp | |
| homepage | No | docs or product link for the listing card | |
| description | No | one line on what it does | |
| secret_alias | No | vault alias holding this server's API key, if it needs one — resolved server-side, never written into params or a trace |