mcpbeat

Sato Hub: Onchain Agents MCP Server

io.github.satohubai/onchain-agents
not responding

Sato Hub: Onchain Agents is listed as active in the registry but did not answer our last check. It exposes 13 tools. Last commit 3 Aug 2026.

Search scored onchain agent frameworks, MCPs, wallets, tools, and live agents.

Uptime history 39 hours of history · worst hour 0%
39 hours agonow
0.0%
Uptime 24h
0 of 91 checks
13
Tools
read from the server
222 ms
Response time
average over 24h
1
Stars
last commit 3 Aug 2026

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 4 min ago.

run in your terminal
claude mcp add onchain-agents --transport http https://satohub.ai/api/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "onchain-agents": {
      "url": "https://satohub.ai/api/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.onchain-agents]
url = "https://satohub.ai/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "onchain-agents": {
      "url": "https://satohub.ai/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "onchain-agents": {
      "url": "https://satohub.ai/api/mcp"
    }
  }
}

Available tools 13

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

onchain
onchain_agent_get_agent_passport
Get the full Sato Agent Passport manifest (sato.agent.manifest/v1) for one REGISTERED agent by slug: identity (sato_agent_id), agent types, chains, model/framework, the stack of Sato Hub directory resources it runs on, links, payment/x402 endpoint metadata, and verification + liveness status. Use onchain_agent_search_agents to find slugs. Payment metadata is self-configured by the creator — published for interoperability, not as an endorsement. Returns an error if the slug is unknown or the agent is not listed. Read-only. Example: { slug: "my-trading-agent" }
onchain_agent_get_deploy_spec
Get the structured deploy manifest for one resource by slug — the essential, install-and-instantiate information an agent needs to BUILD from it: runtime, install command(s), entry snippet, required keys/env/wallet/RPC, chains, license, whether it is itself an MCP server, and a deploy_status. deploy_status is a trust signal, NOT a safety guarantee: "verified" = the install path was reproduced/confirmed from the project's docs; "self_reported" = parsed from the project's README and not independently reproduced. Always verify keys, permissions, and funds before running anything. Returns (json): { slug, name, github_url, docs_url, deploy_spec: { runtime, install[], entry, requires[], chains[], license, mcp_native, mcp_invocation?, deploy_clarity, deploy_status, source_url, as_of }, note }. Returns an error if the resource has no manifest yet (they are being rolled out resource by resource). Read-only. Example: { slug: "solana-agent-kit" }
onchain_agent_get_metrics
Get live ecosystem metrics: the ERC-8004 Identity Registry registered-agent count (read from Ethereum mainnet) and the curated Top Project Tokens index (only tokens of directory-listed projects — never the whole agent-token category or its aggregate market cap). Returns (json): { erc8004: { network, registered_agents, live, checked_at }, top_agent_tokens: [{ symbol, name, current_price, market_cap, price_change_percentage_24h, resource_slug }] }. Read-only.
onchain_agent_get_news
Get the Onchain Agent news feed — official releases (GitHub), announcements (project X posts), and reputable RSS. Strongly filtered to the agent economy. Filter by kind (release/tweet/news/research) and/or chain; paginate via limit/offset. Returns (json): { total, count, offset, has_more, next_offset?, news: [{ kind, title, summary, url, source, author_handle, chains, resource_slug, published_at }] }. Read-only. Example: { kind: "release", limit: 10 }
onchain_agent_get_resource
Get the full record for one directory resource by slug, optionally with its recent activity feed (releases/posts). Use onchain_agent_search_resources first to find a slug. Returns (json): { resource: {...full record incl. marketplace + liveness fields}, recent_activity: [...] }. Returns an error if the slug is unknown or the resource is Deprecated. Read-only. Example: { slug: "coinbase-agentkit" }
onchain_agent_get_wiki_page
Get a full Onchain Agent wiki page by slug — an editorial explainer (summary, why it matters, how it works, key components, examples, risks, related resources/pages). Use onchain_agent_list_wiki_pages to find slugs. Returns (json): the full page object. Returns an error if the slug is unknown. Read-only. Example: { slug: "what-are-mcps" }
onchain_agent_list_categories
List all resource categories with counts, most populated first. Useful before filtering onchain_agent_search_resources by category. Returns (json): { total, categories: [{ name, count }] }. Read-only.
onchain_agent_list_chains
List all blockchains represented in the directory with resource counts, spotlight chains first (Base, Ethereum, Solana, COTI, Injective…). Returns (json): { total, chains: [{ name, count }] }. Read-only.
onchain_agent_list_wiki_pages
List all Onchain Agent wiki pages (slug, title, keyword, summary, last_updated). Returns (json): { total, pages: [...] }. Read-only.
onchain_agent_recent_changes
Get recorded changes across the directory — the auditable Listing History. Omit slug for the SITE-WIDE feed (what changed across all listings); pass slug for ONE resource's history. Events: status flips, verification grants, Sato Score tier moves, liveness (a project going dormant or active again), new releases, and field enrichment. Derived from the daily snapshot time-series + the change-event log; high-signal only (passive score/liveness drift is suppressed). Returns (json): { scope, total, changes: [{ date, kind, slug, name, title, detail?, tone }] }. tone is positive | negative | neutral. Read-only. Example: { days: 7 } · { slug: "coinbase-agentkit" }
onchain_agent_recommend_stack
Given a goal in plain words, returns a trust-ranked stack of directory resources to build it with — bucketed into slots (framework, wallet, payments, trading, data, MCP tooling, security), each pick carrying its Sato Score, liveness, and deploy-spec status, plus honest gaps where the directory has no strong match. Ranking reflects openness/activity/verifiability — never a safety, quality, or returns judgment. Read-only. Example: { goal: "trading agent on Base with x402 payments", chain: "Base" }
onchain_agent_search_agents
Search REGISTERED onchain agents in the Sato Agent Registry — running agents whose creators registered them for a Sato Agent Passport (distinct from the resource directory, which lists the things agents are built FROM). Filter by free-text query, chain, agent_type, or x402_only. Only human-review-listed agents are returned. Trust rule: registration is self-reported by the creator; verification_status distinguishes Self-Reported from evidence-reviewed Verified/Audited. Nothing here implies safety or performance. Returns (json): { total, agents: [{ sato_agent_id, slug, name, description, agent_type, chains_supported, stack, payment/x402 metadata, verification_status, profile_url, manifest_url }] }. Read-only. Example: { chain: "Base", x402_only: true }
onchain_agent_search_resources
Search the Onchain Agent directory of onchain agents, frameworks, skills, and tooling. Filters: query (free text, AND-matched terms), chain, status, liveness, featured, and the taxonomy facets (docs/taxonomy.md): entity_class (resource | agent | reference), resource_type (Framework | Tool/Service | Infrastructure | Venue | Network | Standard), use_case (trading, payments, wallets, data, identity, privacy, launch, security, build), standard (x402, erc-8004, …), iface (mcp, sdk, …). Legacy flags still work: category, is_agent, is_skill, is_harness. Sort by priority (default), newest_release, stars, or name. Paginates via limit/offset. Deprecated resources are never returned. Returns (json): { total, count, offset, has_more, next_offset?, resources: [...] } where each resource includes chains, status, liveness, github_stars, verification_status, and the marketplace fields (is_agent/is_hirable/is_licensable). Read-only. Examples: - "Active hirable agents on Base" -> { chain: "Base", is_agent: true, liveness: "Active" } - "newest releases" -> { sort: "newest_release", limit: 10 } - "wallet tooling" -> { query: "wallet" }

Endpoints

URLTransportStateLatencyChecked
https://satohub.ai/api/mcp streamable-http answering 222 ms 4 min ago

Sato Hub: Onchain Agents — questions

Answers built from our own checks of this server.

What can Sato Hub: Onchain Agents do?
It exposes 13 tools, read directly from the server on our last check. Among them: onchain_agent_get_agent_passport, onchain_agent_get_deploy_spec, onchain_agent_get_metrics, onchain_agent_get_news, onchain_agent_get_resource, onchain_agent_get_wiki_page and 7 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Sato Hub: Onchain Agents working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 91 checks got a reply (0.0%), average response time 222 ms. The bar chart above shows every period we have measured.
The registry lists Sato Hub: Onchain Agents as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Sato Hub: Onchain Agents?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Sato Hub: Onchain Agents need an API key?
No. Sato Hub: Onchain Agents completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 13 of them are readable on this page. This is what we observed, not what the docs claim.
Is Sato Hub: Onchain Agents open source?
Yes — it is published under the NOASSERTION licence, written in JavaScript and 1 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.