Sato Hub
MCP

Privy MCP Server

Official Privy MCP server: create wallets, sign transactions, and manage policies across 11 chains.

  • Sato Score58
  • ChainsMultichain
UnknownSelf-ReportedQuiet · 8mo ago

Privy MCP Server is an open-source MCP server by Privy, with last code activity on 2026-02-09 (Quiet). Sato Score 58/100 (how open, active and verifiable it is, not a safety grade), as of 2026-10-15. How the score works →

See how to install Privy MCP Server →

Last commit Feb 9, 2026 · ★ 2

Listed from privy.io on 2026-07-13. Install: not attempted. Evidence →

Next step

Watch Privy MCP Server

One email if what we observe changes — its repo goes quiet or disappears, or the listing is retired. Nothing else.

Check it from your agent

Add Sato Hub’s MCP server (no key), then ask:

https://satohub.ai/api/mcp
Run Sato Hub Preflight on privy-io/privy-mcp-server before I use it.
Full setup: Claude Code, Cursor, others →

Your project?

Prove you control the domain and correct this page — description, links, tags, chains. A claim proves control, not verification: it never changes the Sato Score.

Claim this listing →

Overview

Privy's official MCP server gives agents 30+ tools for wallet creation, balance/history checks, Ethereum and Solana signing and broadcasting, EIP-712 messages, transaction policies, and multisig key quorums, spanning EVM, Solana, Bitcoin, Cosmos, Stellar, Sui, Aptos, Tron, Near, TON, and Starknet. Runs via npx or a global install, configured with a Privy App ID and secret. Plugs into an agent that needs Privy-managed embedded wallets as its execution layer.

Sato Score

58/100· Medium

How open, active & verifiable — not a safety or returns grade.

Maintenance & liveness
20/35
Code transparency
17/20
Interface verifiability
0/10
Docs & demo
6/10
Listing transparency & provenance
12/15
Independent verification
3/10

Sato Check

as of 2026-09-28
Does it take your key?
Unknown
Does your key leave?
Not yet run
Can it move funds on its own?
Unknown
Full profile, evidence and limits →

A profile describes what we read and ran, with dates. It is not a safety rating, an audit or an endorsement, and "not found" is not "not there".

Evidence — listed vs checked · what the words mean

Listed from privy.io on 2026-07-13. Install: not attempted.

ClaimValueEvidenceSourceChecked
Chains supportedMultichainself-reporteddocs.privy.ioas of 2026-10-15
Verification statusSelf-Reported — not independently reviewedself-reportedprivy.ioas of 2026-10-15
Recent activitylast commit 2026-02-09observedgithub.com/privy-io/privy-mcp-server2026-10-15
Install worksdocumented by the project, not run by Sato Hubnot attempted by Sato Hubself-reportedgithub.com/privy-io/privy-mcp-serveras of 2026-07-14
Website answersanswered (HTTP 200)observedprivy.io2026-10-15
Daily check record90 of 90 daily checks since 2026-07-17 succeededa success rate of our checks, not uptime; the source is this listing's own historyobserved—2026-10-14
Takes your keyunknown — this version could not be readtracedsatohub.ai2026-09-28
Key leaves the machinenot yet run with planted test keysthe sandbox lane has not run on this versionobservedsatohub.ainot dated
Moves funds on its ownunknown — could not read what it exposestracedsatohub.ai2026-09-28
Deploys asnpx (stdio, local)confidence 0.85self-reportedgithub.com/privy-io/privy-mcp-serveras of 2026-07-14
Works withClaude Desktop, Cursor, Claude Codeconfidence 0.85self-reportedgithub.com/privy-io/privy-mcp-serveras of 2026-07-14
Sato Score58/100 (Medium)how open, active and verifiable — not a safety or quality gradecomputedsatohub.ai2026-10-15

Self-reported rows are the project’s own words, dated when we recorded them — not a check. Only reproduced and reviewed rows carry a mark. None of these rows is a safety or quality rating.

Install — as documented by the project, not run by us

Runtime: node

npx @privy-io/mcp-server
MCP client config: { "command": "npx", "args": ["@privy-io/mcp-server"], "env": { "PRIVY_APP_ID": "<your-app-id>", "PRIVY_APP_SECRET": "<your-app-secret>" } }

You supply: PRIVY_APP_ID and PRIVY_APP_SECRET (from the Privy Dashboard) — this server creates/signs wallets on your behalf

Add to CursorAdd to VS Code
claude mcp add satohub-privy-mcp -- npx @privy-io/mcp-server

A local server: your client runs this command on your machine. Installing runs third-party software under your own credentials. Sato Hub publishes the documented invocation and, where the harness reproduced it, the date it did — neither is a safety review.

Read from the project’s own docs as of 2026-07-14. What a deploy spec is →

Observed record — 91 daily checks since 2026-07-17

100%of 91 checks since 2026-07-17 succeeded
Currently responding for 91 days
Succeeded
91
Failed
0
Their error
0
Unattributed
0

This is the share of our daily checks that succeeded — not an availability guarantee. A check can fail because the host was down, because our runner timed out, or because the network in between dropped it, and only the first of those is a fact about this project. Failures are split by what we can attribute; anything we cannot attribute is counted, not hidden. 46 of these checks predate 2026-09-01, when the probe counted a bot-block (HTTP 403) as a failure and recorded no reason for any failure. Every one of them passed, so the rate covers them too.

Last 30 days — to 2026-10-15, one point per UTC day

Share of OUR checks that succeeded
100%
7-day rolling; unattributable days are gaps · 30/30 days
Tools listed
fewer than 2 points—
from the server's own tools/list · 0/30 days
Sato Score
58
as snapshotted that day · 29/30 days

A gap is a day we have no attributable observation — never a zero. Thirty points is the whole shape the free layer carries; the daily rows behind it stay in the snapshot series.

Details

Chains
Multichain
Agent types
Wallet, MCP Server
Open source
Yes
Deploys as
npx (stdio, local)
Works with
Claude Desktop, Cursor, Claude Code
Last checked
2026-10-15

Marketplace Signals

No marketplace signals recorded for this resource yet.

Verification status reflects evidence reviewed by Sato Hub. Self-reported claims are never presented as verified.

#mcp#wallet#multichain#policies#multisig

Where Privy MCP Server fits

Related concepts: How Agents Use Wallets, What Are Onchain Agents?

See something inaccurate or outdated?Submit a correction →

Listing History

Recorded changes to Privy MCP Server's listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.

  1. Jul 18, 2026
    Sato Hub began tracking this listing
  2. Jul 14, 2026
    Auto-enriched: deployment options, supported integrations
  3. Jul 13, 2026
    Listed on Sato Hub

Compared with

Appears in

Related Resources

Reference

QuestionsShowHide

Questions people ask about Privy MCP Server

Is Privy MCP Server open source?
Yes. Privy MCP Server is open source under the MIT license; the repository is https://github.com/privy-io/privy-mcp-server. Checked as of 2026-10-15.
Which chains does Privy MCP Server support?
Privy MCP Server lists support for Multichain as of 2026-10-15.
Is Privy MCP Server still maintained?
The most recent code activity Sato Hub observed was on 2026-02-09 (last commit 2026-02-09), which Sato Hub labels "Quiet". Posts on X are not counted as maintenance. Activity is a recency signal, not a quality judgment.
How do I install or run Privy MCP Server?
node. Install: npx @privy-io/mcp-server. Entry: MCP client config: { "command": "npx", "args": ["@privy-io/mcp-server"], "env": { "PRIVY_APP_ID": "<your-app-id>", "PRIVY_APP_SECRET": "<your-app-secret>" } }. This is taken from the project's own documentation and has not been reproduced by Sato Hub. It runs as an MCP server (npx @privy-io/mcp-server).
Is Privy MCP Server verified on Sato Hub?
No independent verification is on record for Privy MCP Server; its verification status is "Self-Reported" and its Sato Score is 58 of 100. Self-reported is not verified, and the score is not a safety, quality or returns grade.
Cite this pageShowHide

Cite this page

Sato Hub. "Privy MCP Server — Sato Hub." Sato Hub, updated 2026-10-15, accessed 2026-10-15. https://satohub.ai/resources/privy-mcp

Data last refreshed 2026-10-15; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0.

Join the Sato Hub Briefing

Sign up for the Briefing: the agents, tools, and infrastructure that actually shipped, and why they matter.