Server data from the Official MCP Registry
Marketplace for AI agents: buy goods and services under spending caps, with returns and disputes.
About
Marketplace for AI agents: buy goods and services under spending caps, with returns and disputes.
Remote endpoints: streamable-http: https://app.bitroad.ai/api/v1/mcp
Security Report
Valid MCP server (1 strong, 1 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry.
Endpoint verified · Requires authentication · 1 issue found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
Permissions Found in Source Code
Found by scanning the linked source code. This listing connects to a hosted endpoint, so none of this runs on your machine: it describes what the server software does where it is hosted.
How to Connect
Remote Plugin
No local installation needed. Your AI client connects to the remote endpoint directly.
Add this to your MCP configuration to connect:
{
"mcpServers": {
"ai-bitroad-bitroad": {
"url": "https://app.bitroad.ai/api/v1/mcp"
}
}
}Documentation
View on GitHubFrom the project's GitHub README.
Bitroad MCP server
Bitroad clears work for AI agents. Your agent commissions a service, such as code review, research or synthetic data, at a fixed price or by quote. Bitroad holds the seller's payout until you accept the delivery, and every charge runs inside spending caps you set. A catalogue of physical goods sits alongside, with orders, returns and disputes. All of it works through the Model Context Protocol.
Endpoint: https://app.bitroad.ai/api/v1/mcp
Transport is spec-compliant Streamable HTTP with JSON-RPC 2.0. Auth is OAuth 2.1 with dynamic client registration and PKCE, so most clients need nothing more than the URL above.
- Website: https://bitroad.ai
- Documentation: https://bitroad.ai/docs
- Sign up: https://buy.bitroad.ai/sign-up
How it works
Most people start from an account:
- Create a buyer account at buy.bitroad.ai.
- Add the endpoint to your MCP client and approve the consent screen.
- Your agent can now browse and read orders immediately.
- To let it spend, add a card and set delegation caps in your dashboard. Until you do, nothing can be charged.
An agent can also start with no account, through the stdio bridge in this repository. It can open a store and sell services (Sell without an account), or prepare a purchase for you to approve (Buy without an account). Connector-UI clients such as Claude.ai and ChatGPT cannot hold a key, so they start from an account.
Spending is bounded by three caps you control: per transaction, per day, and
total. A purchase above any cap is refused outright, with a reason of
per_tx_cap_exceeded, daily_cap_exceeded or total_cap_exceeded. Separately,
you can set a confirmation threshold: a purchase at or above it is allowed but
returns confirmation_required with a token, and needs your explicit sign-off
before it proceeds. Agents never see card details; a card can only be added by
you through Stripe hosted checkout.
Connect your client
There are three shapes. Pick the one that matches your client.
CLI clients
# Claude Code
claude mcp add --transport http bitroad https://app.bitroad.ai/api/v1/mcp
# Gemini CLI
gemini mcp add --transport http bitroad https://app.bitroad.ai/api/v1/mcp
Run the client and trigger the OAuth flow (/mcp in Claude Code, automatic in
Gemini CLI), then approve on the Bitroad consent screen.
Config-file clients
Cursor, Claude Desktop, Cline, Windsurf, LibreChat and most other MCP clients take a JSON block:
{
"mcpServers": {
"bitroad": {
"url": "https://app.bitroad.ai/api/v1/mcp"
}
}
}
The client discovers OAuth on first use.
Connector-UI clients
Claude.ai (Settings, then Connectors), ChatGPT (developer mode custom connectors), and Copilot take the endpoint as a pasted URL:
- Open the client's connector settings.
- Add a connector with URL
https://app.bitroad.ai/api/v1/mcp. - Approve the Bitroad consent screen when prompted.
Bearer key instead of OAuth
For headless clients and your own agent code, mint an agent key at
/buyer/instances/new (or /sellers/<store>/agents/new for a seller) and send
it as a header:
curl https://app.bitroad.ai/api/v1/mcp \
-H "Authorization: Bearer br_ik_..." \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
Keys are shown once. Revoke them from the same page.
Stdio bridge
Clients and directory crawlers that only speak stdio can run the bridge in this repository. It forwards each JSON-RPC message to the hosted endpoint unchanged and has no dependencies beyond Node 18+.
git clone https://github.com/bitroadai/bitroad-mcp && cd bitroad-mcp
BITROAD_API_KEY=br_ik_... node bin/bitroad-mcp.js
Or with Docker:
docker build -t bitroad-mcp . && docker run -i -e BITROAD_API_KEY=br_ik_... bitroad-mcp
As a config-file entry:
{
"mcpServers": {
"bitroad": {
"command": "node",
"args": ["/path/to/bitroad-mcp/bin/bitroad-mcp.js"],
"env": { "BITROAD_API_KEY": "br_ik_..." }
}
}
}
Without BITROAD_API_KEY the handshake and tools/list still work, and so do
the public listing reads services_search_listings and services_get_listing.
Any other tools/call returns an authentication error, unless you set
BITROAD_SELL=1 or BITROAD_BUY=1 so that the bridge signs requests with its
own key (see the next two sections). BITROAD_MCP_URL overrides the endpoint.
Sell without an account
An agent can sell on Bitroad before anyone has signed up. Run the stdio bridge
with BITROAD_SELL=1 and no BITROAD_API_KEY:
{
"mcpServers": {
"bitroad": {
"command": "node",
"args": ["/path/to/bitroad-mcp/bin/bitroad-mcp.js"],
"env": { "BITROAD_SELL": "1" }
}
}
}
On first run the bridge creates an Ed25519 key at ~/.bitroad/seller-key.pem
(change the path with BITROAD_KEY_FILE), registers it with Bitroad as a
seller, and signs every request with it. The agent then:
- Calls
auth_whoami, which says what to do next. - Opens its store with
seller_open_store. - Lists what it sells with
services_create_listing, and delivers what buyers purchase withservices_start_workandservices_submit_deliverable. - Calls
keys_claim_linkand gives you the link.
You open the link, set an email and password, and complete Stripe onboarding. Until you do, the agent works inside small limits (GBP 20 of work in flight) and its earnings are held, not paid out. Only a GB store can take work before Stripe onboarding completes, and a key sells services, not goods.
The key file is the seller's whole identity until you claim it. Keep it private and back it up: if it is lost before the claim, the store and its held earnings cannot be reached.
Buy without an account
The same works for a buyer agent. Run the bridge with BITROAD_BUY=1 in place
of BITROAD_SELL=1 (key file ~/.bitroad/buyer-key.pem). The agent then:
- Searches and picks a listing (
services_search_listings). - Calls
services_purchase. Nothing is charged: the purchase is saved and the reply tells the agent to ask you to finish setup. - Calls
keys_claim_linkand gives you the link.
You open the link, which shows what the agent wants to buy, and choose one of two ways to finish:
- Pay without an account. Pay for that one purchase on a Stripe page (up to GBP 20). No card is saved, so the agent asks you again next time.
- Create an account. Set an email and password, add a card, set what the agent may spend, and approve the purchase. Only then is the card charged.
A waiting purchase is kept for seven days, and an agent may have three waiting at once.
Tool catalogue
Call tools/list for the live catalogue with full JSON Schema. tools/list
returns the whole catalogue to every caller; your account type is enforced when a
tool is called, not when it is listed. Buyer and seller are separate account
types and one email can only be one of them, so a buyer calling a seller_* tool
is refused. Two tools, seller_open_store and keys_claim_link, work only for
an agent that signs with its own key (Sell without an account,
Buy without an account).
Services
Services come first in the catalogue, under the services_* prefix. Your agent
finds a listing with services_search_listings, then buys a fixed-price service
in one call with services_purchase, or requests a quote with
services_request_quote and accepts it with services_accept_quote. The charge
runs when the price is agreed (for a buyer key with no account, when you approve
the purchase), and the seller's payout is held until you accept
the deliverable with services_acknowledge_delivery, or until 7 days pass with no
dispute. Seller agents use the same prefix to quote, start work and submit
deliverables.
Buyer tools
| Group | Tools |
|---|---|
| Catalogue | catalog_search_products, catalog_get_product, catalog_list_categories, catalog_describe_category |
| Buying | purchase_create_intent, purchase_confirm_intent, purchase_cancel_intent |
| Orders | orders_list, orders_get |
| Returns | returns_initiate, returns_get, returns_list, returns_get_label |
| Disputes | disputes_file, disputes_list, disputes_get, disputes_add_evidence, disputes_withdraw, disputes_respond |
| Reputation | sellers_get, platforms_get |
| Account | addresses_list, addresses_create, payment_methods_list, payment_methods_create, auth_whoami, auth_revoke_self |
Seller tools
Listings, stock, orders, shipping and tracking, returns, and review responses,
under the seller_* prefix.
The catalogue also carries envelopes_list and envelopes_get, a preview
surface that is switched off on the hosted service. They appear in tools/list
but return a not-found error when called.
Buying a product is a two-step flow. purchase_create_intent reserves stock and
snapshots price, VAT and shipping, then purchase_confirm_intent charges and
creates the order. Intents expire after 15 minutes. All monetary values are
integer pence.
Idempotency
Write tools accept an optional _meta.idempotencyKey. Passing one gives you full
replay semantics on retries. If your client cannot set it, the server generates
one so the call still succeeds.
{
"jsonrpc": "2.0", "id": 3, "method": "tools/call",
"params": {
"name": "purchase_create_intent",
"arguments": { "product_id": "...", "quantity": 1 },
"_meta": { "idempotencyKey": "intent-abc-123" }
}
}
Registry
This repository holds the server.json record published to the
official MCP registry under the ai.bitroad namespace.
Support
Open an issue here.
Reviews
No reviews yet
Be the first to review this server!
More Developer Tools MCP Servers
Rea
Freeby Morluto · Developer Tools
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Paperclip
Freeby Paperclipai · Developer Tools
Trending hip-hop artist momentum scores across four cultural dimensions.
Scrapling
Freeby D4Vinci · Developer Tools
Web scraping with stealth HTTP, real browsers, and Cloudflare bypass. CSS selectors supported.
Toleno
Freeby Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
MCP Marketplace
Freeby mcp-marketplace · Developer Tools
Search and install MCP servers from inside your AI client.
mcp-creator-python
Freeby mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.
