brainchain-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BRAINCHAIN_PAY_ON | No | base pays in USDC on Base (Base Sepolia on testnet) instead of USDG on Robinhood Chain. | robinhood |
| BRAINCHAIN_PAY_TO | No | Override the network preset payment recipient address. Required when using a custom desk. | |
| BRAINCHAIN_NETWORK | No | testnet switches every setting to BrainChain testnet. | mainnet |
| BRAINCHAIN_DESK_URL | No | Override the network preset desk URL. A custom desk needs its own BRAINCHAIN_PAY_TO. | |
| BRAINCHAIN_PAYER_KEY | Yes | Private key of the paying wallet, 0x followed by 64 hex characters. | |
| BRAINCHAIN_PAYMENT_RPC | No | Override the network preset payment RPC setting. | |
| BRAINCHAIN_BUDGET_UNITS | No | The most paid in total while the server runs, in the token's base units. | 10000000 |
| BRAINCHAIN_PAYMENT_ASSET | No | Override the network preset payment asset setting. | |
| BRAINCHAIN_MAX_PRICE_UNITS | No | The most paid per task, in the token's base units (6 decimals). | 1000000 |
| BRAINCHAIN_PAYMENT_NETWORK | No | Override the network preset payment network setting. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| brainchain_post_taskA | Pay for a task on BrainChain. Jev, BrainChain's decision model, hires the frontier model best suited to the brief, grades the result against your quality levels and pays the model only if the work reaches the second level or better. Each task costs 1 USDG, paid from this server's wallet on Robinhood Chain. The result is delivered only if Jev accepts the work. If Jev rejects the work, the full amount is refunded to the same wallet on Robinhood Chain, about six hours after grading. If no model delivers within 24 hours, it is refunded after the deadline. Returns an order id for brainchain_get_task; results usually arrive within minutes. If the reply says possiblyCharged, do not post the task again: read the order with brainchain_get_task. |
| brainchain_get_taskA | Read an order from brainchain_post_task: the payment, the task's status on BrainChain, Jev's grade, the result text once the work is accepted, and the refund transaction if it is not. Stop calling when |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools form a clean write/read pair: brainchain_post_task creates an order and brainchain_get_task reads it. Descriptions explicitly cross-reference each other and even tell the agent not to re-post when a reply says possiblyCharged, eliminating the main confusion risk.
Both names follow the same brainchain_<verb>_<noun> pattern with a shared server prefix and snake_case throughout. No deviation or ambiguity in the convention.
Two tools is thin, but here they are a minimal viable pairing for an asynchronous paid-task service (submit then poll), so it is defensible rather than arbitrary. Still, the surface feels sparse for a service that involves payments, refunds, and grading.
The core submit-and-retrieve lifecycle is covered, including refund and failure states in the status semantics. However, there is no way to list orders, cancel a task, check wallet balance or refund status independently, which leaves agents without recovery paths if an order id is lost.