World Sense vs Claude Flow
A side-by-side look at the World Sense and Claude Flow MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose World Sense for developer tools work over a hosted endpoint; choose Claude Flow for coding agents. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose World Sense when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
arcane_overview, arcane_deltas, arcane_domain.
Choose Claude Flow when
- You need dedicated capabilities in the Coding Agents domain.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Coding Agents |
| Quality signal | 53/100 · Good | 49/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Remote HTTP/SSE | — |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 78,442 |
| Directory activity | 1 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 10 | Not listed |
| Full listing | View World Sense | View Claude Flow |
Tools & capabilities
World Sense tools 10
arcane_overviewCurrent ARCANE overview: Combined Threat Score, per-domain risk rows, cascade state, and cross-domain gauges as observed now. ARCANE NOTICES the present; it does not predict or advise. Check as_of/stale before treating as current.arcane_deltasWhat changed since yesterday across ARCANE's domains and primary-source senses (observed diffs only). Grounding-sense items fire once at onset then go quiet, so absence of an item is not calm. Check as_of/stale.arcane_domainDrill-down for one domain: observed risk/momentum series, current-state regime posterior, and news-coverage theme cards (coverage unusualness, not truth or importance). ARCANE NOTICES the present; it does not predict. Check as_of/stale.arcane_bilateralObserved bilateral signal-intensity across seven tracked country pairs (volume and tone indices, plus an observed escalation stage). An index of observed intensity between the pair, not a prediction of what happens next. Check as_of/stale.arcane_data_streamsLatest observations from ARCANE's primary-source physical senses (energy stocks, fires, sanctions, GPS interference, outages, and more) with provider, cadence, and attribution. Observed levels only; some senses go silent when their baseline saturates. Check as_of/stale.arcane_score_treeHow the Combined Threat Score is composed: per-domain roll-ups, applied premiums, and the design weights behind them, each carrying a live/config provenance tag. Weights are design configuration, not fitted parameters. Check as_of/stale.arcane_trigger_chainsObserved multi-stage trigger-chain state for five domains (stage activation, z-scores, and chain health). Descriptive state only, not a forecast; the chains were repaired 2026-07-02 and not yet exercised live. Check as_of/stale.arcane_trackerARCANE's live scenario tracker: for each pre-registered scenario, where the world is on its branching map — checkpoint COMPLETION as N/M (confirming signals fired of total), a direction of resemblance, staleness, and which fork checkpoints have fired or are pending. A live STATE view, NOT a forecast: completion is not a probability and direction is resemblance, not odds. ARCANE never states a scenario's likelihood. Check as_of/stale.arcane_system_statusFreshness of every public ARCANE key: push time, source as_of, and stale flag. Call this before treating any reading as current.arcane_capabilitiesWhat ARCANE's public World-Sense serves and what it explicitly does NOT serve, plus per-stream validation notes. ARCANE NOTICES present-state geopolitical risk from primary-source senses; it does not forecast, advise, or trade.
Claude Flow tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
World Sense
{
"mcpServers": {
"world-sense": {
"url": "https://mcp.arcaneforecasting.com/mcp"
}
}
}
Claude Flow
No confirmed install command for Claude Flow yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
World Sense is categorized under Developer Tools and uses a remote HTTP/SSE transport. Claude Flow belongs to Coding Agents and uses an install path we have not confirmed yet. Pick World Sense for developer tools work and Claude Flow for coding agents.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Claude Flow has no confirmed install command yet — follow its own setup instructions.
World Sense has no declared pricing — check the project's own site. Claude Flow has no declared pricing — check the project's own site. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add world-sense and claude-flow as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, World Sense has a quality signal of 53/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Claude Flow has 49/100 (Fair) with 3 views, 0 installs and 78,442 GitHub stars.