Skip to main content
Glama

Conspiracy Theory

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Server Details

conspiracy-theory MCP — wraps StupidAPIs (keyless — no credential needed)

Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
36.3% over 41 days
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-conspiracy-theory
GitHub Stars
0
Server Listing
conspiracy-theory

TDQS

A4/5.0

Scored across 32 tools

Disambiguation3/5

The descriptions invest heavily in distinguishing tools (e.g. 'PREFER OVER WEB SEARCH', 'use ask_pipeworx instead'), which mitigates much of the overlap. However real functional overlap remains: ask_pipeworx, ask_pipeworx_beta (which the description admits currently matches ask_pipeworx exactly), ask_pipeworx_grounded, and deep_research are four flavors of one router, and the six polymarket_* tools plus bet_research are hard to tell apart at a glance. An agent will frequently have to re-read long descriptions to pick correctly.

Naming Consistency4/5

Everything is consistently snake_case, and most tools follow a verb_noun pattern (resolve_entity, validate_claim, compare_entities, scan_dependency, generate_llms_txt). Minor deviations exist — ai_visibility_check is noun_verb, and the ask_pipeworx family relies on suffix variation (_beta, _grounded) rather than a distinct verb. Readable and predictable overall.

Tool Count3/5

At 32 tools this is on the heavy side for a single MCP surface, and the load is inflated by redundancy: a literal beta duplicate of ask_pipeworx and six closely-related Polymarket tools. Most tools do map to genuinely distinct data domains or workflows, so the count is defensible but not tight.

Completeness4/5

As a data-gateway surface it is broad and lifecycle-aware: meta/memory tools (remember/recall/forget), subscription management (subscribe/unsubscribe/list_subscriptions/recent_alerts), onboarding (suggest_questions, discover_tools), feedback, and rich domain lookups. Coverage gaps are minor (e.g. no explicit update/edit for memory, only overwrite via remember).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 2 tool updates
    • Changedbet_research2 fields changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "market": "will-bitcoin-reach-100k-in-july-2026"
-  },
-  {
-    "market": "https://polymarket.com/event/will-bitcoin-hit-150k-by-june-30-2026"
-  }
-]New value: +[
+  {
+    "market": "will-kristi-noem-win-the-2028-republican-presidential-nomination"
+  },
+  {
+    "market": "https://polymarket.com/event/will-kristi-noem-win-the-2028-republican-presidential-nomination"
+  }
+]
      • changedInput schema / properties / market / description
        Previous value: -"Polymarket slug (\"will-bitcoin-hit-150k-by-june-30-2026\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k by June 30?\")"New value: +"Polymarket slug (\"will-kristi-noem-win-the-2028-republican-presidential-nomination\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."
    • Changedpolymarket_kalshi_spread2 fields changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "topic": "fed"
-  },
-  {
-    "topic": "btc"
-  }
-]New value: +[
+  {
+    "topic": "fed"
+  },
+  {
+    "topic": "btc"
+  },
+  {
+    "topic": "bitcoin"
+  },
+  {
+    "topic": "fed rate decision"
+  }
+]
      • changedInput schema / properties / topic / description
        Previous value: -"Pre-mapped: fed | btc | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president"New value: +"Subject to compare. Canonical keys: fed | btc | eth | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president — but aliases and keywords resolve too (\"bitcoin\", \"fed rate decision\", \"ethereum\", \"inflation\", \"s&p 500\", \"us recession\", \"next pope\", \"2028 election\"). Check resolution.topic_matched_by in the response: \"exact\"/\"alias\" is a curated pairing, \"phrase\"/\"token\" is a keyword guess."

Related MCP Connectors

Related MCP Servers

Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources