About HiveBank
HiveBank is an MCP server for autonomous agents managing USDC treasuries, yield-bearing vaults, and scheduled payment streams. It supports settlement in USDC on Base and USDCx on Aleo.
Key features
- 01Create yield-bearing USDC vaults
- 02Deposit USDC into vaults
- 03Create programmable payment streams
- 04View vault balance and yield
- 05Retrieve treasury-wide statistics
Use cases
- 01Set up an agent's USDC vault
- 02Deposit funds into a treasury vault
- 03Schedule payments between DIDs
- 04Review vault yield or treasury statistics
MCP support
Exposes vault creation, deposits, payment stream creation, balance queries, and treasury statistics as MCP tools. The server accepts JSON-RPC 2.0 over HTTP.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://hivebank.onrender.com/mcpclaude mcp add --transport http srotzin-hivebank https://hivebank.onrender.com/mcp{"mcpServers":{"srotzin-hivebank":{"type":"http","url":"https://hivebank.onrender.com/mcp"}}}Open in Cursor{"servers":{"srotzin-hivebank":{"type":"http","url":"https://hivebank.onrender.com/mcp"}}}Open in VS Code{"mcpServers":{"srotzin-hivebank":{"type":"http","url":"https://hivebank.onrender.com/mcp"}}}{"mcpServers":{"srotzin-hivebank":{"serverUrl":"https://hivebank.onrender.com/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
5| Parameter | Type | Required | Description |
|---|---|---|---|
| owner_did | string | Yes | Decentralized identifier (DID) of the vault owner |
| vault_name | string | Yes | Human-readable name for the vault |
| vault_type | string | No | Vault type (e.g. standard, high-yield) |
Details
From the project READMEHiveBank — Agent Treasury Protocol — MCP Server
HiveBank is an MCP server that provides yield-bearing vaults, payment streaming, and treasury management for autonomous AI agents.
Dual settlement rails: USDC on Base L2 (fast, public) + USDCx on Aleo mainnet (ZK-private, Circle-backed). Bridge via Circle xReserve CCTP — no third-party bridge, 1:1 guaranteed.
MCP Endpoint
POST /mcp
JSON-RPC 2.0 over HTTP. Supports initialize, tools/list, and tools/call.
MCP Tools
| Tool | Description | Required Parameters |
|---|---|---|
hivebank_create_vault | Create a yield-bearing USDC vault for an agent | owner_did, vault_name |
hivebank_deposit | Deposit USDC into a vault | vault_id, amount_usdc, depositor_did |
hivebank_create_stream | Create a programmable payment stream | from_did, to_did, total_usdc, duration_seconds |
hivebank_get_balance | Get vault balance and yield info | vault_id |
hivebank_get_stats | Get treasury-wide stats | (none) |
Usage
# Initialize
curl -X POST https://hivebank.onrender.com/mcp \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize"}'
# List tools
curl -X POST https://hivebank.onrender.com/mcp \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":2,"method":"tools/list"}'
# Call a tool
curl -X POST https://hivebank.onrender.com/mcp \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":3,"method":"tools/call","params":{"name":"hivebank_get_stats","arguments":{}}}'
Running Locally
npm install
npm start
Server starts on port 3001 (or PORT env var). Health check at GET /health.
Architecture
Node.js + Express + SQLite. Yield accrual, stream processing, and credit monitoring run as background tasks.
License
Proprietary — Hive Civilization
Hive Civilization
Hive Civilization is the cryptographic backbone of autonomous agent commerce — the layer that makes every agent transaction provable, every payment settable, and every decision defensible.
This repository is part of the PROVABLE · SETTABLE · DEFENSIBLE pillar.
- thehiveryiq.com
- hiveagentiq.com
- agent-card: https://hivetrust.onrender.com/.well-known/agent-card.json
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.