Skip to main content
Glama

Server Details

GeoNet New Zealand 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
43.4% over 38 days
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-geonet-nz
GitHub Stars
0

TDQS

A3.8/5.0

Scored across 34 tools

Disambiguation3/5

The large majority of tools target distinct operations (quake detail vs quake list vs volcano alerts; remember/recall/forget; subscribe/unsubscribe/list_subscriptions), but the ask_pipeworx family (ask_pipeworx, ask_pipeworx_beta — currently identical, ask_pipeworx_grounded, deep_research) present four overlapping routing entry points whose boundaries are described at great length rather than being self-evident. The five polymarket_* tools plus entity_profile/recent_changes/compare_entities also overlap enough that misselection is plausible, though descriptions do provide guidance.

Naming Consistency3/5

All names are snake_case, which is good, but the conventions are mixed: verb_noun (get_quake, list_subscriptions, resolve_entity, validate_claim, generate_llms_txt), bare verbs (forget, remember, recall, subscribe, unsubscribe), and noun phrases with no verb (entity_profile, bet_research, deep_research, polymarket_edges, pipeworx_trending). It remains readable but does not follow a single predictable pattern.

Tool Count2/5

34 tools is heavy for any single MCP surface, exceeding the 25+ threshold that signals overload. Several slots are redundant or experimental (ask_pipeworx_beta explicitly duplicates ask_pipeworx today; five polymarket_* tools), so the count is not just large but partly padded with overlapping capability.

Completeness4/5

Interpreted as a broad data-gateway plus NZ GeoNet surface, coverage is wide: discovery (discover_tools, suggest_questions), querying (ask_pipeworx, deep_research), entity resolution, comparison, subscriptions with delivery, memory, and feedback are all present, and the GeoNet side covers quake list/detail and volcano alert levels. Minor gaps exist (e.g. no memory update besides delete, no subscription edit), but agents can work around them.

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

  • A
    license
    A
    quality
    D
    maintenance
    A unified MCP server that queries 20 seismic agencies in parallel, reconciles cross-agency earthquake reports, and surfaces discrepancies for AI agents.
    7
    1
    MIT
  • A
    license
    A
    quality
    C
    maintenance
    MCP server for Icelandic weather, forecasts, warnings, and earthquakes. Data comes from the Icelandic Meteorological Office.
    6
    30 npm
    5
    MIT
  • A
    license
    A
    quality
    D
    maintenance
    MCP server that surfaces cited official Japanese government data on Nankai Trough earthquake hazards, building safety standards, and routes users to official hazard maps without inventing numbers.
    6
    45 npm
    MIT
Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.