Sato Kit MCP server
ai.satohub/kit·v0.1.0Prepare -> execute for onchain agent actions: policy pre-flight, simulation, receipt log.
0 stars61 downloads/wk
Reviews
Write oneNobody has reviewed Sato Kit yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Sato Kit tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.10 · 2026-10-01 · same rubric, same numbers if you re-run it
- Code scan151 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 1 days ago15/15
- Maintainer identitynamespace and repository owner differ; website matches verified namespace5/10
How Sato Kit compares
Against every graded AI and agents MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 88/100
- higher than 80% of 4,460 AI and agents servers
- Downloads a week
- 61
- more than 50% of 1,538 AI and agents servers with a package
Install Sato Kit in Claude Code, Cursor or VS Code
Runs npx -y @satohub/kit on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add kit -- npx -y @satohub/kit
What the publisher says
From the Sato Kit repository's README, as published. We do not edit it. Read it on GitHub
Sato Hub integrations
⬡ Sato Hub inside the agent frameworks people already run.
Sato Hub indexes what onchain agents are built from — agent frameworks, MCP servers, wallets and key management, x402 and stablecoin payment rails, ERC-8004 identity, trading venues, onchain data, agent skills — rebuilds the index daily from public evidence, and scores every listing on how open, active and verifiable it is.
This repository packages four of those calls for the agent frameworks below, so an agent can reach them without anyone writing a fetch wrapper first.
Two of those rows are deliberately not packages. Both SDKs speak MCP, and Sato Hub serves MCP; a package between them would be a wrapper around a URL.
The four calls
All four are read-only. All 32 MCP tools are at https://satohub.ai/mcp if you want the rest.
What these packages do, and do not
They wrap. They never re-implement. No scoring, ranking or verdict logic lives in this repo. Sato Hub decides; these packages carry the answer and check the signature on it.
The payload comes back verbatim. Every tool returns the record as Sato Hub sent it, with provenance beside it and never folded into it — so nothing the model reads has passed through a summariser of ours.
Responses are verified. Preflight verdicts and Sato Route decisions leave satohub.ai with a detached Ed25519 signature. satohub-core fetches the JWKS, verifies the raw bytes, and by default throws when a signature is present and does not match. An unsigned response is reported as unsigned — unknown, not invalid. We never emit a placeholder signature and this code never invents one. (the scheme)
Non-custodial, everywhere. Nothing here signs a transaction, holds a key, deploys or moves funds. A swap tool returns a quote and calldata for the caller to read and sign with its own signer. An unsigned route costs nothing. The Sato fee — 3 bps stable-to-stable, 15 bps on any volatile leg — is stated in the response before anything is signed, including when it is zero.
The readings, and their limits
These are in every tool description, because a tool description is the part a model actually reads:
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Sato Kit: common questions
- Is Sato Kit MCP server safe?
- Yes, by our scan: it is graded A (88/100). Read the Sato Kit safety report
- How do I install Sato Kit?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Sato Kit need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Sato Kit maintained?
- The last commit was 35 days ago (2026-09-30). The latest release is v0.1.0.
- What can I use instead of Sato Kit?
- Servers from other publishers that do the same job: Emilia Protocol MCP server, three.ws Provenance MCP server and Decionis MCP server.
- How does Sato Kit compare with other AI and agents MCP servers?
- safety score 88/100 (higher than 80% of 4,460 AI and agents servers); downloads a week 61 (more than 50% of 1,538 AI and agents servers with a package). Full comparison.
Alternatives to Sato Kit
Same job from other publishers: the closest match first, then the best rated.
- Emilia ProtocolExact-action approval for consequential agent actions: request, track, and verify signed receipts.not reviewedEstablishedB
three.ws ProvenanceAppend-only, signed, on-chain-verifiable agent action log — record and audit what agents did.not reviewedEstablishedB- DecionisAuthorize consequential AI agent actions before executionnot reviewedEstablishedA
- Agent-Native ChatMinimal chat-first app with durable threads, actions, and the app-agent loopnot reviewedEstablishedA
Agoragentic Agent OS MCPTriptych OS (Agent OS) MCP for governed routing, receipts, and USDC settlement on Base.not reviewedEstablishedB
