Skip to main content
Glama

Meteostat

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Server Details

Meteostat MCP — historical weather from 11k+ stations (no auth)

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

TDQS

A3.9/5.0

Scored across 34 tools

Disambiguation3/5

There are several overlapping clusters: ask_pipeworx / ask_pipeworx_beta / ask_pipeworx_grounded / deep_research all route questions to the same 5,961-tool catalog with near-identical response shapes, and the beta description explicitly says it currently matches the stable router exactly. The polymarket_* family (arbitrage, edges, edge_tracker, fill_risk, kalshi_spread) and entity_profile vs recent_changes vs compare_entities also require careful reading to pick correctly. Descriptions are detailed and help, but an agent must work hard to disambiguate.

Naming Consistency3/5

A recognizable verb_noun pattern dominates (find_stations, get_daily_history, resolve_entity, compare_entities, validate_claim, discover_tools), but it is mixed with bare verbs (remember, recall, forget, subscribe, unsubscribe), noun-prefixed tool families (polymarket_*, ask_pipeworx*), and noun-only names (entity_profile, recent_alerts, recent_changes). Grouping prefixes are helpful, so it remains readable despite the mixed conventions.

Tool Count3/5

34 tools is heavy and above the comfortable 3-15 band, and for a server named after a weather data provider the count is wildly disproportionate. As a multi-domain aggregator each tool does earn some place, but the surface is large enough that discovery and selection become burdensome.

Completeness4/5

Across its many domains the surface is broad: research/routing, entity resolution, company/drug profiles, comparison, memory (remember/recall/forget), subscriptions (subscribe/unsubscribe/list/recent_alerts), and prediction-market analytics are all covered. Weather coverage itself is thin (only find_stations, get_daily_history, get_monthly_normals — no current/hourly lookups), but the overall toolkit has few obvious dead ends.

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": "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."
    • Changedpolymarket_kalshi_spread1 field changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "topic": "fed"
-  },
-  {
-    "topic": "btc"
-  }
-]New value: +[
+  {
+    "topic": "fed"
+  },
+  {
+    "topic": "btc"
+  },
+  {
+    "topic": "bitcoin"
+  },
+  {
+    "topic": "fed rate decision"
+  }
+]
  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_spread1 field changed
      • 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

  • weather-mcp

    idrabenia
    A
    license
    Not graded
    quality
    C
    maintenance
    MCP server providing weather data via the Open-Meteo API, including geocoding, current conditions, daily and hourly forecasts, and city lookup. No API key required, with support for multiple units and transport types.
    1
    MIT

  • Weather MCP Server

    newcoast27-hub
    F
    license
    Not graded
    quality
    C
    maintenance
    An MCP server providing worldwide weather via the free Open-Meteo APIs (no API key needed). Runs fully self-contained in Docker as a streamable-HTTP MCP service.
    -
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