In-depth architectural comparison of the Chaos Index and Conspiracy Theory 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
Chaos Index
Social Media · Local stdio
Quality: 28/100 (Emerging) | Auth: No auth required
Conspiracy Theory
Social Media · Local stdio
Quality: 43/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Chaos Index if you need specialized Social Media tools running via a local process. Choose Conspiracy Theory if your workspace requires Social Media integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Chaos Index when:
You need dedicated capabilities in the Social Media domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
No explicit tool names declared in metadata yet. Check project README on main listing page.
Conspiracy Theory Tools (1)
conspiracy_theory_generate
Generate a conspiracy theory in one of three modes: 'connect' (link thing_one + thing_two), 'investigate' (explore an event), or 'complete' (extend an "I have noticed that..." prompt). Control depth (surface/deep/full_tinfoil) and confidence level.
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).
Chaos Index is categorized under Social Media and uses a local stdio subprocess. In contrast, Conspiracy Theory belongs to Social Media using local stdio subprocess. Select Chaos Index when you need capabilities focused on social media and Conspiracy Theory when you require tools for social media.