Side-by-Side Model Context Protocol Comparison
Forcedream MCP vs Aiskillstore
In-depth architectural comparison of the Forcedream MCP and Aiskillstore 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
Aiskillstore
Aggregators · Remote HTTP/SSE
Quality: 53/100 (Good) | Auth: API Key required
Verdict Summary: Choose Forcedream MCP if you need specialized Aggregators tools running via a local process. Choose Aiskillstore if your workspace requires Aggregators integration with remote web transport. 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.
Choose Aiskillstore when:
- You need dedicated capabilities in the Aggregators domain.
- You prefer remote streaming HTTP/SSE transport architecture.
- Your security boundary fits: API Key required (Free / Open Source).
- You have access to required keys:
SKILL_STORE_URL. - Primary tools included: search_skills, get_skill, get_skill_schema.
Feature & Specification Comparison
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
Aiskillstore Configuration
