Stat Gl
Server Details
Statistics Greenland (Grønlands Statistik) PxWeb 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.4% over 43 days
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- pipeworx-io/mcp-stat-gl
- GitHub Stars
- 0
- Server Listing
- mcp-stat-gl
TDQS
Scored across 34 tools
Most tools have clearly distinct purposes, but several cluster in overlapping 'ask a question' territory: ask_pipeworx, ask_pipeworx_grounded, deep_research, and especially ask_pipeworx_beta (which the description admits is currently identical to ask_pipeworx). The Polymarket opportunity scanners (edges, arbitrage, kalshi_spread) also overlap, so an agent must rely heavily on the long descriptions to choose correctly.
Names are uniformly lowercase snake_case with no camelCase or style clashes, which is the important consistency. The only wrinkle is a verb/noun mix (remember/recall/forget/subscribe vs. subjects/table_meta/entity_profile/recent_changes), but the pattern is still readable and predictable.
At 34 tools this is on the heavy side for a single MCP surface. The breadth is partly justified by the gateway nature and vast underlying catalog, but a near-duplicate beta router and multiple overlapping meta-research tools pad the count without adding new capability.
Coverage is broad and mostly closed-loop: full CRUD for memory (remember/recall/forget) and subscriptions (subscribe/unsubscribe/list_subscriptions), plus discovery, entity resolution, comparison, and research tools. The named 'Stat Gl' domain is thin (only subjects/table_meta/query_table), but the overall data-fetching surface has few obvious dead ends.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
2 tool updates
- 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."
- Changed
polymarket_kalshi_spread1 field changed- changed
Input schema / examplesPrevious value: -[ - { - "topic": "fed" - }, - { - "topic": "btc" - } -]New value: +[ + { + "topic": "fed" + }, + { + "topic": "btc" + }, + { + "topic": "bitcoin" + }, + { + "topic": "fed rate decision" + } +]
2 tool updates
- Changed
bet_research2 fields 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" + } +] - 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_spread1 field changed- 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."
Related MCP Connectors
Statistics Faroe Islands (Hagstova Føroya) PxWeb MCP.
Statistics Denmark (Danmarks Statistik / Statbank) MCP.
Statistics and Research Åland (ÅSUB) PxWeb MCP.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceMCP server for querying statistical data from Hagstova Føroya (Statistics Faroe Islands) via PxWeb.9 npmMIT
- AlicenseAqualityDmaintenanceMCP server for accessing statistical data via the PxWeb API v2.615 npm1MIT
- AlicenseAqualityDmaintenanceMCP server for official statistics from Statistics Finland (Tilastokeskus) — the StatFin database, exposed through the PxWeb API. Search 3000+ tables, inspect their dimensions, and pull data as JSON-stat2.424 npmMIT
- AlicenseNot gradedqualityBmaintenanceMCP server for Statistics Norway (SSB) PxWebApi, enabling table metadata queries via a single tool.180 npmMIT
Glama MCP Gateway
Add one secure layer between your agents and this server.