Hive Mcp Flag
by srotzincommunityv1.0.0
An MCP server that provides feature-flag management for the A2A network, including evaluating, listing, creating, updating, deleting, and describing flags targeted by DID, DID prefix, or percentage rollout rules. Paid calls are verified through Base USDC transaction receipts before execution.
From the registry: Feature flag service for safe rollouts across the Hive agent fleet
Install & configure
Prerequisites
- requiredNode.js and npmInstall Node.js and npm to run the server locally from the cloned repository.https://nodejs.org/
Install in your client
Paste into the AI you're chatting with — it will figure out the rest
Please install the `hive-mcp-flag` MCP server into my current AI client (that's you).
Required prerequisites (do these first if not already done):
- **Node.js and npm** — Install Node.js and npm to run the server locally from the cloned repository. (https://nodejs.org/)
Canonical MCP server config (HTTP transport):
- url: `https://hive-mcp-flag.onrender.com/mcp`
- headers:
- `x402-tx-hash`: `<your-base-usdc-payment-tx-hash>`
Note: README provides a hosted Streamable-HTTP MCP endpoint at /mcp. Paid tool calls require submitting a Base USDC transaction hash either in the request body or via the x402-tx-hash header. Local run instructions are provided (git clone, npm install, npm start), but no separate MCP client config URL for local use is explicitly documented; if self-hosting locally, the service listens on the configured PORT (default 3000) and exposes POST /mcp. Relevant server environment variables for self-hosting are: PORT (optional, HTTP port), ENABLE (optional, master switch), WALLET_ADDRESS (optional, payment receiver address), BASE_RPC_URL (optional, but practically required when VERIFY_ONCHAIN=true, which is the default), VERIFY_ONCHAIN (optional, defaults true), MAX_FLAGS_PER_DID (optional), and DB_PATH (optional).
Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.Note: README provides a hosted Streamable-HTTP MCP endpoint at /mcp. Paid tool calls require submitting a Base USDC transaction hash either in the request body or via the x402-tx-hash header. Local run instructions are provided (git clone, npm install, npm start), but no separate MCP client config URL for local use is explicitly documented; if self-hosting locally, the service listens on the configured PORT (default 3000) and exposes POST /mcp. Relevant server environment variables for self-hosting are: PORT (optional, HTTP port), ENABLE (optional, master switch), WALLET_ADDRESS (optional, payment receiver address), BASE_RPC_URL (optional, but practically required when VERIFY_ONCHAIN=true, which is the default), VERIFY_ONCHAIN (optional, defaults true), MAX_FLAGS_PER_DID (optional), and DB_PATH (optional).
Tools (6)
flag_eval
Evaluate a flag for a DID and return the resolved value and matched rule.
flag_list
List flags owned by a DID.
flag_describe
Return the full flag definition and recent evaluations.
flag_create
Create a flag with a default value and targeting rules.
flag_update
Update a flag's default value or targeting rules; owner-only.
flag_delete
Tombstone a flag; owner-only.
Environment variables
WALLET_ADDRESSrequiredBase L2 receiver wallet address used to verify and receive inbound USDC payments.BASE_RPC_URLrequiredBase RPC endpoint used to read transaction receipts for payment verification.Remote Endpoints
https://hive-mcp-flag.onrender.com/mcp
type: streamable-http
Details
- Language
- JavaScript
- License
- MIT
- Released
- Apr 29, 2026
- Last commit
- Jun 22, 2026
- Registry name
- io.github.srotzin/hive-mcp-flag