mcpField
H
Hive Vault

Hive Vault

Remote
hiveagentiq.comFinance0Updated 10w ago

About Hive Vault

Hive Vault is an MCP service connected to HiveVault, offering read-only balance, statistics, identity, and quantum public-key queries, plus AES-256-GCM encrypted item storage.

Key features

  1. 01Read balance, statistics, and identity
  2. 02Retrieve the quantum public key
  3. 03Store items with AES-256-GCM encryption
  4. 04Verify stored items without returning plaintext

Use cases

  1. 01Inspect read-only HiveVault data
  2. 02Retrieve the vault quantum public key
  3. 03Store encrypted items and confirm their presence

MCP support

The MCP service provides four read-only HiveVault query tools. Encrypted item storage is available through HTTP endpoints and gated by x402.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://hive-mcp-vault.onrender.com/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

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

4

This tool takes no parameters.

Details

From the project README

hive-mcp-vault

srotzin/hive-mcp-vault MCP server

MCP access to confirmed HiveVault FENR reads and an AES-256-GCM encrypted item store.

Live contract

The server exposes four read-only MCP tools backed by the live HiveVault service:

ToolLive backend route
vault.balanceGET /vault/balance
vault.statsGET /vault/stats
vault.identityGET /vault/identity
vault.quantum_pubkeyGET /vault/quantum/pubkey

vault.balance returns the backend response exactly as received. An unauthenticated response can be marked obfuscated: true; clients must not treat that value as a confirmed treasury balance.

The server also exposes an encrypted item store:

MethodPathDescription
POST/v1/vault/storeStore an AES-256-GCM encrypted item after the x402 gate
GET/v1/vault/store/:item_refConfirm a stored item exists without returning plaintext

Unknown paths return HTTP 404. Upstream failures return explicit MCP errors. The service does not return fabricated success payloads.

Discovery and health

MethodPathDescription
GET/healthReadiness. This process plus current upstream reachability. Returns 503 and degraded when the upstream is unreachable
GET/livezLiveness only. This process, no upstream claim. This is the path platform health checks should use
POST/mcpMCP JSON-RPC 2.0, protocol 2024-11-05
GET/.well-known/mcp.jsonMCP discovery manifest
GET/.well-known/agent-card.jsonA2A agent card
GET/.well-known/agent.jsonAgent card
GET/.well-known/oac.jsonOpen Agent Card JSON-LD
GET/llms.txtPlain-text integration guide

Persistence

Set BOGO_DB_PATH to a path on durable storage in production. The default path, /tmp/bogo_vault.db, is suitable only for local development and tests. The server refuses to start in production unless an explicit database path is configured.

Environment variables

VariableRequiredPurpose
PORTNo, default 3000HTTP port
VAULT_BACKEND_URLNo, default https://hive-vault.onrender.comLive HiveVault backend
INTERNAL_KEYYes in productionDerives the local encryption key and is sent to the backend as x-vault-key
BOGO_DB_PATHYes in productionSQLite database path on durable storage. Local development defaults to /tmp/bogo_vault.db
BASE_RPC_URLNo, default https://mainnet.base.orgBase RPC endpoint used for x402 payment verification

The server refuses to start with NODE_ENV=production if INTERNAL_KEY or BOGO_DB_PATH is missing.

Testing

npm install
npm test

Tests cover health reporting, unknown-route handling, MCP tool discovery, upstream failure behavior, encrypted storage, and plaintext absence from the SQLite file.

Brand

Hive Civilization. Brand gold #C08D23. Steve Rotzin.

Directory

Comments

Markdown supported

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.