Skip to main content
Glama

Legiscan

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Server Details

LegiScan MCP — wraps the LegiScan API (api.legiscan.com)

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
28.7% over 43 days
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-legiscan
GitHub Stars
0
Server Listing
legiscan

TDQS

A4.1/5.0

Scored across 34 tools

Disambiguation3/5

Most tools target distinct tasks, but there is real overlap in the query family: ask_pipeworx, ask_pipeworx_beta (explicitly identical to the stable router right now), ask_pipeworx_grounded, and deep_research all 'ask a cross-source question.' The six polymarket_* tools plus bet_research also share a domain and rely heavily on verbose prose to draw boundaries. Descriptions do most of the disambiguating work, keeping it from being genuinely confusing.

Naming Consistency4/5

Names are uniformly snake_case with consistent prefixes (ask_pipeworx*, polymarket_*, pipeworx_*, recent_*), which makes them predictable to scan. The only deviation is that some entries are verb_noun (search_bills, compare_entities) while others are noun-only (entity_profile, list_sessions placeholder style), but nothing mixes camelCase or casing conventions.

Tool Count3/5

34 tools is on the heavy side and exceeds the comfortable 3-15 range, but the server spans many independent domains (finance, drugs, prediction markets, memory, subscriptions), so breadth partly justifies it. A clear deduction for redundancy: ask_pipeworx_beta currently duplicates ask_pipeworx exactly, and the polymarket family is large for one niche.

Completeness4/5

The surface covers discovery, querying (raw, grounded, deep), entity resolution, comparison, memory (remember/recall/forget), subscriptions (subscribe/unsubscribe/list_subscriptions), feedback, and monitoring, which is a coherent lifecycle for a data gateway. Gaps are minor and partly out of scope: despite the 'Legiscan' name, the legislative component is thin (search_bills/get_bill/list_sessions with no roll-call, sponsor, or voting tools).

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."
  3. 1 tool update
    • Changedentity_profile3 fields changed
      • changedInput schema / properties / type / description
        Previous value: -"Entity type. Only \"company\" supported today; person/place coming soon."New value: +"\"company\" or \"ticker\" — both are accepted and behave identically; `value` can be a ticker, CIK, or company name either way. person/place coming soon."
      • changedInput schema / properties / type / enum
        Previous value: -[
-  "company"
-]New value: +[
+  "company",
+  "ticker"
+]
      • changedInput schema / properties / value / description
        Previous value: -"Ticker (e.g., \"AAPL\") or zero-padded CIK (e.g., \"0000320193\"). Names not supported — use resolve_entity first if you only have a name."New value: +"Ticker (e.g., \"AAPL\"), zero-padded CIK (e.g., \"0000320193\"), or company name (e.g., \"Moderna\") — names resolve via SEC EDGAR company-name match."

Related MCP Connectors

Related MCP Servers

  • LegiScan MCP Server

    sh-patterson
    A
    license
    A
    quality
    B
    maintenance
    Provides access to legislative data from all 50 US states through the LegiScan API, enabling comprehensive search and retrieval of bills, votes, legislators, and legislative session information.
    10
    32 npm
    11
    MIT

  • congressgov-mcp-server

    cyanheads
    A
    license
    Not graded
    quality
    A
    maintenance
    Enables access to U.S. congressional data including bills, laws, members, committees, votes, nominations, CRS reports, and the Congressional Record through MCP, with stdio and Streamable HTTP support.
    308 npm
    1
    Apache 2.0

  • va-lis-mcp

    JonnyWaffles
    A
    license
    A
    quality
    A
    maintenance
    Enables MCP clients to read-only access the Virginia General Assembly's sessions, bills, summaries, full text, history, votes, members, committees, and meetings via the LIS REST API.
    22
    MIT
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