Forcedream MCP vs Ncp — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Forcedream MCP vs Ncp
In-depth architectural comparison of the Forcedream MCP and Ncp 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
Ncp
Aggregators · Local stdio
Quality: 64/100 (Good) | Auth: API Key required
Verdict Summary: Choose Forcedream MCP if you need specialized Aggregators tools running via a local process. Choose Ncp 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).
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.
NCP orchestrates your entire MCP ecosystem through intelligent discovery, eliminating token overhead while maintaining 98.2% accuracy.
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 is categorized under Aggregators and uses a local stdio subprocess. In contrast, Ncp belongs to Aggregators using local stdio subprocess. Select Forcedream MCP when you need capabilities focused on aggregators and Ncp when you require tools for aggregators.
Real security review for code: OWASP Top 10, injection, secrets, and dependency risks. Cross-references imported dependencies against OSV.dev for real CVEs, and scans for hardcoded secrets via GitGuardian's real-time detection (400+ types). SPENDS your balance — requires FD_API_KEY. Returns severity-graded findings, a risk score, what you were charged, and a proof_id.
forcedream_extract_data
Structured JSON extraction from unstructured text -- grounded in real, live verification, not just pattern-matching. Pulls requested fields, nulls anything missing, never guesses. Cross-references detected proper-noun entities (companies, people, places) against Wikidata to confirm which extracted values are independently verified vs. unconfirmed. SPENDS your balance — requires FD_API_KEY. Returns the extracted rows, what you were charged, and a proof_id.
forcedream_score_lead
Score sales leads hot/warm/cold with weighted signals and a recommended next action — grounded in real, live verification. Cross-references detected companies, domains, and locations against 8 real sources: Wikidata, UK Companies House, EU VIES VAT validation, postcodes.io, Google PageSpeed Insights, OpenStreetMap Nominatim, DNS/MX records, and live HTTP checks. Global by design — 5 sources work for any lead worldwide; 3 regional ones (UK/EU) apply only when genuinely detected. SPENDS your balance — requires FD_API_KEY.
forcedream_generate_code
Generates real, working code with real, live verification — not just an LLM's opinion. Every response is checked with 6 independent modules: syntax validation, dependency health, security scanning (OSV.dev + GitGuardian), complexity analysis, documentation coverage, and test detection. Returns a deterministic quality score, honest risk assessment, and deployment readiness. SPENDS your balance — requires FD_API_KEY.
forcedream_generate_sentiment
Real, 14-source sentiment analysis — not just an LLM's opinion. Combines lexicon-based sentiment (VADER, AFINN), a transformer model (HuggingFace DistilBERT), toxicity (Google Perspective), entity/location verification (Wikidata, OpenStreetMap), news and community alignment (GDELT, Hacker News), grammar, readability, and language detection into one deterministic overall sentiment, urgency, and business impact score. SPENDS your balance — requires FD_API_KEY.
forcedream_check_fraud
Real fraud risk assessment using AbuseIPDB IP reputation data. SPENDS your balance — requires FD_API_KEY. Returns risk_score, signals, and an allow/review/block verdict, WORM-sealed.
forcedream_generate_embedding
Real 1024-dim vector embedding via Voyage voyage-3.5, retrieval-optimised. SPENDS your balance (per-token charge) — requires FD_API_KEY. Returns the vector, dimensions, token count, WORM-sealed.
forcedream_market_quote
Real, live market quote for a stock symbol via Alpha Vantage: price, change %, volume, day high/low, liquidity score. SPENDS your balance — requires FD_API_KEY. Hard-cached, WORM-sealed.
forcedream_search_reliability
Real, system-measured reliability per agent: success_rate, avg_latency_ms, sample_size. No key needed. Same real data as forcedream_search_agents' health field, exposed standalone for reliability-focused queries.
+2 more tools listed on main page
Ncp Tools (1)
sequentialthinking
A detailed tool for dynamic and reflective problem-solving through thoughts.
This tool helps analyze problems through a flexible thinking process that can adapt and evolve.
Each thought can build on, question, or revise previous insights as understanding deepens.
When to use this tool:
- Breaking down complex problems into steps
- Planning and design with room for revision
- Analysis that might need course correction
- Problems where the full scope might not be clear initially
- Problems that require a multi-step solution
- Tasks that need to maintain context over multiple steps
- Situations where irrelevant information needs to be filtered out
Key features:
- You can adjust total_thoughts up or down as you progress
- You can question or revise previous thoughts
- You can add more thoughts even after reaching what seemed like the end
- You can express uncertainty and explore alternative approaches
- Not every thought needs to build linearly - you can branch or backtrack
- Generates a solution hypothesis
- Verifies the hypothesis based on the Chain of Thought steps
- Repeats the process until satisfied
- Provides a correct answer
Parameters explained:
- thought: Your current thinking step, which can include:
* Regular analytical steps
* Revisions of previous thoughts
* Questions about previous decisions
* Realizations about needing more analysis
* Changes in approach
* Hypothesis generation
* Hypothesis verification
- nextThoughtNeeded: True if you need more thinking, even if at what seemed like the end
- thoughtNumber: Current number in sequence (can go beyond initial total if needed)
- totalThoughts: Current estimate of thoughts needed (can be adjusted up/down)
- isRevision: A boolean indicating if this thought revises previous thinking
- revisesThought: If is_revision is true, which thought number is being reconsidered
- branchFromThought: If branching, which thought number is the branching point
- branchId: Identifier for the current branch (if any)
- needsMoreThoughts: If reaching end but realizing more thoughts needed
You should:
1. Start with an initial estimate of needed thoughts, but be ready to adjust
2. Feel free to question or revise previous thoughts
3. Don't hesitate to add more thoughts if needed, even at the "end"
4. Express uncertainty when present
5. Mark thoughts that revise previous thinking or branch into new paths
6. Ignore information that is irrelevant to the current step
7. Generate a solution hypothesis when appropriate
8. Verify the hypothesis based on the Chain of Thought steps
9. Repeat the process until satisfied with the solution
10. Provide a single, ideally correct answer as the final output
11. Only set nextThoughtNeeded to false when truly done and a satisfactory answer is reached