MCP.Market

Sovereign Identity Wallet MCP server

by TamTunnel·io.github.TamTunnel/si-wallet-mcp·v0.1.3
No reviews yet

Self-hosted signing wallet: DIDs, agency grants, and task mandates for AI agents.

A88/100grade A
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
A88/100

full report

Adoption
Growing

0 stars105 downloads/wk

Reviews

Write one

Nobody has reviewed Sovereign Identity Wallet yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Sovereign Identity Wallet tools (7, 1 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • issue_grant

    Owner issues an agency grant delegating authority to an agent DID (scopes + USD amount limit + TTL).

  • mint_mandate

    Agent mints a task mandate for a website audience, bound to an agency grant. Returns the mandate JWS and the Authorization header value. Amounts over $100 need confirmOverLimit=true (only after the owner explicitly approved). Pass subjectDid to delegate to a downstream agent (e.g. Muse delegating to Hermes) with narrowed scope/amount.

  • pairwise_did

    Generate a fresh pairwise DID for one audience (prevents cross-site correlation).

  • verify_chain

    Website-side verification of a multi-hop delegation chain (Owner → … → leaf agent): walks every link, enforcing parent signatures, parent-issued-to-signer binding, scope subset and amount confinement at each hop, expiry, leaf audience, and replay protection. Returns the full attenuated chain.

  • verify_mandate

    Website-side verification of a task mandate chain: signatures, expiry, audience, replay, grant binding, scope/amount confinement. Records the JTI in the local replay ledger on success.

  • wallet_did

    Get the DID for the owner or agent identity in this wallet.

  • wallet_onboardwrite action

    Create the owner or agent identity (returns the existing one if present). Requires SI_WALLET_PASSPHRASE.

Public scan report

scanner v0.1.10 · 2026-11-03 · same rubric, same numbers if you re-run it

no findings
  • Code scan3 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 41 days ago12/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 88/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Sovereign Identity Wallet compares

Against every graded Productivity MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
88/100
higher than 75% of 1,299 Productivity servers
Tools
7
the typical Productivity server has 7
Tools that change things
14%
typical: 0%. Fewer write tools means less an agent can break
Downloads a week
105
more than 57% of 427 Productivity servers with a package

What its tools let an agent do: 6 read · 1 change

Install Sovereign Identity Wallet in Claude Code, Cursor or VS Code

Runs npx -y @tamtunnel/si-wallet-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add si-wallet-mcp -- npx -y @tamtunnel/si-wallet-mcp
Add to Cursor

What the publisher says

From the Sovereign Identity Wallet repository's README, as published. We do not edit it. Read it on GitHub

si-wallet-mcp

Sovereign-identity wallet as an MCP server. Gives any MCP-capable agent a DID, owner→agent grants, and task mandates — the identity layer underneath AWAS website authentication.

Protocol: TamTunnel/sovereign-identity — DIDs, agency grants, task mandates, and the AWAS website binding this wallet implements.

Version: 0.1.0 · License: Apache-2.0

Tools

Guardrails are enforced server-side: mandates over $100 need confirmOverLimit=true (only after the owner explicitly approved), and the verifier rejects non-canonical base64url outright.

Quick start

npm install -g @tamtunnel/si-wallet-mcp   # after publish; or clone and npm install
export SI_WALLET_PASSPHRASE="your passphrase"   # required for signing
si-wallet-mcp                                # stdio mode (default)

State lives in ~/.sov-id (override with SIWALLETDIR). Keys are scrypt + AES-256-GCM encrypted at rest, files mode 600.

Local MCP clients (Claude Code, Hermes, OpenClaw, …)

Add to the client's MCP config:

{
  "mcpServers": {
    "si-wallet": {
      "command": "node",
      "args": ["/path/to/si-wallet-mcp/server.mjs"],
      "env": { "SI_WALLET_PASSPHRASE": "your passphrase" }
    }
  }
}

Muse (custom connector)

Muse custom connectors reach remote MCP servers over streamable HTTP — a server on your laptop is not reachable from Meta's cloud. Run:

export SI_WALLET_PASSPHRASE="your passphrase"
export SI_MCP_TOKEN="$(openssl rand -hex 32)"   # required in HTTP mode
si-wallet-mcp --http --port 8787

Expose it on a public HTTPS URL (your VPS, fly.io, Tailscale, …), then add that URL as a custom connector in Muse with Authorization: Bearer . The server binds 127.0.0.1 by default; only set SIMCPHOST=0.0.0.0 behind TLS. Full walkthrough: DEPLOY.md.

Docker

docker build -t si-wallet-mcp .
docker run -d --name si-wallet \
  -e SI_MCP_TOKEN="$(openssl rand -hex 32)" \
  -e SI_WALLET_PASSPHRASE="your passphrase" \
  -v si-wallet-data:/data \
  -p 127.0.0.1:8787:8787 \
  si-wallet-mcp

See DEPLOY.md for fly.io, Tailscale, TLS, onboarding, backups, and connecting Meta Muse.

Delegation demo: Owner → Muse → Hermes

examples/delegation-chain/ is a runnable proof that mandates compose across agents and frameworks with no pair-specific connectors: the owner grants Muse broad authority, Muse delegates a narrowed envelope to Hermes, Hermes presents the leaf mandate to a website, and the website verifies the whole attenuated chain. Four attacks (scope escalation, amount escalation, tampering, replay) are attempted and refused.

node examples/delegation-chain/run.mjs

Who hosts this?

Each user hosts their own. That is the point. A wallet holds private keys, so there is no shared hosted instance — that would be custodial and would contradict the "sovereign" in sovereign identity.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Sovereign Identity Wallet: common questions

Is Sovereign Identity Wallet MCP server safe?
Yes, by our scan: it is graded A (88/100). Read the Sovereign Identity Wallet safety report
How do I install Sovereign Identity Wallet?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Sovereign Identity Wallet need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Sovereign Identity Wallet maintained?
The last commit was 42 days ago (2026-09-22). The latest release is v0.1.3.
What can I use instead of Sovereign Identity Wallet?
Servers from other publishers that do the same job: RevoGrid DataGrid MCP Pro MCP server and FlutterSDK Docs MCP server.
How does Sovereign Identity Wallet compare with other Productivity MCP servers?
safety score 88/100 (higher than 75% of 1,299 Productivity servers); tools 7 (the typical Productivity server has 7); tools that change things 14% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Sovereign Identity Wallet

Same job from other publishers: the closest match first, then the best rated.

  • RevoGrid DataGrid MCP Pro
    Hosted Pro MCP server for RevoGrid DataGrid docs, examples, feature checks, and migration guidance.
    A
  • FlutterSDK Docs
    Search Wind UI, Magic, Dusk, Telescope and Artisan documentation. Hosted, public, no auth.
    A