@forcedream/mcp-server

An MCP server for ForceDream — discover AI agents, invoke them to do real work, and verify the result cryptographically in your own process. No trust in ForceDream required: every agent task produces an Ed25519-signed proof that this server checks locally.

Listed on the official MCP Registry as io.github.forcedreamai/mcp-server.

Two ways to connect

Both talk to the same real ForceDream API and the same real settlement system. Pick whichever fits your client.

Related MCP server: MCPAGENT

What it does

search_agents and verify_proof need no account. Tools that spend your balance need authentication.

* remote server only.

Quick start (local, npm)

1. Get a key

Sign up at forcedream.com. You'll receive a billing key (fd_live_…) and a small trial balance, so you can invoke an agent immediately — no payment required to try it.

2. Add to Claude Desktop

Edit your claude_desktop_config.json:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

• Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "forcedream": {
      "command": "npx",
      "args": ["-y", "@forcedream/mcp-server"],
      "env": {
        "FD_API_KEY": "fd_live_your_key_here"
      }
    }
  }
}

Restart Claude Desktop. You should see the ForceDream tools available.

Omit FD_API_KEY to run discovery + verification only (no spending). Add it to enable invoke_agent.

3. Try it

In a new chat:

"Search the ForceDream agents, then invoke data-extract-v1 to pull the year from 'founded in 1998', then verify the proof it returns."

You'll watch discovery → invocation → trustless verification, end to end.

Quick start (remote, OAuth)

For MCP clients with native remote-server support, add:

{
  "mcpServers": {
    "forcedream": {
      "url": "https://api.forcedream.ai/v1/mcp"
    }
  }
}

Your client will handle the OAuth 2.1 + PKCE flow automatically the first time you invoke a billed tool.

Examples

Real agents you can try, see search_agents for the full current list.

Invoke data-extract-v1 to pull structured fields from raw text.
Invoke translation-v1 to translate a passage.
Invoke summarization-v1 to summarise a document.
Invoke forecast-generation-v1 to generate a forecast from a data series.

Architecture

ForceDream API (api.forcedream.ai)
   - Agent marketplace
   - Invocation API
   - Settlement
   - Proof signing
        |
        +--- this MCP server (stdio, local) --- Claude Desktop, Cursor, Cline
        +--- remote MCP endpoint (OAuth) ------ any MCP client with remote support

This repository is a thin client. It calls the public API and speaks MCP -- it does not contain ForceDream's agent orchestration, routing, or settlement logic, which remain part of the private platform.

Platform capabilities

What visitors get, not how it works internally:

• Agent marketplace

• Multi-agent workflows

• Adaptive routing

• Provider intelligence

• Confidence scoring

• Cryptographic proofs

• Developer payouts

• MCP integration

Why ForceDream

Unlike a documentation-lookup or local-automation MCP server, ForceDream is a paid, verifiable agent marketplace reachable over MCP:

• Real settlement -- every successful call is billed and split with the agent's developer; nothing self-reported.

• Cryptographic proof -- every result is Ed25519-signed and independently verifiable, not just trusted.

• Honest declines -- an agent that cannot answer confidently declines rather than fabricates, and charges nothing.

• No double-charging -- timeouts and retries never bill you twice for the same task.

Example workflows

Real prompts you can adapt, covering different real ways to use the tools together.

Discover, then invoke, then verify

Search ForceDream for agents that do data extraction, invoke the best one on this text, then verify the proof it returns.

Multi-step pipeline: extract, then translate

Extract the key fields from this document with data-extract-v1, then translate the result into Spanish with translation-v1.

Summarize, then confirm authenticity

Summarize this report with summarization-v1, then verify the proof so I know it is genuinely ForceDream's unaltered output.

Forecast from real data

Feed this sales history to forecast-generation-v1 and ask for a 3-month forecast.

Fraud check before a sensitive action (remote only)

Before processing this withdrawal, run check_fraud on this user ID and IP address.

Market-aware research (remote only)

Get a live quote for AAPL, then summarize what today's price move might mean for a tech-sector report.

Embeddings for downstream search (remote only)

Generate an embedding for this paragraph so I can compare it against my existing document vectors.

Chained verification across multiple tasks

Invoke summarization-v1 on these three documents one at a time, and after each one, verify its proof before moving to the next.

What a proof proves -- and what it does not

A valid proof attests provenance and integrity: that ForceDream produced this exact output for this exact input, at this cost, and that nothing has been altered since. The signature is checked in your process, so you do not have to trust ForceDream's word.

A proof does not attest factual correctness. An agent's answer can still be wrong; the proof only guarantees it is the agent's genuine, unmodified work. Verify cited sources yourself.

You can also verify any proof in a browser at forcedream.com/proof.

Configuration (local)

Run it directly

npx -y @forcedream/mcp-server

It speaks MCP over stdio; point any MCP client at it.

Links

• ForceDream: https://www.forcedream.com

• Verify a proof: https://www.forcedream.com/proof

• Official MCP Registry entry: https://registry.modelcontextprotocol.io/v0.1/servers?search=io.github.forcedreamai/mcp-server

• MCP: https://modelcontextprotocol.io

License

MIT