Sato Hub: Build Onchain & Crypto Agents
REMOTE · SATOHUB.AI · 2 COMPONENTS
Build any crypto agent: x402, ERC-8004, wallets. Does a server take your key? Hosted? Maintained?
Available components
Last scanned (15 hours ago)
Scores higher than 88% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 31997 tokens (~666/item across 48 items; 48 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 99% of tool parameters carry a description.Partial
- Structured output schemas are declared (4% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "onchain_agent_get_deploy_spec" implies "deploy" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Fail
- An AI judge read all 49 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Nov 26 0
- Tool “onchain_agent_build_plan” rewrote its description, which is the text the model reads security
- Tool “onchain_agent_route_swap” rewrote its description, which is the text the model reads security
- Tool “onchain_agent_join_passport” rewrote its description, which is the text the model reads security
- 18 Nov 26 0
- Tool “onchain_agent_check_install” rewrote its description, which is the text the model reads security
- Tool “onchain_agent_get_changes” rewrote its description, which is the text the model reads security
- “onchain_agent_get_changes” added an optional parameter “only” cosmetic
- 11 Nov 26 +1
- Stability: 0.97 → pass security
- 10 Nov 26 −1
- Stability: pass → 0.97 functional
- 9 Nov 26 +1
- Stability: 0.97 → pass security
- 8 Nov 26 −1
- Stability: pass → 0.97 functional
- 7 Nov 26 0
- Tool “onchain_agent_join_passport” rewrote its description, which is the text the model reads security
- “onchain_agent_join_passport” added an optional parameter “builder_stamp” cosmetic
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://satohub.ai/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.satohub.ai | CN=YR1,O=Let's Encrypt,C=US | 17 Nov 2026 | 15 Feb 2027 | RSA 2048 | SHA256-RSA | 6a5176edaa2f07ac7842e4416f515f2415d |
| SANs: *.satohub.ai, satohub.ai | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of satohub.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | DS published | 1814 | 8 | Verified |
| satohub.ai. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains |
| content-security-policy | frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://satohub.ai/api/mcp | Verified | 200 | |
| http (plaintext) | http://satohub.ai/api/mcp | HTTPS enforced | 308 | https://satohub.ai/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
onchain_agent_search_resources Find crypto-agent tooling by name, chain, standard or what it does ~1,587
USE WHEN you need to look up crypto-agent tooling (frameworks, MCP servers, wallets, payment rails, data tools) by name, chain, standard or what it does, or check that a specific project exists and is maintained. A daily-rebuilt directory, each entry scored from public evidence and linking to a citable page. NOT FOR a build goal in plain words such as "a trading agent on Base" (use onchain_agent_recommend_stack instead), a RUNNING agent to hire or pay (use onchain_agent_search_agents), a downloadable agent package (use onchain_agent_search_listings), what an agent skill touches (use onchain_agent_search_skills), or one record by slug (use onchain_agent_get_resource). `search` is the one-box version for ChatGPT deep research. RETURNS (json): { total, count, offset, has_more, next_offset?, resources: [...] }; each resource has chains, status, liveness, github_stars, verification_status and the marketplace fields (is_agent/is_hirable/is_licensable). Read-only. With NO argument it is a compact overview (rule "defaulted": complete rows, fewer, plus directory counts); detail: "full" is the full first page. FILTERS: query (free text, AND-matched terms), chain, status, liveness, featured, and the taxonomy facets (docs/taxonomy.md) entity_class, resource_type, use_case, standard and iface — closed vocabularies listed in the input schema: anything else is refused with the list, never answered with an empty result. 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. STARTING POINTS: a query asking for somewhere to start — "tutorial", "starter", "beginner", "template", "example", "docs" — returns starting points labelled as such: listings named as a starter or template first, then listings whose install Sato Hub reproduced, plus the wiki guides. "starter" / "template" / "x402 starter" also carry `templates`: a pointer to onchain_age…
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Filter to a resource category. |
| chain | string | – | Filter to resources supporting this chain. |
| creator | string | – | Filter by who built it (prefix match on creator name), e.g. 'Coinbase', 'Privy'. |
| deploys_as | string | – | Filter by deployment shape: npm, pip, docker, mcp server, hosted, self-hosted, cli, sdk, claude code plugin. |
| detail | string | – | 'full' returns the full first page (20 rows by default) even with no filter. Omitted with no other argument, the answer is a compact overview: the first rows in the default order, what the directory… |
| entity_class | string | – | Filter by class: 'resource' = things you build/deploy WITH (frameworks, tools, infra, venues, standards); 'agent' = curated, live onchain agents; 'reference' = editorial. |
| featured | boolean | – | True = only editorially featured resources. |
| iface | string | – | Filter by how it is accessed/integrated. One of: mcp, sdk, rest-api, plugin, cli, ui, contract. |
| integration | string | – | Filter to resources that integrate with a client or framework, e.g. 'claude code', 'cursor', 'langchain', 'openclaw'. Case-insensitive exact match. |
| is_agent | boolean | – | True = only resources that are themselves onchain agents. |
| is_harness | boolean | – | True = only agent frameworks/harnesses (OpenClaw, Codex, Claude Code…). |
| is_skill | boolean | – | True = only agent-skill resources (skill repos/marketplaces). |
| limit | integer | – | Max results to return (1-50, default 20). |
| liveness | string | – | Code activity (commit or release, not posts): Active ≤30d, Recent ≤90d, Quiet ≤1y, Dormant >1y. |
| mcp_answering | boolean | – | True = only listings whose MCP ENDPOINT answered Sato Hub's most recent MCP handshake (one check of ours, not uptime). Use this for 'which MCP servers answer'; min_observed_success alone is mostly a… |
| min_observed_days | integer | – | Minimum days of daily observation behind the success rate, counted in the rate window (default 14 when min_observed_success is set). |
| min_observed_success | number | – | Only listings whose share of Sato Hub's daily checks that succeeded is at least this percent, over at least min_observed_days (default 14). The rate and the days both count only checks in the rate wi… |
| offset | integer | – | Results to skip, for pagination (default 0). |
| query | string | – | Free-text search across name, description, tags, chains, and agent type. Space-separated terms are AND-matched. |
| resource_type | string | – | Filter resources by role. Venue = DEX/launchpad/marketplace; Network = an L1/L2. |
| response_format | string | – | Text format; structuredContent is JSON either way. |
| sort | string | – | Sort order: priority (default), newest_release, stars, or name. |
| standard | string | – | Filter to resources implementing a standard. One of: x402, erc-8004, erc-8183, mcp, a2a. |
| status | string | – | Filter by lifecycle status. |
| use_case | – | – | Filter by use case. One of: trading, payments, wallets, data, identity, privacy, launch, security, build, airdrops. |
| verified_only | boolean | – | True = only listings whose documented install was reproduced in a container by Sato Hub (deploy_status verified). Says nothing about runtime safety. |
No output schema declared.
No examples provided.
onchain_agent_search_skills Check what a crypto agent skill does before installing it ~526
USE WHEN someone is about to install an agent skill and should know what it will touch first: keys, credentials, remote scripts, outbound hosts. Crypto-relevant agent skills from ClawHub and skills.sh, each with a static DISCLOSURE: hosts it contacts, whether it generates or handles private keys, whether it asks the user to paste a credential, whether it pipes a remote script into a shell, whether it grants itself unrestricted tools, whether it registers the agent with a third-party host, whether it schedules itself. Each flag carries evidence lines on the skill's page. NOT FOR finding frameworks, MCP servers or wallets (use onchain_agent_search_resources instead), an npm/pip/MCP install command (use onchain_agent_check_install), or one skill's Preflight verdict (use onchain_agent_preflight with skill). RETURNS (json): { total, skills: [{ id, name, registry, canonical_url, installs, stars, disclosure_flags, hosts_contacted, declared_env, registry_scan, belongs_to_slug, skill_md_sha256, as_of }], note }. A disclosure is a description, not a safety verdict — a wallet skill that generates keys is doing its job, and no flags is not a clearance. The registry's own scan status is attributed to the registry. `slug` is the directory listing a skill targets: a slug that matches no skill comes back empty, and says whether it is a directory listing (onchain_agent_get_resource reads it), a wiki page or Sato Hub's own planner. Read-only. Cite https://satohub.ai/skills. Examples: - "solana skills that don't touch keys" -> { query: "solana" } then filter disclosure_flags - "which skills phone home" -> { flag: "registers_with_third_party" } - "skills for Coinbase AgentKit" -> { slug: "coinbase-agentkit" }
| Name | Type | Req | Description |
|---|---|---|---|
| flag | string | – | Only skills carrying this disclosure flag: pipes_remote_to_shell, executes_fetched_code, generates_or_handles_keys, solicits_credentials, reads_secret_paths, broad_tool_grant, registers_with_third_pa… |
| limit | integer | – | – |
| query | string | – | Free text over skill name, description, owner/repo and hosts contacted. |
| registry | string | – | Restrict to one registry. |
| response_format | string | – | Text format; structuredContent is JSON either way. |
| slug | string | – | Only skills that target this directory listing. |
No output schema declared.
No examples provided.
onchain_agent_submit_project Submit a project to the Sato Hub directory ~646
USE WHEN an agent has found, built or maintains a crypto-agent project that is not in the directory and wants it considered. NOT FOR correcting a listing that already exists (that goes through the claim flow on its page), checking whether a project is listed (use onchain_agent_search_resources first), or registering a running agent (use onchain_agent_register_agent). This WRITES: it files the same row the /submit form files, into the same queue, and the daily triage run evaluates it through the same single apply path — probe the public evidence, validate against the listing schema, list it or hold it or decline it with a reason. WHAT HAPPENS NEXT: the website, the repository and any declared endpoint are probed from public sources. A project that clears that evidence is listed; one that does not is held for a person, or declined with the reason. If `contact_email` is given you get exactly ONE email, and only if it is listed. A hold sends nothing — silence means a person is looking. SUBMISSION IS NOT VERIFICATION. It is a request to be looked at. Being listed says what was observed about a project on a date, not that it is safe, audited, profitable or endorsed. Copy carrying profit, safety or risk claims is refused here rather than quietly cleaned up. DEDUPE: the website host and the repository are checked against the live directory and against submissions already waiting. A match returns that existing entry instead of filing a second row — correcting a listing that already exists goes through the claim flow on its page, which proves control of the domain first. LIMIT: 5 write calls an hour per caller. Nothing is written when it trips. RETURNS (json): { ok, duplicate, submission_id | slug, next, caveat }. Example: { name: "Example Agent Kit", website_url: "https://example.dev", repo_url: "https://github.com/example/kit", category: "Agent Framework", description: "A TypeScript toolkit for wiring agents to Base with viem and an MCP server.", chains: ["Base"] }
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | The directory category it belongs in. Pick the closest; triage corrects it if you are wrong. |
| chains | array | – | Chains it supports, by display name, e.g. ['Base','Solana']. |
| contact_email | string | – | Where the one approval reply goes. Optional — without it nothing is ever sent, and there is no other notification. |
| description | string | yes | What it does, in plain words: what it is, who it is for, what it connects to. No profit, safety or performance claims — they are refused at the door. |
| name | string | yes | The project's name, as its own site writes it. |
| repo_url | string | – | The public source repository, when there is one: github.com/<owner>/<name>. |
| response_format | string | – | Text format; structuredContent is JSON either way. |
| website_url | string | yes | The project's own https site. Not a GitHub URL unless the repository IS the project's home. |
No output schema declared.
No examples provided.
onchain_agent_swap Quote a swap, check it against a policy, and get an unsigned transaction ~1,756
USE WHEN an agent is about to swap and wants the venue chosen, the fee disclosed, and the trade CHECKED before anything is signed. Two modes: `recommend` returns the choice, the fee sentence and the verdicts and NEVER a transaction; `build-tx` returns an UNSIGNED transaction, and only when the gate allowed it and a simulation did not revert. `build-tx` WRITES a receipt row. NOT FOR a plain quote with no policy gate (use onchain_agent_route_swap instead), a token launch (use onchain_agent_route_launch), or a liquidity pool (use onchain_agent_route_lp). NON-CUSTODIAL: this tool NEVER signs, holds, moves or broadcasts funds, and it never asks for a key. What comes back is an unsigned object the caller signs or discards. The response signature proves Sato Hub produced those bytes; it is not a claim that anyone authorised a transfer. WHAT IS CHECKED, and under what: four targets — token_in, token_out, the venue endpoint, and the recipient — each with its own verdict, the rule id that produced it and the reason. Then the caller's policy (caps per trade and per period, allowed chains, tokens, venues, recipients, slippage and deadline). Manage policies at https://satohub.ai/api/swap/policies; with no stored policy the default applies. UNKNOWN REFUSES BY DEFAULT. A target we could not read, or a simulation that could not run, WITHHOLDS the transaction unless the policy says otherwise — and the response says which lane could not be read. "We did not check" and "we checked and it is fine" never look alike. A refusal is an ANSWER: it is not an error, and retrying it unchanged will refuse again. A COUNTERPARTY WITH NO PASSPORT IS `no_record`: the ordinary case, not a finding against the address. wallet_verified proves control of a key, never anything about the product behind it. There is no list of trusted counterparties here. THE FEE: disclosed verbatim in `disclosure`, per venue, before anything is signed. A trade that is never signed pays nothing. `sato_fee_side` ("in"…
| Name | Type | Req | Description |
|---|---|---|---|
| amount_in | string | yes | Sell amount in the INPUT token's base units (1000000 = 1 USDC at 6 decimals). A string, because a uint256 does not survive a JSON number. |
| chain_in | string | yes | Source chain as the directory writes it. The agent bots swap on Base, BNB Chain, Arbitrum, Polygon and Solana; a short spelling ('bnb', 'bsc', 'matic', 'arbitrum one') is read as the same chain, and… |
| chain_out | string | – | Destination chain. Omit, or repeat chain_in, for a same-chain swap. A different value is the cross-chain lane, and the two lanes are never compared with each other. |
| deadline | integer | – | Unix seconds the quote should stay good until. Omit for the venue's own default. |
| mode | string | – | `recommend` (default) never returns a transaction, whatever the gate said. `build-tx` returns an unsigned one, and only when the gate allowed it AND the simulation did not revert. |
| recipient | string | – | Where the output goes. Omit to send to the taker. A recipient we hold no record of is `no_record` — an absence of evidence, and on its own never a refusal. |
| recipient_owner | string | – | The caller declares `recipient` is ITS OWN address on `chain_out`. Sato Hub does not check that. Read only on a cross-chain `build-tx` (rule RCPT5: the look-alike and mark checks still run first); ig… |
| referrer | string | – | Optional referral: a referral name (like sunny-otter) or a payout address (a Base 0x address or a Solana address) that earns 30% of the Sato fee on this swap, paid weekly in USDC once Sato Hub has re… |
| response_format | string | – | Text format; structuredContent is JSON either way. |
| slippage_bps | integer | – | Slippage tolerance in basis points, passed through to the venue. A policy may cap it, and then the refusal states the cap and the value. |
| taker | string | – | The address that would sign. Some venues only return a transaction when it is given; nothing is ever signed here. |
| token_in | string | yes | Input token: a contract address (or Solana mint), or a symbol for the well-known stablecoins. |
| token_out | string | yes | Output token: a contract address (or Solana mint), or a symbol. |
| usd_notional | number | – | USD notional of amount_in, when YOU already hold a price. Omitted is unknown, never zero — a USD cap simply does not bite without it. |
| venue | string | – | Pin ONE venue. Only it is quoted; if it cannot answer, is not offered on the chain or is refused, the reply names it and says why, and no other venue is tried. Omit and the chooser ranks every venue… |
No output schema declared.
No examples provided.
onchain_agent_watch Watch a repo, package, endpoint or agent for a Preflight verdict change ~551
USE WHEN an agent (or the person it works for) wants to be told if something in its stack stops checking out — rather than re-running a Preflight on a schedule of its own. This WRITES one subscription row. NOT FOR a one-off check now (use onchain_agent_preflight instead) or a record's change history (use onchain_agent_recent_changes). Goes through the SAME path the public form uses: same validation, same normalisation, same rate limit, one row per address and target. WHAT HAPPENS: the target is re-checked once a day by the public Preflight path, and an email is sent ONLY when the verdict CHANGES. Never on a schedule, never a digest. A transition INTO `unknown` (a check that failed to run) is recorded and never mailed — a failed check is not news about the target. wallet: get told when Sato Scan sees address poisoning aimed at that wallet. FREE WHILE IN PREVIEW. No price is set and no payment is taken. WHAT IS STORED: the normalised target, the address (a notice has to be delivered), an HMAC of it for counting, and the baseline verdict. No IP address and no name. Asking twice is idempotent; `action: "unsubscribe"` stops the mail and answers the same way whether a row existed or not. RULE ENFORCED: a verdict describes what was checked and when. It is not a safety, security or returns judgment, and a CHANGE is a change in what was observed — not a warning. RETURNS (json): { ok, action, target_kind, target, watch_id, verdict, notice, caveat }. Example: { target_kind: "package", target: "solana-agent-kit", notify_to: "me@example.com" }
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | subscribe (default) arms the watch; unsubscribe stops the mail for this address and target. |
| notify_to | string | yes | The email address the change notice goes to. Stored once for delivery and counted by an HMAC; it never enters telemetry or logs. |
| response_format | string | – | Text format; structuredContent is JSON either way. |
| target | string | yes | The thing itself, in the spelling that kind takes. It is normalised, so two spellings of one repository become one watch. |
| target_kind | string | yes | What is being watched: repo (owner/name or a GitHub URL), package (npm name), endpoint (an https URL), agent (an ERC-8004 reference like 'base:42'), wallet (<Chain>:<address>, e.g. 'Base:0x...'). |
No output schema declared.
No examples provided.
search Search Sato Hub ~264
USE WHEN you want one query box over Sato Hub, the daily-rebuilt index of what onchain and crypto AI agents are built from (frameworks, MCP servers, wallets, x402 and stablecoin payment rails, data tools), plus its dated answers, agent-economy numbers and wiki. Not for token prices, trading or investment advice. NOT FOR filtered or paginated directory queries (use onchain_agent_search_resources instead) or registered agents (use onchain_agent_search_agents). RETURNS (json): { results: [{ id, title, url }] }, at most 10, best first, from one query string; url is the canonical satohub.ai page to cite. Pass an id to `fetch` for the full text. A query nothing matches returns results: [] — never padded with unrelated records — plus scope_note, what Sato Hub covers. Read-only. Examples: "coinbase agentkit", "x402 payment rails on Base", "how many ERC-8004 agents by chain", "MCP servers that answer".
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | What to look for, in plain words: a project name, a chain, a standard, or a question about building onchain agents. Matched on its first 200 characters. |
| Name | Type | Req | Description |
|---|---|---|---|
| about_url | string | – | Only with identity_note: the satohub.ai page that says what Sato Hub is. |
| example_calls | array | – | With needs_input: exact calls that would work. |
| identity_note | string | – | Only when a search for the Sato name itself matched nothing: Sato Hub's no-token statement. Not a result. |
| interpretations | array | – | Only when more than one reading applied: every label, the first being interpreted_as / rule. |
| interpreted_as | string | – | Only when the call was read another way (a tool name, the arguments' form): what was served. |
| needs_input | boolean | – | Only when the call lacked its required argument: nothing was served; note says what to send. |
| note | string | – | With interpreted_as or needs_input: one sentence saying what was read, or what to send. |
| requested | string | – | Only with interpreted_as: what was sent. |
| results | array | yes | At most 10 matches, best first. Empty when nothing matches — never padded. |
| rule | string | – | Only with interpreted_as: which reading (format-variant, param-alias). |
| scope_note | string | – | Only when nothing matched: what Sato Hub covers and how to ask it. Not a result; results stays empty. |
| suggestions | array | – | Where to go next (a tool to call, or a candidate id to fetch). Suggestions, never matches. |
No examples provided.
How do I install the Sato Hub: Build Onchain & Crypto Agents MCP server?
Sato Hub: Build Onchain & Crypto Agents is a hosted endpoint at https://satohub.ai/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · satohub.ai
claude mcp add --transport http ai-satohub-onchain-agents 'https://satohub.ai/api/mcp'
What is the Sato Hub: Build Onchain & Crypto Agents MCP server?
Sato Hub: Build Onchain & Crypto Agents is an MCP server listed in the public MCP registry as ai.satohub/onchain-agents. Build any crypto agent: x402, ERC-8004, wallets. Does a server take your key? Hosted? Maintained? This page covers its hosted endpoint (https://satohub.ai/api/mcp).
Is the Sato Hub: Build Onchain & Crypto Agents MCP server safe to use?
Sato Hub: Build Onchain & Crypto Agents scores 86 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Sato Hub: Build Onchain & Crypto Agents MCP server expose?
Sato Hub: Build Onchain & Crypto Agents exposes 48 tools: onchain_agent_search_resources, onchain_agent_get_resource, search, fetch, onchain_agent_get_deploy_spec, and 43 more. Their descriptions and schemas cost roughly 31,542 tokens of context every time the server is loaded.
Does the Sato Hub: Build Onchain & Crypto Agents MCP server require authentication?
No. We connected to Sato Hub: Build Onchain & Crypto Agents without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Sato Hub: Build Onchain & Crypto Agents MCP server still maintained?
Sato Hub: Build Onchain & Crypto Agents is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Sato Hub: Build Onchain & Crypto Agents MCP server?
VerifyMCP ran 13 checks on Sato Hub: Build Onchain & Crypto Agents, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.