Data Batonrouge
Server Details
Baton Rouge Open Data (data.brla.gov) Socrata 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.7% over 42 days
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- pipeworx-io/mcp-data-batonrouge
- GitHub Stars
- 0
- Server Listing
- mcp-data-batonrouge
TDQS
Scored across 34 tools
The router/meta cluster — ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, discover_tools, suggest_questions — overlaps heavily; beta is explicitly identical to the stable router today, and several tools all promise to 'route a question to the right source.' Detailed descriptions help, but the boundaries are genuinely blurry and misselection is likely.
All names are snake_case, but the convention is not a uniform verb_noun pattern: some are bare nouns (datasets, metadata, query), some are bare verbs (remember, recall, forget, subscribe), and some are domain-prefixed (polymarket_*, pipeworx_*). Readable but not predictable.
34 tools is heavy for the apparent scope, and several are overlapping router variants rather than distinct capabilities. The set feels like multiple bundled suites (Baton Rouge open data, Polymarket, Pipeworx meta, AI-visibility) stacked into one server rather than a tightly scoped toolset.
Coverage is broad and mostly closed-loop: memory has remember/recall/forget, subscriptions have subscribe/list/unsubscribe/recent_alerts, Polymarket has scan/tracker/fill-risk/spread/bet tools, and Baton Rouge open data has datasets/metadata/query. Minor gaps exist (e.g. no explicit update for stored memory), but agents can work around them.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
- Changed
bet_research2 fields changed- changed
Input schema / examplesPrevious 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" + } +] - changed
Input schema / properties / market / descriptionPrevious 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 tool updates
- Changed
bet_research1 field changed- changed
Input schema / properties / market / descriptionPrevious 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."
- Changed
polymarket_kalshi_spread2 fields changed- changed
Input schema / examplesPrevious value: -[ - { - "topic": "fed" - }, - { - "topic": "btc" - } -]New value: +[ + { + "topic": "fed" + }, + { + "topic": "btc" + }, + { + "topic": "bitcoin" + }, + { + "topic": "fed rate decision" + } +] - changed
Input schema / properties / topic / descriptionPrevious 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."
1 tool update
- Changed
bet_research1 field changed- changed
Input schema / examplesPrevious 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" + } +]
Related MCP Connectors
Norfolk Open Data (data.norfolk.gov) Socrata MCP.
Mesa Open Data (citydata.mesaaz.gov) Socrata MCP.
Orlando Open Data (data.cityoforlando.net) Socrata MCP.
Fulton County Open Data (sharefulton.fultoncountyga.gov) Socrata MCP.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceDataCambridge MCP — Cambridge open data (data.cambridgema.gov, Socrata SODA API).142 npmMIT
- AlicenseNot gradedqualityBmaintenanceMCP server for accessing Kansas City, MO open data through the Socrata SODA API. Enables querying and retrieving public datasets from data.kcmo.org.135 npmMIT
- AlicenseNot gradedqualityBmaintenanceMCP server for accessing data.ny.gov datasets via the Socrata Open Data API, enabling search, query, metadata retrieval, and column value exploration.147 npm1MIT
- AlicenseNot gradedqualityBmaintenanceMCP server providing access to Montgomery County, MD open data through the Socrata SODA API, enabling querying and analysis of public datasets via natural language.123 npmMIT
Glama MCP Gateway
Add one secure layer between your agents and this server.