Agent MCP Directory

Rokha: MCP server, CLI and agent surfaces

Yes: Rokha runs a public MCP server at rokha.ai that listed 30 tools to a client with no credentials on 4 November 2026. Examples: send_agent_message, registry_search, registry_get_skill. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool.

Fact sheet

CompanyRokha
Domainrokha.ai
CategoryInfrastructure (assigned by this directory from the registry description)
MCP serverVerified (No authentication)
Ora scorenone: Ora returned no cached score for rokha.ai when asked on 5 November 2026
Company found throughthe GitHub MCP Registry; the official MCP Registry
Last verified4 November 2026

MCP server

Endpointhttps://rokha.ai/mcp/jsonrpc
How it was foundlisted in the GitHub MCP Registry; the official MCP Registry
Transportstreamable-http
HTTP status200
Protocol version2025-11-25
Serverrokha 1.0.0
Capabilitiesprompts, resources, tools
Tools30
Resources0
Prompts2
Connected4 November 2026, 20:04 UTC
Handshake time2,514 ms over 1 attempt

Tools listed

30 tools

  • send_agent_message
  • registry_search
  • registry_get_skill
  • rig_search
  • rig_get
  • trace_search
  • rig_run
  • skill_author
  • auth_resolve
  • rig_author
  • trace_get
  • registry_publish
  • auth_wallet_challenge
  • auth_wallet_verify
  • studio_doors
  • market_search
  • mark_check
  • hunt_report
  • page_me
  • page_claim
  • registry_list_server
  • registry_adopt
  • free_tier_status
  • agent_create
  • product_get
  • product_checkout
  • purchases_mine
  • subscribe
  • subscription_status
  • tools_catalog

Connector log

2 connections on 4 November 2026, read-only methods only

  • 19:59:15Z https://rokha.ai/mcp/jsonrpc sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 2644 ms
  • 20:04:19Z https://rokha.ai/mcp/jsonrpc sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 2514 ms

Authentication

Auth typeNo authentication

The sign-in route, step by step

  1. Send the handshake to https://rokha.ai/mcp/jsonrpc over streamable-http. Servers on the 2026-07-28 revision answer server/discover; older servers answer initialize.
  2. Send tools/list, then resources/list and prompts/list if the capabilities name them.
  3. Send no token. The connector sent none and the server answered, so any MCP client can read this list.
  4. Calling a tool is a separate step this directory never takes.

See OAuth for MCP: client ID metadata documents and dynamic registration for how each route works.

CLI

No CLI is on record for Rokha. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See shipping a CLI agents can use.

Other agent surfaces

Agent surfaces other than MCP and CLI
SurfaceResult
OpenAPI fileNo OpenAPI file at the root paths checked.
WebMCP in the initial HTMLNot checked: the home page was not read by the shared crawl.
MCP discovery fileNot checked: the domain is not in the shared crawl for this edition.
A2A agent cardNot checked: the domain is not in the shared crawl for this edition.
A2A agent card (older path)Not checked: the domain is not in the shared crawl for this edition.
agents.jsonNot checked: the domain is not in the shared crawl for this edition.
OAuth authorization server metadataNot checked: the domain is not in the shared crawl for this edition.
NLWeb endpointNot checked in this edition.

Registry listings

Registry listings
RegistryListed
Official MCP RegistryYes: ai.rokha/rokha
GitHub MCP RegistryYes
awesome-remote-mcp-serversNo
SmitheryNot checked: Smithery's listing pages and search API were unavailable on 4 November 2026.
GlamaNot checked: Glama's API needs a key and attribution terms.