Skip to main content
Glama
Wickemu

well-data-mcp

by Wickemu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to well-data-mcp

No user-submitted related servers found.

    Related Servers

    • FracFocus MCP Server

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to search U.S. hydraulic fracturing disclosure records — well-level frac job details (operator, API number, location, dates, base fluid volumes) and the disclosed chemical additives per job — by state, county, operator, or API number, plus lookups of where a given chemical has been used by CAS number. Responses include source, license, and coverage-window metadata so callers can distinguish missing data from out-of-window disclosures.
      61 npm
      MIT

    • mcp-arcgis-tulsa

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables searching and querying City of Tulsa GIS open geospatial datasets (parcels, zoning, public works) via ArcGIS Feature Services through natural language or direct MCP tool calls.
      15 npm
      MIT

    • arcgis-stanislaus

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables searching and querying Stanislaus County GIS open geospatial datasets (parcels, addresses, zoning, public works) via ArcGIS Feature Services. Supports natural language access through Pipeworx gateway.
      18 npm
      MIT
    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

    A4.2/5.0

    Scored across 8 tools

    Disambiguation4/5

    Tools are largely distinct: search_wells, raw_query, and wells_near differ by query mode, while search_gem_projects and search_geothermal_datasets target separate datasets. The only mild ambiguity is between the three 'search_*' tools, but descriptions clearly specify data source and query style.

    Naming Consistency4/5

    Most tools follow a clear list_/search_/get_ verb_noun pattern, making the set predictable. raw_query and wells_near break that pattern, but they are still readable and not confusing.

    Tool Count5/5

    8 tools is well-scoped for the domain: source discovery, operator lookup, normalized search, spatial proximity, raw SQL escape hatch, and specialized project/dataset searches. Each tool earns its place without redundancy.

    Completeness5/5

    The surface covers the full read-only workflow: discover sources, inspect operators, query wells by attributes or location, retrieve full records by API, and fall back to raw SQL when needed. The specialized GEM and OSTI searches add meaningful coverage beyond state well data.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources