What is the key difference between Forcedream MCP and Anomaly MCP?

Forcedream MCP belongs to the Aggregators category with local stdio execution, while Anomaly MCP belongs to the Aggregators category with local stdio execution.

How do I install Forcedream MCP or Anomaly MCP in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Forcedream MCP and Anomaly MCP free or paid?

Forcedream MCP operates under a Paid Service model (API Key required). Anomaly MCP operates under a Paid Service model (No auth required).

Which MCP server has more tools and community activity?

Forcedream MCP lists 14 tools with 2 views and 1 GitHub stars. Anomaly MCP lists 16 tools with 4 views and 0 GitHub stars.

Can I use both Forcedream MCP and Anomaly MCP together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Forcedream MCP vs Anomaly MCP

In-depth architectural comparison of the Forcedream MCP and Anomaly MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

Forcedream MCP

Aggregators · Local stdio

Quality: 61/100 (Good) | Auth: API Key required

Anomaly MCP

Aggregators · Local stdio

Quality: 64/100 (Good) | Auth: No auth required

Verdict Summary: Choose Forcedream MCP if you need specialized Aggregators tools running via a local process. Choose Anomaly MCP if your workspace requires Aggregators integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Forcedream MCP when:

You need dedicated capabilities in the Aggregators domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Paid Service).
You have access to required keys: FD_API_KEY.
Primary tools included: forcedream_verify_proof, forcedream_search_agents, forcedream_invoke_agent.

Explore Forcedream MCP Details

Choose Anomaly MCP when:

You need dedicated capabilities in the Aggregators domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Paid Service).
You have access to required keys: ANOMALY_API_BASE.
Primary tools included: health_check, anomaly_scan, token_scan.

Feature & Specification Comparison

Specification	Forcedream MCP forcedreamai Aggregators	Anomaly MCP forgemeshlabs Aggregators
Summary	Discover, invoke, and cryptographically verify AI agents on a paid agent marketplace. 13 tools spanning code generation (6-module engineering verification), security scanning (OSV.dev + GitGuardian), and lead scoring (8 real sources). Every result is Ed25519-signed and independently verifiable -- no trust in the platform required. Install: npx -y @forcedream/mcp-server.	Real-time anomaly detection powered by NASA-derived sequence mining across blockchain, mempool, stablecoin depeg, aviation, and GitHub signals via x402 USDC micropayments on Base. npx -y @forgemeshlabs/anomaly-mcp
Category & Scope

Tools & Capabilities Breakdown

Forcedream MCP Tools (14)

forcedream_verify_proof

Independently verify that a ForceDream agent proof is authentic and untampered, using public-key cryptography. Provide a task_id (proof is fetched from the public endpoint) or a full proof object. Verification runs locally — ForceDream is never asked whether the proof is valid; the Ed25519 math decides. No account or key needed.

forcedream_search_agents

Discover ForceDream agents and their honest, system-derived metrics (proof_count, success_rate). Optionally filter by capability (e.g. "research:citation") or free-text query. No key needed. Every agent listed has real cryptographic proofs you can verify with forcedream_verify_proof.

forcedream_invoke_agent

Invoke a ForceDream agent to do real work. SPENDS your balance — requires FD_API_KEY in the server env. Returns the output, what you were charged, and a proof_id you can verify with forcedream_verify_proof. Handles honest declines (charged 0) and insufficient balance gracefully. Invokes once; never double-charges. Use this for any agent WITHOUT a dedicated tool. For security-scan-v1, data-extract-v1, or lead-score-v1 specifically, prefer forcedream_security_scan, forcedream_extract_data, or forcedream_score_lead instead -- same underlying agents, simpler input shape.

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

Forcedream MCP Configuration

mcpServers (Claude Desktop / Cursor)

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

Anomaly MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "forgemeshlabs-anomaly-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@forgemeshlabs/anomaly-mcp"
      ],
      "env": {
        "ANOMALY_API_BASE": "YOUR_ANOMALY_API_BASE_HERE"
      }
    }
  }
}

Frequently Asked Questions

Forcedream MCP is categorized under Aggregators and uses a local stdio subprocess. In contrast, Anomaly MCP belongs to Aggregators using local stdio subprocess. Select Forcedream MCP when you need capabilities focused on aggregators and Anomaly MCP when you require tools for aggregators.

More alternatives to Forcedream MCP More alternatives to Anomaly MCP Aggregators category hub