{"id":"f038f58d-4383-469a-884f-7634f3ae55d2","slug":"mcp-conspiracy-theory","kind":"mcp","name":"mcp-conspiracy-theory","summary":"conspiracy-theory MCP — wraps StupidAPIs (keyless — no credential needed)","owner":"pipeworx-io","repoUrl":"https://github.com/pipeworx-io/mcp-conspiracy-theory","license":"MIT","licenseTier":"permissive","trust":"community","stars":0,"match":null,"fewStars":true,"format":"mcp","createdAt":"2026-04-15T19:58:55.000Z","addedAt":"2026-10-14T05:53:04.099Z","logoUrl":"https://avatars.githubusercontent.com/u/270792911?v=4","linkOnly":false,"collection":null,"skillPath":null,"categories":["cloud-infra","memory-knowledge"],"tags":["conspiracy-theory","pipeworx"],"runtime":"remote","local":false,"cloudCapable":false,"cloudCapability":"unknown","cloudReadyOnPlatform":false,"needsApiKey":false,"reviewed":false,"syncedAt":"2026-10-21T02:05:56.803Z","sample":false,"url":"https://conduits.dev/tools/mcp-conspiracy-theory","language":"TypeScript","transports":["http"],"install":{"remoteUrl":"https://gateway.pipeworx.io/conspiracy-theory/mcp"},"requirements":{"env":[],"upstreamMayCharge":false},"tools":null,"readme":"# mcp-conspiracy-theory\n\nconspiracy-theory MCP — wraps StupidAPIs (keyless — no credential needed)\n\nPart of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 1854+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.\n\n## Tools\n\n| Tool | Description |\n|------|-------------|\n| `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. |\n\n## Quick Start\n\nAdd to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):\n\n```json\n{\n  \"mcpServers\": {\n    \"conspiracy-theory\": {\n      \"url\": \"https://gateway.pipeworx.io/conspiracy-theory/mcp\"\n    }\n  }\n}\n```\n\n### What this endpoint actually serves\n\n`tools/list` at `https://gateway.pipeworx.io/conspiracy-theory/mcp` returns the tools in the table\nabove **plus the shared Pipeworx meta-tools** — `ask_pipeworx`,\n`discover_tools`, `search_within`, `remember`/`recall` and the rest of the\ngateway-wide set. So the tool count you see is larger than this table: a\nsingle-pack endpoint currently lists roughly 30 shared tools alongside the\npack's own. The connection's `initialize` response states its exact scope, and\nis the authoritative answer for a given day.\n\nThis is deliberate, not multiplexing by accident. The meta-tools are what let a\nscoped connection answer a question this pack does not cover — via\n`ask_pipeworx`, which routes across the whole catalog — without you adding a\nsecond MCP server. There is currently no way to mount a pack endpoint without\nthem; if the extra schemas cost you more context than the routing is worth,\nconnect to the full gateway once rather than to several pack endpoints.\n\nOr connect to the full Pipeworx gateway to get every pack's tools listed\ndirectly, instead of just this one's:\n\n```json\n{\n  \"mcpServers\": {\n    \"pipeworx\": {\n      \"url\": \"https://gateway.pipeworx.io/mcp\"\n    }\n  }\n}\n```\n\nBoth URLs reach the same gateway and the same 1854+ data sources. The\nonly difference is which pack's tools are listed **directly**; `ask_pipeworx`\nreaches all of them from either one.\n\n## No MCP client? Call it over HTTP\n\n```bash\ncurl -X POST https://gateway.pipeworx.io/v1/tools/conspiracy_theory_generate \\\n  -H 'Content-Type: application/json' \\\n  -d '{\"mode\":\"connect\",\"thing_one\":\"pharmaceutical companies\",\"thing_two\":\"social media algorithms\",\"depth\":\"deep\",\"confidence\":\"medium\"}'\n```\n\nNo account needed for the first calls. Inspect any tool: `GET https://gateway.pipeworx.io/v1/tools/conspiracy_theory_generate`. Find one: `POST https://gateway.pipeworx.io/v1/tools/search_packs` with `{\"query\":\"...\"}`.\n\n## Standalone (no gateway account)\n\nThis package also runs as a local stdio MCP server — no Pipeworx account, no\ngateway round-trip:\n\n```json\n{\n  \"mcpServers\": {\n    \"conspiracy-theory\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"@pipeworx/mcp-conspiracy-theory\"]\n    }\n  }\n}\n```\n\nOr run it directly to confirm it starts:\n\n```bash\nnpx -y @pipeworx/mcp-conspiracy-theory\n```\n\nIt speaks MCP over stdin/stdout and answers `initialize`/`tools/list`/`tools/call`\nfor **only** this pack's tools — none of the shared meta-tools the gateway\nconnection above adds. Same source, same tools, no ask_pipeworx routing.\n\n## Using with ask_pipeworx\n\nInstead of calling tools directly, you can ask questions in plain English —\nthis works on the pack endpoint above as well as on the full gateway:\n\n```\nask_pipeworx({ question: \"your question about Conspiracy Theory data\" })\n```\n\nThe gateway picks the right tool and fills the arguments automatically.\n\n## More\n\n- [Docs and guides](https://pipeworx.io/docs)\n- [pipeworx.io](https://pipeworx.io)\n\n## License\n\nMIT\n"}