
Hive Secrets
io.github.srotzinPublished by GitHub account srotzinv1.0.0Updated Oct 24, 2026
Encrypted secret store and rotation for autonomous agent credentials
The publisher's own server: Secrets.RealEstate
Overview
A remote MCP server that stores and retrieves encrypted agent credentials in per-agent namespaces, with paid reads and writes settled in USDC on Base.
- What you can do
- Store, read and delete secrets keyed by namespace and key, encrypted at rest with AES-256-GCM and scoped to the caller's agent DID namespace. List the keys held in a namespace. Read the per-namespace audit log of actions, including payment and error events. Check today's revenue snapshot and service health. Paid operations require a Base USDC transaction hash that the service verifies on-chain before serving the call.
- When to use it
- Useful when an autonomous agent needs a hosted place to keep API keys or other credentials between runs, isolated per agent identity, and you accept paying small per-call USDC fees for reads and writes.
- Requirements
- Remote streamable-HTTP endpoint; no local install or declared authentication. Paid calls need a Base USDC transfer to the operator's wallet and a transaction hash supplied in the request body or the x402-tx-hash header. Self-hosting needs Node.js, npm and a SECRETS_MASTER_KEY environment variable; without it, writes return 503.
Installation
In SourceWeft
- Open Hive Secrets 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-secrets/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-secrets": {
"type": "http",
"url": "https://hive-mcp-secrets.onrender.com/mcp"
}
}
}README
hive-mcp-secrets
[srotzin/hive-mcp-secrets MCP server]
Encrypted secret store for the A2A network — Hive Civilization. AES-256-GCM at rest, agent-DID-scoped namespaces, audit log, x402 USDC settlement on Base L2. MCP 2024-11-05. Inbound only.
Agents put encrypted secrets keyed by (namespace, key) and retrieve them later. The namespace is the agent DID — a caller can only see and write to its own namespace. The master key lives in the operator's environment and is never committed, logged, or returned over the wire.
Quick start
Hosted endpoint: https://hive-mcp-secrets.onrender.com/mcp
Tools and pricing
All payments are inbound. Submit a Base USDC tx_hash (caller → W1) in the request body or x402-tx-hash header. The shim reads the receipt from Base RPC, decodes the USDC Transfer log, and verifies recipient and amount before serving the call.
Operator note — master key required for writes
hive-mcp-secrets reads SECRETS_MASTER_KEY from the process environment at startup.
- If set, it is parsed as 64-char hex → 32 raw bytes; or as base64 → 32 raw bytes; or otherwise SHA-256 hashed to 32 bytes.
- If not set, writes return
503 service_unavailablewithreason: "SECRETS_MASTER_KEY not set". Reads of records that do not exist return404as usual; reads of stored records require the same key that wrote them, since AES-256-GCM rejects decryption with any other key.
The key is never committed to the repository, never logged, and never returned over the wire. Operators are expected to set it in the deployment environment (Render env var, Kubernetes secret, etc.) before enabling production traffic. Rotating the key invalidates all previously stored ciphertexts.
Namespace model
The namespace parameter on every endpoint is the agent DID that owns the data. Every endpoint enforces caller_did === namespace and returns forbidden_namespace_mismatch otherwise. There is no superuser, no cross-namespace read, and no multi-DID sharing in v1.
The audit log is per-namespace and records every action — get, put, delete, list, audit, plus the negative paths payment_required, error:not_found, error:integrity_check_failed, etc. Entries store caller_did, action, ts_ms, and (for paid ops) tx_hash, payer, and amount_usd.
REST endpoints
PUT /v1/secrets/{namespace}/{key} body
Without tx_hash, the response is a 402 envelope:
Encryption details
- Algorithm:
aes-256-gcm(FIPS-recognized AEAD) - Key length: 32 bytes
- IV length: 12 bytes, fresh
crypto.randomBytes(12)per record - Auth tag length: 16 bytes
- Storage: SQLite
secretstable —(namespace, key, ciphertext, iv, auth_tag, created_ms, updated_ms, version)with PRIMARY KEY(namespace, key) - Write path:
node:crypto.createCipheriv → update → final, thengetAuthTag(). All three values stored as base64 TEXT. - Read path:
createDecipheriv → setAuthTag → update → final. Any single bit flipped inciphertext,iv, orauth_tagcausesfinal()to throw, which surfaces asintegrity_check_failed.
The smoke test below verifies tampered ciphertext fails to decrypt — this is real AES-GCM, not an integrity check tacked on after the fact.
MCP usage
Local smoke test
Hosting
Deployed to Render: srv hive-mcp-secrets, oregon, starter, autoDeploy=true. The Render env var SECRETS_MASTER_KEY is the operator's responsibility to set. Without it, the deployed service still runs, /health reports master_key_loaded: false, and writes return 503.
License
MIT — see LICENSE.
Hive Civilization Directory
Part of the Hive Civilization — agent-native financial infrastructure.
- Endpoint Directory: https://thehiveryiq.com
- Live Leaderboard: https://hive-a2amev.onrender.com/leaderboard
- Revenue Dashboard: https://hivemine-dashboard.onrender.com
- Other MCP Servers: https://github.com/srotzin?tab=repositories&q=hive-mcp
Brand: #C08D23
Source: README.md at commit d7d19b7
Tools
0Version history
1- v1.0.0LatestSep 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
Other Secrets integrations
Secrets.RealEstate
realestate.secretsOfficial publisher
A remote MCP endpoint giving assistants sourced French property intelligence: sold prices, energy ratings, risk, crime and school data for addresses.

Bitwarden Public API and Secrets Manager (unofficial)
Published by GitHub account mguttmann
Unofficial local MCP server that lets an assistant manage Bitwarden organization members, groups, collections, policies and Secrets Manager projects and…

LLM Data Guard: PII & Secrets Redaction
Published by GitHub account fairquery
Detect and redact PII and secrets (API keys, tokens) in text, HTML or PDF before it reaches an LLM.

Keeper Secrets Manager
Published by GitHub account WYRE-AI
Read-only multitenant Streamable HTTP bridge over Keeper Secrets Manager's MCP server.

Keeper Secrets Manager
Published by GitHub account wyre-technology
Read-only, multitenant HTTP bridge that re-serves Keeper Secrets Manager's MCP server so an assistant can list, search and read vault secrets per tenant.