Skip to main content
Glama

Politics Feeds

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Server Details

Politics Feeds MCP.

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.2% over 46 days
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-politics-feeds
GitHub Stars
0
Server Listing
Politics Feeds

TDQS

A4/5.0

Scored across 34 tools

Disambiguation3/5

Most tools have distinguishable purposes, but there are clear clusters of near-duplicates: ask_pipeworx vs ask_pipeworx_beta (explicitly identical today) vs ask_pipeworx_grounded vs deep_research all answer questions, and polymarket_arbitrage vs polymarket_edges vs bet_research vs polymarket_edge_tracker overlap heavily in 'find mispricings/edges'. Discovery tools (discover_tools, suggest_questions, pipeworx_trending) also blur. Descriptions do a lot of heavy lifting with explicit 'prefer X over Y' guidance, which keeps this from being worse.

Naming Consistency4/5

Names are uniformly snake_case and many follow a verb_noun pattern (list_feeds, read_feed, fetch_feed, subscribe, resolve_entity, validate_claim). A minority are noun phrases or noun-only (ai_visibility_check, entity_profile, polymarket_edges, recent_alerts, recent_changes, suggest_questions), a minor deviation rather than a convention break. No case mixing or chaotic styles.

Tool Count2/5

34 tools is well into 'heavy' territory and the surface is redundant: four question-answering routers (one explicitly a duplicate of the stable one), four-plus Polymarket edge tools, and three discovery/help tools. While the underlying gateway spans 1552 sources, several tools do not earn a distinct place. For a server labeled 'Politics Feeds' this is a large scope mismatch.

Completeness4/5

Coverage is genuinely broad: entity resolution, entity profiles, comparisons, change feeds, feed listing/reading/fetching, subscriptions with cancel, memory, grounded research, claim validation, and prediction-market analysis. Minor gaps exist (no feed/source write or management operations, no general web-search path, only subscribe/unsubscribe for subscription lifecycle). No obvious dead ends for the stated gateway purpose.

Tool Schema Changelog

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

  1. 1 tool update
    • Changedbet_research2 fields changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "market": "when-will-bitcoin-hit-150k"
-  },
-  {
-    "market": "https://polymarket.com/event/when-will-bitcoin-hit-150k"
-  }
-]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 (\"when-will-bitcoin-hit-150k\"), 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."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."
  2. 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": "when-will-bitcoin-hit-150k"
+  },
+  {
+    "market": "https://polymarket.com/event/when-will-bitcoin-hit-150k"
+  }
+]
      • 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 (\"when-will-bitcoin-hit-150k\"), 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