
Hive Wallet
io.github.srotzinPublished by GitHub account srotzinv1.1.1Updated Oct 24, 2026
HiveWallet MCP Server
Overview
Remote MCP server for HiveWallet that lets an assistant provision agent-DID wallets, move USDC on Base, and mint or verify signed receipts.
- What you can do
- Inspect wallet service info: verifier public key, supported proofs and backend versions
- Create a new agent-DID wallet where the DID is the account holder
- Transfer USDC between DIDs and mint a signed HiveDNA receipt for the transfer
- Verify a single receipt publicly, including signature, body hash and chain recomputation
- Walk a DID's full receipt chain and return a signed integrity statement
- When to use it
- Use it when an assistant needs to hold and move USDC on Base on its own behalf and produce verifiable, signed receipts for those transfers, or when someone needs to check the integrity of an existing receipt or receipt chain.
- Requirements
- A remote streamable-HTTP endpoint; no accounts or API keys are declared for the MCP server itself. The README describes USDC on Base as the payment rail and an x402 quote/settle flow with an access token header for the gateway endpoint. Running the server locally would need Node.js and the PORT, HIVE_WALLET_URL and HIVEBANK_URL settings.
Installation
In SourceWeft
- Open Hive Wallet in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.srotzin%2Fhive-mcp-wallet/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"hive-wallet": {
"type": "http",
"url": "https://hive-mcp-gateway.onrender.com/wallet/mcp"
}
}
}README
hive-mcp-wallet
The first wallet where the agent IS the account holder.
Public MCP server for HiveWallet — the agent-native wallet primitive in the Hive Civilization stack. Tools provision DID-as-holder wallets, transfer USDC, mint HiveDNA 3-proof receipts (SHOD + spectral-ZK + CTEF, Ed25519-signed), and verify receipts or whole chains offline. Real rails — USDC on Base — no mocks.
- Endpoint:
https://hive-mcp-wallet.onrender.com/mcp - Transport: Streamable-HTTP (MCP 2024-11-05)
- Backend:
hive-wallet.onrender.com→hivebank.onrender.com - Treasury:
0x15184Bf50B3d3F52b60434f8942b7D52F2eB436E
Tools
Why HiveDNA receipts
The receipt is a separate, signed artifact (not just a transaction log entry):
- SHOD — Sovereign Holographic Object Descriptor layers; rejection layers cannot mint receipts
- Spectral-ZK — verified zero-knowledge ticket scoped to the epoch
- CTEF chain — content-addressed, race-safe append; chain root walks deterministically
- Ed25519 signed canonical body with
verify_urlpublished in the response - Score 0-1000 — deterministic from proofs, regime, chain depth
Public key travels with the receipt. A regulator with the receipt and the published key can verify offline without trusting the operator.
Endpoints behind the tools
Connect
Claude Desktop
Inspector / curl
Run locally
Configuration
License
MIT
Agent-Callable
This MCP server is fully agent-callable — no accounts, no API keys, no human approval required.
Sample request
Source: README.md at commit 96e85aa
Tools
0Version history
1- v1.1.1LatestSep 16, 2026
Score
85% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listedRequired15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts