Skip to main content
Glama

Inaturalist

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Server Details

iNaturalist MCP — citizen-science species observations (free, no auth for read-only)

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

TDQS

A3.8/5.0

Scored across 34 tools

Disambiguation3/5

The three ask_pipeworx variants overlap heavily — the description of ask_pipeworx_beta admits it 'currently matches ask_pipeworx exactly' — and deep_research/discover_tools/suggest_questions all answer 'what can I ask / find me tools'. The polymarket_* family (edges, arbitrage, fill_risk, edge_tracker, kalshi_spread) and the entity tools (resolve_entity, entity_profile, compare_entities, recent_changes, validate_claim) are distinguishable but only after reading very long descriptions. An agent must parse a lot of prose to avoid misselection.

Naming Consistency4/5

Nearly everything is snake_case and most follow a verb_noun shape (resolve_entity, compare_entities, search_taxa, validate_claim, discover_tools). Minor deviations exist — entity_profile, top_species, and ai_visibility_check are noun-first — but the convention is readable and predictable. No camelCase/snake_case mixing.

Tool Count2/5

34 tools is well past the 15-tool comfort zone, and only three of them (search_observations, search_taxa, top_species) relate to the server's stated iNaturalist domain. The rest is a general data-gateway surface (meta-routers, memory, subscriptions, prediction-market analytics) bolted onto a wildlife-observation server, so most tools don't earn their place for this purpose.

Completeness3/5

For the iNaturalist domain the surface is thin: search and top-species ranking exist, but there is no fetch-observation-by-id, no taxon lookup by ID, no place/project/user endpoints, and no write operations — notable gaps that will force workarounds. The generic gateway side is broad, but that coverage doesn't serve the named server's purpose.

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

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