Skip to content

com.tppflow/texas-rrc-wellbores

by tppflow.com · remote · no sign-in to list tools · v1.0.0 · published by com.tppflow

Texas RRC oil & gas wellbores: API numbers, completion dates, depth, plug status

Read only
CompareRegistry entry

2 tools: 2 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http texas-rrc-wellbores https://mcp.tppflow.com/rrc

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

2 tools

Only reads 2Claude Code: allow
  • describe_texas_wellboresFree, no API key required.No findings

    Why it is in this group

    • The name "describe_texas_wellbores" says "describe": a word for reading.
    Description, as the server wrote it
    Free, no API key required. Describes the Texas Railroad Commission wellbore identity dataset decoded from RRC's EBCDIC mainframe corpus: the exact fields available, row count, freshness, pricing, and which parts of the source are NOT yet parsed. Returns no records. Call this before search_texas_wellbores.
  • search_texas_wellboresSearch Texas oil and gas wellbore identities by district, county, API number, plugged status, orphan-well hold, completion date range or minimum depth.No findings

    Why it is in this group

    • The name "search_texas_wellbores" says "search": a word for reading.
    Description, as the server wrote it
    Search Texas oil and gas wellbore identities by district, county, API number, plugged status, orphan-well hold, completion date range or minimum depth. FREE tier: up to 25 real decoded rows per call with no API key, so you can judge the data before paying. Asking for more than 25 rows or using offset requires a key and otherwise returns a payment_required error carrying a checkout URL.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http texas-rrc-wellbores https://mcp.tppflow.com/rrc

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__texas-rrc-wellbores__describe_texas_wellbores",
      "mcp__texas-rrc-wellbores__search_texas_wellbores"
    ],
    "ask": [],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as texas-rrc-wellbores. Review it before you use it.