
Bloom Exchange
io.github.astyboyy-ship-itPublished by GitHub account astyboyy-ship-itv0.2.0Updated Nov 20, 2026
Negotiate in a double-blind sandbox and verify Ed25519 receipts. Agent-to-agent clearing over A2A.
The publisher's own server: Exchange.news — Crypto offers, campaigns and news
Overview
Lets an assistant negotiate a double-blind price deal with another agent on a Bloom Exchange node and verify the Ed25519-signed settlement receipt.
- What you can do
- Negotiate a deal against a mandate (ceiling price, budget, SLA tier, net days) on a Bloom Exchange node
- Verify a BLOOM-XCH receipt offline or against the issuer's signed Agent Card
- Publish an agent intent for clearing over A2A JSON-RPC
- Optionally poll an event feed for wake-ups and post-settlement hooks when the node enables it
- When to use it
- Use it when you want an IDE or desktop agent to run a machine-to-machine procurement or price negotiation against a Bloom Exchange node and get a verifiable, signed settlement receipt, typically in a sandbox or test setup rather than a live payment flow.
- Requirements
- Runs locally over stdio via npx from the npm package @bloom-exchange/mcp, on Node 20 or newer. Needs a reachable Bloom Exchange node; BLOOM_EXCHANGE_URL sets its base URL (default Optional BLOOM_ACCESS_KEY switches from the sandbox to production clearing, and BLOOM_AGENT_NAME sets how the agent introduces itself. Desktop only.
Installation
In SourceWeft
- Open Bloom Exchange in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
Bloom Exchange
Two AI agents negotiate a deal over A2A JSON-RPC while each side's price limits stay sealed in salted SHA-256 commitments that the other side's engines never see; a prompt-injection firewall screens every message, deterministic clamps keep every offer inside both mandates, and the result is an Ed25519-signed receipt anyone can verify offline.
Bloom Exchange is the reference implementation of the Bloom Clearing Protocol, an extension profile of A2A v1.0 that maps settlement to AP2 mandates and Stripe / x402 payloads, with an MCP server so any IDE agent can use it. Apache-2.0.
Try it (no API key, no account, no model)
Negotiations run on deterministic engines with the same vault, firewall, clamps and signatures as production. Requires Node 22.18+ for the repository scripts; the published npm packages run on Node 20+.
One command, every claim checked. Starts two nodes with separate keys, fires a prompt-injection payload at the firewall, checks that no private number reaches the attacker, settles a cross-node deal, then verifies the receipt with the CLI (and checks that a $1 tamper and the wrong key both fail):
Verify a receipt without cloning anything. The script above prints the folder where it saved receipt.json and the issuer's card.json; on the desk, the Enclave Inspector's JSON button downloads a receipt and the card is at /.well-known/agent-card.json.
Give your agent the tools (Claude Code, with a node running on :3000):
Cursor, Claude Desktop or any MCP client:
What you get
Repository
Every endpoint in packages/core/src/http is a plain (Request) => Response function. apps/node mounts them in Next.js; handle() from @bloom-exchange/core/http/router serves them from any runtime (Node, Bun, Deno, Workers) or in-process.
Connect an agent
TypeScript (Node ≥ 20, Deno, Bun or the browser)
Claude Code, Cursor or any MCP client (setup above)
Ask your agent to "negotiate a 12-month license with a $52k ceiling on Bloom and verify the receipt". Tools: negotiate, verify_receipt, publish_intent. For a remote server, npx -y -p @bloom-exchange/mcp bloom-exchange-mcp-http serves stateless Streamable HTTP at /mcp. Optional environment: BLOOM_ACCESS_KEY, BLOOM_AGENT_NAME.
Verify any receipt
Installed, the same command is bloom-verify receipt.json. Inside this repository: npm run verify -- receipt.json.
Raw A2A JSON-RPC
Two nodes, one cross-node deal each way
deploy/docker-compose.yml runs two Sovereign nodes, node-alpha (:3001) and node-beta (:3002). Each has its own Ed25519 root key and its own state, and each is pre-wired to the other through BLOOM_PEERS:
No Docker? npm run build && npm run demo:two-node:local starts the same two nodes as local processes with fresh keys. Output from a real run:
Each node verifies the other's signed Agent Card (GET /api/exchange/peers). An agent from one node negotiates on the other, presenting its home node's card. Each receipt names both nodes and verifies only against its issuer's key. The same deal with the SDK:
Run a single node with docker compose -f deploy/docker-compose.yml up node-alpha. Kubernetes runs one node per namespace: kubectl apply -k deploy/k8s (see deploy/k8s/kustomization.yaml). With no model keys and no settlement webhook, nodes make no outbound calls beyond their configured peers. Configuration lives in .env.example.
Access keys are optional. They switch enclaves from the sandbox to production clearing and unlock operator views: npm run key:issue -- --role operator --holder "You".
Develop
Every test has a conformance id in SPEC.md Appendix B. Appendix A gives byte-exact vectors for canonical JSON, key derivation, round hashes, commitments, certificate ids and Ed25519 signatures, so implementations in other languages can match the reference exactly.
What is and is not built
- Built: everything above runs today, end to end, with tests.
- Opt-in: an event feed for wake-ups and post-settlement hooks (
BLOOM_EVENTS=1): cursor polling, SSE, an MCPpoll_eventstool, and webhook, JSONL and dry-run adapters. It carries no mandate figures. See docs/EVENTS.md. - Format only:
bloom.exchange/<agent>links. They are a naming format that resolves to a node's signed Agent Card; there is no public registry or resolver yet. - Open: in v0.1 the vault runs on the provider's node, so the counterparty trusts that operator not to read its mandate. The roadmap is neutral hosted clearing, attested enclaves and federation. See SPEC.md §12.
Release notes are in CHANGELOG.md.
License
Apache License 2.0. See NOTICE.
The two paintings in apps/node/public/paintings are public-domain works: Jean-Honoré Fragonard, c. 1760, and Claude Lorrain, 1653. They come from Wikimedia Commons under the Public Domain Mark 1.0, and the Apache License does not cover them. Attribution is in NOTICE and CREDITS.
Source: README.md at commit 1f0ca8c
Tools
0Version history
2- v0.2.0LatestNov 19, 2026
- v0.1.0Nov 19, 2026
Score
50% 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 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 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 Exchange integrations
Exchange.news — Crypto offers, campaigns and news
news.exchangeOfficial publisher
A read-only remote catalog that lets an assistant look up crypto signup codes, partner links, campaign dates and Exchange.news stories.

PlaylistExchange
Published by GitHub account PlaylistExchange
Search and read user-curated music playlists by keyword, genre or moment, and post your own Spotify playlists to PlaylistExchange.
AI Agent Promotion Exchange
com.aiagentpromotionexchange
Local MCP server that lets an assistant onboard and trade on the AI Agent Promotion Exchange, with keys kept on the user's machine.

AI Agent Promotion Exchange
Published by GitHub account robertmarshii
Lets an assistant onboard onto the AI Agent Promotion Exchange and trade promotion listings with other agents, with keys kept on the local machine.
ECB exchange rates
com.foreverworks
ECB exchange rates's local MCP server, published by foreverworks.com; no sign-in required; STDIO; 4 tools.