Skip to content
MCP server

Bloom Exchange

MCP server for negotiating deals between AI agents with sealed limits and signed receipts

Runs locally
Install
Pricing
Open source
Platforms
CLI, API, Self-hosted
Runs
Locally
Version
0.1.0
Listing updated
today

Similar MCP servers

About Bloom Exchange

Bloom Exchange is an open-source MCP server for agent tooling. It runs locally on your machine and is started by your AI client.

The README says Bloom Exchange lets two AI agents negotiate a deal over A2A JSON-RPC while each side keeps its price limits hidden in salted SHA-256 commitments. A prompt-injection firewall screens incoming messages, and deterministic clamps keep every offer within both parties' mandates before it is sent or signed.

The result of a negotiation is an Ed25519-signed receipt that can be checked offline with the bloom-verify CLI or the SDK. The project positions itself as a reference implementation of the Bloom Clearing Protocol, an extension profile of A2A v1.0 that maps settlement to AP2 mandates and Stripe or x402 payloads.

The repository includes a sandbox node that runs deterministic negotiation engines without an API key or model, plus an MCP server exposing negotiate, verify_receipt and publish_intent tools for IDE agents such as Claude Code and Cursor. The README notes that in v0.1 the vault runs on the provider's node, so the counterparty must trust that operator with its mandate.

Install

Run in a terminal

claude mcp add bloom-exchange --env BLOOM_ACCESS_KEY='<BLOOM_ACCESS_KEY>' -- npx -y @bloom-exchange/mcp

Add to claude_desktop_config.json

{
  "mcpServers": {
    "bloom-exchange": {
      "command": "npx",
      "args": [
        "-y",
        "@bloom-exchange/mcp"
      ],
      "env": {
        "BLOOM_ACCESS_KEY": "<BLOOM_ACCESS_KEY>"
      }
    }
  }
}

Add to ~/.cursor/mcp.json

{
  "mcpServers": {
    "bloom-exchange": {
      "command": "npx",
      "args": [
        "-y",
        "@bloom-exchange/mcp"
      ],
      "env": {
        "BLOOM_ACCESS_KEY": "<BLOOM_ACCESS_KEY>"
      }
    }
  }
}

Add to .vscode/mcp.json

{
  "servers": {
    "bloom-exchange": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@bloom-exchange/mcp"
      ],
      "env": {
        "BLOOM_ACCESS_KEY": "<BLOOM_ACCESS_KEY>"
      }
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "bloom-exchange": {
      "command": "npx",
      "args": [
        "-y",
        "@bloom-exchange/mcp"
      ],
      "env": {
        "BLOOM_ACCESS_KEY": "<BLOOM_ACCESS_KEY>"
      }
    }
  }
}

Add to your client's MCP settings (most use this shape)

{
  "mcpServers": {
    "bloom-exchange": {
      "command": "npx",
      "args": [
        "-y",
        "@bloom-exchange/mcp"
      ],
      "env": {
        "BLOOM_ACCESS_KEY": "<BLOOM_ACCESS_KEY>"
      }
    }
  }
}

Using several servers? Build one config file with the MCP config generator.

Configuration

  • BLOOM_EXCHANGE_URLBase URL of the Bloom Exchange node (default http://localhost:3000)
  • BLOOM_ACCESS_KEYOptional Bloom access key for production enclaves instead of the sandbox
  • BLOOM_AGENT_NAMEHow this client's agent introduces itself to the counterparty

Tools this server provides (3)

Taken from the project documentation; the running server may differ.

negotiate
Negotiate a deal between agents within mandate limits.
verify_receipt
Verify a signed negotiation receipt.
publish_intent
Publish an intent to the exchange.

What it does

Sealed price limits
Each side's ceiling and budget are stored as salted SHA-256 commitments that the other party's engines never receive.
Deterministic offer clamping
Offers are clamped to both mandates by code rather than by the model before they are sent or signed.
Prompt-injection firewall
Incoming messages are screened for injection patterns, encoded payloads and hidden Unicode before any engine reads them.
Offline receipt verification
Signed receipts can be checked with the bloom-verify CLI without contacting the issuing node.
Sandbox without accounts
A local node runs negotiations on deterministic engines, requiring no API key, account or language model.

Good for

  • Letting a coding agent negotiate a software license within a set budget and verify the receipt
  • Running a procurement agent that buys from a supplier agent on another node
  • Checking the signature and digest of a negotiation receipt offline for audit
  • Testing agent-to-agent negotiation flows locally before connecting to a production enclave

Pricing

Open source

Apache-2.0 open source; run locally or self-hosted.

Bloom Exchange FAQ

Does the MCP server need an API key to run?

The README says the sandbox needs no API key, account or model. A Bloom access key is optional and only needed for production enclaves.

Which tools does the MCP server expose?

The README lists negotiate, verify_receipt and publish_intent.

What license is the project under?

The repository is licensed under Apache License 2.0.

Where is the counterparty's price limit visible in v0.1?

The README states that in v0.1 the vault runs on the provider's node, so the counterparty has to trust that operator not to read its mandate.

Is Bloom Exchange free?

Yes. Bloom Exchange is open source, so you can use and self-host it for free.

How do I add Bloom Exchange to Claude Code?

Run this command in your terminal: claude mcp add bloom-exchange --env BLOOM_ACCESS_KEY='<BLOOM_ACCESS_KEY>' -- npx -y @bloom-exchange/mcp

What are the best alternatives to Bloom Exchange?

The closest alternatives to Bloom Exchange are Pactwire, Mare Liberum · the open sea for agents, Agentiam MCP, LHUB agent service marketplace and Mare Liberum · the open sea for agents.

Where this comes from

  • Description: written from the project's README and its MCP Registry entry.
  • Install steps: from the official MCP Registry entry.

How AIPoweredBot checks servers