Skip to content

Releases: forcedreamai/forcedream-mcp

Release list

v0.4.2 — Registry publication, OAuth, proof verification, new tools

v0.4.2 — Registry publication, OAuth, proof verification, new tools Latest
Latest

Choose a tag to compare

View all tags
@forcedreamai forcedreamai released this 11 Jul 13:18
v0.4.2
9166b75

Real, verified state of the ForceDream MCP server as of this release. Nine real tools, live on both a local npm package and a hosted OAuth server, published to the official MCP Registry.

What's new since the initial 0.1.0 release

  • Split into this standalone public repository (forcedreamai/forcedream-mcp), separate from ForceDream's private monorepo.
  • Three new tools: search_reliability, search_costs, search_providers -- real, system-measured data, not new computation.
  • Real fd-verify CLI, with --json and --quiet flags for CI/scripting use.
  • FD_MOCK_MODE for invoke_agent -- test locally with zero real network calls and zero balance spent.
  • Published to the official MCP Registry as io.github.forcedreamai/mcp-server.
  • Full CI (GitHub Actions), issue templates, and this changelog.

Breaking changes

None. All changes are additive.

Tools (9 total)

Keyless: search_agents, verify_proof, search_reliability, search_costs, search_providers
Billed: invoke_agent (both surfaces), check_fraud, generate_embedding, market_quote (remote only)

MCP Registry & directory listings

Listed on the official MCP Registry. Directory listing status: PulseMCP integrates with the official registry automatically; Smithery and Glama require separate, explicit submission (in progress).

OAuth support

The remote server (https://api.forcedream.ai/v1/mcp) supports full OAuth 2.1 + PKCE, discovered automatically by clients with native remote-MCP support. Verified end-to-end this release cycle: real client registration, consent, token exchange, and authenticated invocation.

Proof verification

Every invoke_agent call returns a real, Ed25519-signed proof. Verify it three ways -- the verify_proof tool, the fd-verify CLI, or the production web verifier at forcedream.com/proof -- and all three will agree, since they all run the identical verification logic.

Marketplace integration

Agents invoked through this MCP server are the same real, live agents on ForceDream's marketplace -- same pricing, same settlement, same proofs. No separate MCP-specific agent roster.

Bug fixes this cycle

Five real, distinct instances of the same serious issue were found and fixed: several billed endpoints (both MCP-specific and REST) were not checking whether a charge actually succeeded before returning results, meaning insufficient-balance callers could receive real, paid output for free. Each fix verified live by draining a real test account to zero and confirming correct rejection.

Roadmap

  • invoke_chain / verify_chain -- real backend infrastructure exists; blocked on an account-key vs. billing-key auth design decision, not yet resolved.
  • Signature rotation.
  • Agent sandboxing.
  • Real, rebuilt usage analytics (the original design used fabricated Redis keys and was never shipped).

Links

Assets 2
Loading