Sato Kit

Name: Sato Kit
Author: satohubai

by satohubaiversion 0.1.0i★ –iRuns on your computer

Registry nameai.satohub/kit

Install

Overview

Description from the maker (original English)

Prepare -> execute for onchain agent actions: policy pre-flight, simulation, receipt log.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "kit": {
      "command": "npx",
      "args": [
        "-y",
        "@satohub/kit",
        "mcp"
      ]
    }
  }
}

Run this in your terminal

claude mcp add kit -- npx -y @satohub/kit mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "kit": {
      "command": "npx",
      "args": [
        "-y",
        "@satohub/kit",
        "mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "kit": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@satohub/kit",
        "mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

✓ Pass
Maker matches the repo
The registry name was verified against the domain satohub.ai (the registry checks domain ownership)
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 32489 servers in this category
Published to the registry more recently than 52% of the other 32489 servers in this category
Basic checks equal to or better than 100% of the other 32489 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Sato Kit safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.0) reached the registry 38 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Whisper

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday

Install

Whisper

by whisper-sec

One routable IPv6 per AI agent, verifiable from the DNS root. Keyless tools need no signup.

Computer or cloudUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

@satohub/kit

0.1.1 preview.

Sato Kit wraps the tools agents already use (viem, signers, x402) with a prepare -> execute contract: an action prepares an unsigned intent, a policy pre-flight explains any refusal, the transaction is simulated, and execute({ intent_id }) hands it to your signer and appends a hash-chained sato.receipt/v1 line.

What it is not: not a wallet, not a custodian, not an agent framework, and not a guarantee. It never holds funds and ships no keys.

Fork by default. A policy's network defaults to fork; mainnet needs an explicit opt-in.
Pre-flight vs enforcement. The kit's policy check runs before an intent is returned and says which rule refused and why. It does not enforce anything once a key is in play. Enforcement lives in the signer (e.g. a CDP policy compiled from the same file).
`scan.payto_changed`. The scan block of policy.json records payto_changed (caution | refuse | off), but it is enforced only by hosts that implement it. The offline guard in satohub-core (scanRecipient) does not enforce it today: a changed x402 payTo needs the payee's earlier value, which the offline check is not given.
Swaps are venue-neutral. Any venue is accepted. Sato Swap is the labelled default and its fee is disclosed on every response, with a no-Sato-fee quote alongside; venue: "direct" skips Sato entirely.

Contracts (sato.action/v1, sato.policy/v1, sato.receipt/v1) live in src/spec (see VENDORED.md).

Install

npm install @satohub/kit viem

npx -y @satohub/kit@0.1 --help

Node 20 or later. viem is a peer; every framework SDK below is an optional peer, installed only if you use its subpath.

Honest limits

Pre-flight, not enforcement. evaluatePreflight runs before an intent is returned and names each refused rule with its limit and the observed value. Once a key is in play the kit enforces nothing: enforcement is the signer's (a CDP, Privy or Turnkey policy compiled from the same policy.json, OWS's policy engine, or a Safe's owners). viemLocalSigner enforces only its mainnet refusal.
x402 execution scope. x402.prepare reads what an x402 resource asks to be paid and returns a priced, policy-checked intent. execute does not send x402 payments: it sends EVM transactions, EIP-712 typed data (Safe proposals) and Solana transactions only. Pay through your x402 client.
AgentKit's own analytics call. AgentKit's @CreateAction decorator posts an invocation event to cca-lite.coinbase.com on every invoke. Actions consumed through fromAgentKitProvider still make that call; the kit neither blocks nor adds to it.
Unknown prices refuse. When a USD value cannot be read, a max_usd_* rule refuses with unknown_price rather than guessing.
Simulation is not a promise. A passing simulation says what the chain answered at that block.

Action reference

Generated from the registered descriptors by node scripts/gen-actions-doc.mjs (after npm run build); test/readme-actions.test.ts fails when this table drifts from the registry. "custody" is the descriptor's own answer to three sato.custody/v1 questions. toolset says whether the tool is in the default MCP profile or only under --toolsets all.

Registered actions

action id	tool name	kind	effects	custody	chains	toolset
`chain.read`	`chain_read`	read	`read`	reads key: no; key leaves: no; moves funds: never	ethereum, sepolia, base, base-sepolia, arbitrum, arbitrum-sepolia, optimism, optimism-sepolia, polygon	default, all
`swap.quote`	`swap_quote`	read	`quote`	reads key: no; key leaves: no; moves funds: never	ethereum, base, arbitrum, optimism, polygon	default, all
`swap.prepare`	`swap_prepare`	prepare	`quote`, `sign`, `broadcast`	reads key: no; key leaves: no; moves funds: with_approval	ethereum, base, arbitrum, optimism, polygon	default, all
`x402.prepare`	`x402_prepare`	prepare	`sign`, `pay`	reads key: no; key leaves: no; moves funds: with_approval	base, base-sepolia, ethereum, sepolia, polygon, arbitrum, optimism, solana, solana-devnet	default, all
`erc8004.lookup`	`erc8004_lookup`	read	`read`	reads key: no; key leaves: no; moves funds: never	ethereum, base, arbitrum, optimism, polygon	all
`tx.simulate`	`tx_simulate`	read	`simulate`	reads key: no; key leaves: no; moves funds: never	ethereum, sepolia, base, base-sepolia, arbitrum, arbitrum-sepolia, optimism, optimism-sepolia, polygon	all
`token.approvals.list`	`token_approvals_list`	read	`read`	reads key: no; key leaves: no; moves funds: never	ethereum, sepolia, base, base-sepolia, arbitrum, arbitrum-sepolia, optimism, optimism-sepolia, polygon	all
`token.approvals.revoke`	`token_approvals_revoke`	prepare	`sign`, `broadcast`	reads key: no; key leaves: no; moves funds: with_approval	ethereum, sepolia, base, base-sepolia, arbitrum, arbitrum-sepolia, optimism, optimism-sepolia, polygon	all
`erc8004.register`	`erc8004_register`	prepare	`sign`, `broadcast`	reads key: no; key leaves: no; moves funds: with_approval	ethereum, base, arbitrum, optimism, polygon	all
`bridge.quote`	`bridge_quote`	read	`quote`	reads key: no; key leaves: no; moves funds: never	ethereum, base, arbitrum, optimism, polygon	all
`bridge.prepare`	`bridge_prepare`	prepare	`quote`, `sign`, `broadcast`	reads key: no; key leaves: no; moves funds: with_approval	ethereum, base, arbitrum, optimism, polygon	all
`safe.info`	`safe_info`	read	`read`	reads key: no; key leaves: no; moves funds: never	ethereum, sepolia, base, base-sepolia, arbitrum, optimism, polygon	all
`safe.propose`	`safe_propose`	prepare	`sign`	reads key: no; key leaves: no; moves funds: with_approval	ethereum, sepolia, base, base-sepolia, arbitrum, optimism, polygon	all
`solana.read`	`solana_read`	read	`read`	reads key: no; key leaves: no; moves funds: never	solana, solana-devnet	all
`solana.transfer`	`solana_transfer`	prepare	`sign`, `broadcast`	reads key: no; key leaves: no; moves funds: with_approval	solana, solana-devnet	all
`solana.swap.quote`	`solana_swap_quote`	read	`quote`	reads key: no; key leaves: no; moves funds: never	solana	all
`solana.swap.prepare`	`solana_swap_prepare`	prepare	`quote`, `sign`, `broadcast`	reads key: no; key leaves: no; moves funds: with_approval	solana	all

Meta tools

tool name	kind	effects	toolset
`execute`	execute	`sign`, `broadcast`	default, all
`status`	meta	`read`	default, all
`actions_search`	meta	`read`	default, all
`actions_describe`	meta	`read`	default, all

Default MCP profile, in order: chain_read, swap_quote, swap_prepare, x402_prepare, execute, status, actions_search, actions_describe.

Actions consumed from an AgentKit provider (fromAgentKitProvider) are not in this table: they are built at runtime from the provider you pass, and appear under toolset all.

Entry points

import	what it gives you
`@satohub/kit`	`createKit`, `coreActions`, the tool surface, config loader, everything below re-exported
`@satohub/kit/spec`	the vendored contracts: `sato.action/v1`, `sato.policy/v1`, `sato.receipt/v1`, id rules, descriptor lint
`@satohub/kit/policy`	`evaluatePreflight`; compilers `compileCdpPolicy`, `compilePrivyPolicy`, `compileTurnkeyPolicy`
`@satohub/kit/signers`	`viemLocalSigner`, `owsSigner`, `cdpSigner`, `solanaLocalSigner`, `humanApprove`
`@satohub/kit/intent`	intent store, HMAC intent ids (`loadOrCreateIntentSecret`, `verifyIntentId`)
`@satohub/kit/receipts`	the hash-chained `sato.receipt/v1` log
`@satohub/kit/actions`	every core action, descriptor and builder
`@satohub/kit/ai-sdk`	`satoKitTools(kit, opts)` for the Vercel AI SDK
`@satohub/kit/agentkit`	`satoKitActionProvider(kit, opts)` and `fromAgentKitProvider(provider, { chain })`
`@satohub/kit/claude-agent-sdk`	`createSatoKitSdkServer(kit, opts)` + `requireApprovalHook()`
`@satohub/kit/openai-agents`	`satoKitOpenAITools(kit, opts)`
`@satohub/kit/langchain`	`satoKitLangChainTools(kit, opts)`
`@satohub/kit/eliza`	`satoKitElizaPlugin(kit, opts)` (compatibility adapter, see below)
`@satohub/kit/mcp`	the local MCP server (stdio)
`@satohub/kit/cli`	the `sato-kit` CLI as a function
`@satohub/kit/sato-os`	`attachToSatoOs`, `proposeIntent`
`@satohub/kit/goat`	`fromGoatPlugin(plugin, { chain })` — consume an existing GOAT plugin with the kit's guarantees

Signers

viemLocalSigner — a key in this process. Fork/testnet by default; refuses mainnet chain ids unless allowMainnet: true (not recommended). generate: true makes a throwaway in-memory key.
owsSigner — a structural adapter over an Open Wallet Standard account; OWS's policy engine enforces. See src/signers/OWS.md.
cdpSigner — a structural adapter over a Coinbase CDP server account; CDP enforces its policies. Pass a compiled policy as nativePolicy to carry it with the signer (the adapter does not register it).
solanaLocalSigner — local Solana signing for devnet and tests only; refuses any non-devnet payload and a mainnet-beta RPC, with no mainnet switch.
humanApprove(signer, approve) — wraps any signer so a person approves each summary before it signs.

Policy compilers

compileCdpPolicy, compilePrivyPolicy and compileTurnkeyPolicy turn one sato.policy/v1 into the provider's native policy document. Each result lists what did not compile (not_compiled) with the reason, so a rule the provider cannot express is never silently dropped.

CLI

sato-kit read <action> --input '<json>'      run a read-only action

sato-kit prepare --input ' ' build an intent; nothing is signed sato-kit execute --intent hand one prepared intent to the signer sato-kit mcp [--toolsets default|all] local MCP server over stdio sato-kit doctor check config, Sato Status and template drift

Config comes from the working directory: policy.json (absent means the default policy, network fork), .sato/ (intents, intent secret, receipts), SATO_RPC_URL_ per chain, and SATO_SIGNER=viem-local-fork (fork network only) for a local signer.

MCP server

npx -y @satohub/kit@0.1 mcp runs a stdio MCP server (registry name ai.satohub/kit). The default profile is the eight tools listed above; --toolsets all adds every other registered action. Tools that sign carry anthropic/requiresUserInteraction in _meta.

Sato Status

status and sato-kit doctor read the nightly per-action results (sato.action-status/v1) published by the templates repo. When that file cannot be read, the answer says so; nothing is filled in.

Recommended .gitignore

The file intent store and the intent HMAC secret live under .sato/ by default (intents/, intent.key, mode 0600). Keep them out of version control:

.sato/

`sato-kit doctor`: template drift

In a repo made by create-sato-agent (one with sato.create.json), doctor also sends sato.create.json and sato.lock.json to https://satohub.ai/api/create/drift (3 s timeout) and prints the changes it returns: a newer template version that passed its checks, a custody change in a stored Sato Check profile for a pinned package, or a pinned package version that fails the templat

Only the beginning is shown; read the rest in the repo

Sato Kit

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

Whisper

README from the maker

@satohub/kit

Install

Honest limits

Action reference

Registered actions

Meta tools

Entry points

Signers

Policy compilers

CLI

MCP server

Sato Status

Recommended .gitignore

sato-kit doctor: template drift

`sato-kit doctor`: template drift