Skip to main content
Glama

Server Details

openSenseMap MCP — citizen-science environmental sensor network (opensensemap.org)

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
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-opensensemap
GitHub Stars
0
Server Listing
mcp-opensensemap

TDQS

A3.9/5.0

Scored across 34 tools

Disambiguation3/5

The three ask_pipeworx variants (stable, beta, grounded) and deep_research have nearly identical routing behavior and overlapping use cases, which the verbose descriptions attempt to differentiate but cannot fully disambiguate. Polymarket tools (edges, arbitrage, fill_risk, edge_tracker) also overlap in purpose, though the descriptions provide clear guidance on when to use each. The openSenseMap tools are distinct from each other, but the set as a whole contains several pairs that an agent could easily confuse.

Naming Consistency3/5

All names use snake_case, but verb styles are mixed: some are verb-led (ask_, discover_, validate_, resolve_, compare_, generate_) while others are noun-led (entity_profile, deep_research, recent_changes, ai_visibility_check). Prefixes are inconsistently applied (opensensemap_*, pipeworx_*, polymarket_*), with many tools lacking any domain prefix. The naming is readable but not predictable.

Tool Count2/5

34 tools is well above the typical well-scoped range of 3-15, and several tools (e.g., three ask_pipeworx variants, two AI visibility tools) appear redundant. The breadth spans unrelated domains (memory, subscriptions, Polymarket, openSenseMap, AI marketing) within a single server, suggesting scope creep rather than a cohesive surface.

Completeness3/5

For the openSenseMap domain specifically, the three provided tools (nearby, box, area_average) cover basic discovery and current readings, but lack historical time-series retrieval, global station listing, or filtering by sensor type across the network. If the server is intended as a Pipeworx gateway, many data domains have only partial coverage, leaving notable gaps for agents to work around.

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": "will-bitcoin-reach-100k-in-july-2026"
        -  },
        -  {
        -    "market": "https://polymarket.com/event/will-bitcoin-hit-150k-by-june-30-2026"
        -  }
        -]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 (\"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 (\"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_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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.