Macrostrat
Server Details
Macrostrat MCP — geologic map / column / unit data for North America and beyond.
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
- 38.6% over 46 days
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- pipeworx-io/mcp-macrostrat
- GitHub Stars
- 0
- Server Listing
- mcp-macrostrat
TDQS
Scored across 34 tools
Several tool clusters overlap heavily: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research and validate_claim all answer factual questions via the same 5,961-tool router, and discover_tools vs suggest_questions both serve discovery. The extremely detailed descriptions do a lot of disambiguation work, but boundaries between variants (notably the beta, which is currently identical to the stable router) are inherently fuzzy. Distinct clusters like geology (find_columns/find_units/define_lithology), memory (remember/recall/forget), and subscriptions are cleanly separated.
Names are uniformly snake_case with clear domain prefixes (polymarket_*, pipeworx_*, ask_pipeworx_*) and no camelCase or mixed conventions. Verb-noun patterns dominate (find_columns, list_subscriptions, define_lithology, compare_entities), though a few are noun-only (entity_profile, polymarket_edges) and suffixes (_beta, _grounded) vary the base verb pattern. Overall predictable and readable.
34 tools exceeds the range where each tool clearly earns its place, and there is genuine redundancy: three ask_pipeworx variants (one of which is currently identical to the base), two discovery/onboarding tools, and multiple research/verification tools. As a multi-domain gateway some breadth is justified, but the surface is heavy for the apparent scope.
For the named domain (Macrostrat), coverage is thin — only define_lithology, find_columns and find_units, with no tools for fossil/paleo data, timescale, or measurements, so the geology lifecycle is clearly incomplete. Across the broader gateway the surface is fairly complete (memory CRUD, subscription lifecycle, feedback, research), but there is no direct tool to fetch a pipeworx:// record by citation URI.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
- 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."
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_spread2 fields changed- changed
Input schema / examplesPrevious value: -[ - { - "topic": "fed" - }, - { - "topic": "btc" - } -]New value: +[ + { + "topic": "fed" + }, + { + "topic": "btc" + }, + { + "topic": "bitcoin" + }, + { + "topic": "fed rate decision" + } +] - 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
Paleobiology Database (PBDB) MCP — the global fossil record. Keyless.
USGS MRData MCP — the Mineral Resources Data System (MRDS)
Related MCP Servers
- AlicenseBqualityDmaintenanceEnables Claude to query comprehensive geologic data from the Macrostrat API, including geologic units, columns, minerals, and timescales through natural language.87 npm8MIT
- AlicenseNot gradedqualityAmaintenanceSearch fossil occurrences, resolve taxon fossil ranges, plot diversity through deep time, and look up the geologic time scale via MCP.265 npm2Apache 2.0
- FlicenseNot gradedqualityDmaintenanceMCP server for querying the CONAPESCA historical fishing landings database (2001–2026) from Mexico's Pacific and Gulf coasts, providing tools to extract and analyze standardized landing records (avisos de arribo).-
- AlicenseBqualityDmaintenanceMCP server for searching research grants across NSF (US), ERC (EU), and KRF/NRF (Korea) via a unified interface. NIH excluded—covered by existing connectors.316 npmMIT
Glama MCP Gateway
Add one secure layer between your agents and this server.