Skip to main content
Glama
blake365

Macrostrat MCP Server

by blake365
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Macrostrat MCP Server

No user-submitted related servers found.

    Related Servers

    • Claude MCP Server for USGS

      blake365
      A
      license
      A
      quality
      C
      maintenance
      Provides access to the USGS Quakes API within Claude Desktop, enabling users to retrieve earthquake data and details through natural language queries.
      3
      2 npm
      1
      MIT

    • Qlik MCP Server

      jwaxman19
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables Claude to interact with Qlik Cloud applications and extract data from visualizations through the Qlik Cloud API.
      11
      MIT

    • earthscope-fdsn

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables querying seismic station metadata, regional earthquake catalogs, and federated waveform data availability across FDSN web services, letting users locate seismometers, retrieve local seismicity, and identify data holdings through direct tool calls or natural language.
      213 npm
      MIT

    • geotab-mcp

      deanjbrown
      F
      license
      Not graded
      quality
      C
      maintenance
      Exposes the MyGeotab API as AI-callable tools, letting Claude query fleet data, device status, trips, tachograph files, fuel, diagnostics, faults, and driver information across multiple customer databases through natural language.
      -
    Deploy Server
    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

    TDQS

    B3/5.0

    Scored across 8 tools

    Disambiguation3/5

    Most tools have distinct purposes, but 'find-columns' and 'find-units' overlap significantly in their descriptions (both for geological analysis of locations), which could cause confusion. Other tools like 'defs' and 'defs-autocomplete' are clearly related but serve different functions, while tools like 'lat-lng-to-tile' and 'map-tiles' are distinct but interdependent.

    Naming Consistency2/5

    The naming is inconsistent with mixed conventions: some use snake_case ('lat-lng-to-tile'), some use kebab-case ('defs-autocomplete'), and others use plain words ('defs', 'timescale'). There is no predictable verb_noun pattern, making it harder for agents to infer tool purposes from names alone.

    Tool Count4/5

    With 8 tools, the count is reasonable for a geological data server, covering definitions, location-based queries, mapping, and mineral/time information. It's slightly under the ideal 10-15 range for comprehensive coverage but not overly sparse, fitting the domain scope adequately.

    Completeness3/5

    The tool set covers core geological data access (definitions, units, columns, minerals, timescales) and mapping functions, but there are notable gaps such as missing update/delete operations for data manipulation and limited query capabilities (e.g., no advanced filtering or aggregation tools). It supports basic retrieval but lacks full lifecycle coverage.

    Maintenance

    ActivitySlowing
    ResponsivenessUnresponsive

    Resources