Rokha

安装

选择你使用的 AI 应用，然后复制设置。

通过 4/4 项检查 · 你的提问会经过开发者的服务器（rokha.ai） · ✓ 命令已检查 2026年11月13日

claude mcp add --transport http --scope user rokha https://rokha.ai/mcp/jsonrpc

{
  "mcpServers": {
    "rokha": {
      "url": "https://rokha.ai/mcp/jsonrpc"
    }
  }
}

{
  "servers": {
    "rokha": {
      "type": "http",
      "url": "https://rokha.ai/mcp/jsonrpc"
    }
  }
}

哪些应用可以使用它

依据这个服务器的连接方式和各应用自己的文档，检查于 2026年11月10日。

通过互联网连接，适用于

ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast

全部应用及其优缺点 →

它能做什么

工具名称和描述与服务器在 2026年11月13日 报告的完全一致。这些内容由作者撰写，不是我们写的；我们以纯文本形式显示。

• 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: give it one lead — a link (site, docs page, API or MCP endpoint, an x.com post = its author), an X @handle, a domain, gh:owner/repo, npm: , pypi

• x_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 promotional-worth anchor in X-algorithm engagement units (reply 13.5 · quote 1.5 · repost 1.0 · like 0.5). Hard metrics from X's own numbers: engagemen

• send_agent_message

  Send a message to a Rokha agent (default 'rokha-agent') and get its reply. With a logged-in identity (Authorization: Bearer ) the agent acts AS you — it can run your rigs (rig_run), read your saved keys/OAuth grants, and spend your budget; anonymous callers get general chat only.

• registry_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/stats), by free-text query. Returns name, slug, provider, author, version, downloads, and description for each match. A UUID query is an exa

• registry_get_skill

  Fetch everything an agent needs to adopt a Registry skill: the full SKILL.md (agentskills.io standard — frontmatter name/description + body), its classification (prompt-shaped vs scripted vs mcp), and required binaries. To install: save the returned skill_md as SKILL.md inside a

• rig_search

  List YOUR saved rigs, newest first, optionally narrowed by `query` (matches the name/summary). This is how an agent RECOVERS: rig_author returns an id, but an agent that runs across sessions will not still be holding it, and without this it could only ever re-author from scratch

• rig_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 saved rather than against what you remember authoring, and after a run to check the rig is shaped the way you think it is. Owner-scoped. Require

• trace_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, and the trace is where the answer lands. Without it an agent can run a rig and never learn whether it worked, which makes the run untestable. F

• rig_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 on demand, and so never test the thing it just built. Name the rig by `rig_id` (one you own or adopted) OR by `provider_id` + `external_id` (

• skill_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, numbers, single hyphens, ≤64 chars); a `description` stating WHAT it does AND WHEN to use it, third person, with concrete trigger words (the fiel

• auth_resolve

  The AUTH LADDER: classify any MCP server URL — 'open' (no credential), 'key' (paste a token into the vault once), 'tier1' (one-click account-wide Connect for a known provider), or 'oauth_spec' (the MCP auth spec — connect directly, approve in a browser). Returns the one right nex

• rig_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_type` linear | dag (default) | stateful_graph (loops with guarded edges; an unfired guard skips its target). A step with no binding is a model

• trace_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, every trace). Signed in (Authorization: Bearer ): your own traces. No token: a PUBLIC rig's run is readable by anyone holding its trace id or ru

• registry_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 (Authorization: Bearer ); the listing is owned by the verified caller and the display author is derived server-side (your claimed page's display

• auth_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's private key. Works for Solana (base58 Ed25519 address) and EVM (0x address). Follow with auth_wallet_verify. New wallets are auto-register

• auth_wallet_verify

  Step 2: submit the signed challenge. On success returns session_token — a JWT to send as `Authorization: Bearer ` on every subsequent MCP/API request, unlocking the owner-scoped tools (page_claim, create_harness, rig_author, registry_publish, schedules, …). Solana: Ed25519 signat

• studio_doors

  WHAT ROKHA COSTS. Rokha is the Agent Runtime and Marketplace — build tools, run them for real, sell or hire them. No platform payouts. THREE RUNGS: FREE, signed in (an agent signs in with a wallet over MCP) — 5 runs a day of tools on Rokha's runtime, model steps on your own key;

• market_search

  THE MARKET (rokha.ai/market, GET /api/market) — everything you can run on Rokha in one store: Rokha-native rigs, skills, MCP servers, agents, builders and marketers, plus the whole synced open registry (the public skill and MCP registries), one order: proven first, then most used

• mark_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 deep read on any mark: a Solana contract address (or a pump.fun / DexScreener / Solscan / Birdeye link naming one), an X @handle or x.com lin

• page_me

  YOUR page as the logged-in identity sees it. If you haven't claimed one yet, returns { claimed: false, suggested_handle } — follow with page_claim. Carries your linked X account too: `x_handle` (the connected @handle), `x_verified_type` ('blue'/'business'/'government' or ''), `x_

• page_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 verified caller. handle: lowercase letters/numbers/-/_ , ≤32 chars; display_name ≤80; bio ≤600; glyph: 1-2 chars shown as your mark (a profi

• registry_adopt

  The select → input → run door: materialize YOUR OWN runnable copy of any published rig listing (find provider_id + external_id via registry_search; the listing must carry a metadata.rig skeleton). Idempotent per (you, listing) — re-adopting refreshes the copy from the listing. Re

• 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 questions a day — the same taste signed in) and read everything public — the Market, every listing, public runs and traces, finished hunts a

• 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 checks as building an agent on rokha.ai: name + handle (lowercase letters, numbers, - and _, ≤32; reserved names and taken handles refused),

• product_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/harness), by agent_handle (an agent), or by kind + ref. A pack is kind 'pack' + ref = the pack id. Returns {product:{id,title,model: one_time|mont

• product_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 USDC, payTo, maxAmountRequired — the exact amount binds the payment to your order); transfer that USDC, wait for finality, then call again wit

• purchases_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, full access to everything: the runtime, the Lab, 300 runs a day (model steps on your own model key) — for YOURSELF; it never names another acc

• subscription_status

  Requires a JWT or an rk_ key. Read-only. Your own access: studio (true = full access), access (rent | holder | house | none …), current_period_end, tier, full_access, and the ladder — free runs a day, the run pack (product_id, price, how to buy) and the Lab month (subscribe). fre

• tools_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 toolsets with counts. `query`: words matched against every tool's name, title and description — one line per hit (name · title · toolset). `tools

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月14日

• ✓ 通过

  作者与仓库一致

  注册名称已通过域名 rokha.ai 验证（注册中心会核实域名所有权）

• ✓ 通过

  仍在维护

  代码最后更新于昨天

• – 不适用

  有许可证

  不适用：由 rokha.ai 的所有者自己运行的云端服务器，你不会运行仓库里的代码

• ✓ 通过

  端点有响应

  在 469 毫秒内响应（HTTP 200）

• – 不适用

  使用 OAuth 登录

  无需登录

• ✓ 通过

  工具描述中没有隐藏指令

  已读取 30 个工具描述，未发现针对 AI 的隐藏指令

用户评价

还没有评价

用 Google 登录后写评价

与“搜索与 AI 记忆”中的其他服务器比较i

• 星标数多于此分类中其他 6070 个服务器的 76%
• 发布到注册中心的时间比此分类中其他 6070 个服务器的 44% 更新
• 基础检查结果等于或优于此分类中其他 6070 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

同类别的其他选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：↓ 每周下载量i★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Context7

Up-to-date docs for AI agents

作者：upstash·广泛使用·↓ 125万/周·★ 6.5万·前天更新

电脑或云端

安装

Codebase Memory

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

作者：DeusData·广泛使用·↓ 1.7万/周·★ 4.9万·28天前更新

在你的电脑上运行

安装

Ruflo

Agent teams, swarms, memory and hooks for Claude Code and Codex, served over MCP.

作者：ruvnet·广泛使用·↓ 7.4万/周·★ 8.2万 整个仓库的星标·昨天更新

在你的电脑上运行

安装

作者的 README

claude mcp add --transport http rokha https://rokha.ai/mcp/jsonrpc

import { RokhaClient } from '@rokha_ai/sdk';