Texas Rrc Wellbores

com.tppflowPublished by tppflow.comOfficial publisherv1.0.0Updated Oct 28, 2026

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

The publisher's own server: Warn Act Layoffs

VerifiedStreamable HTTPWeb executableLocation & LifestyleData & Analytics

Overview

AI-generated overview

Remote MCP server for searching Texas Railroad Commission oil and gas wellbore identities by district, county, API number, plug status and depth.

What you can do
  • Describe the wellbore dataset: available fields, row count, freshness, pricing and which source parts are not yet parsed
  • Search wellbore identities by district, county, API number, plugged status, orphan-well hold, completion date range or minimum depth
  • Return decoded rows from the RRC mainframe corpus, with a free tier of up to 25 rows per call
When to use it
Useful when you need Texas oil and gas well records — locating wells by API number or county, checking plug or orphan status, or filtering by completion date and depth — and want the assistant to query them directly.
Requirements
Remote streamable HTTP endpoint at mcp.tppflow.com; no local runtime. No key needed for the free tier (25 rows per call, 20 queries a day); an API key sent as an Authorization bearer header removes the caps.
Before you install
An API key is passed in the Authorization header; larger result sets or off-schedule queries appear to require a paid key, so check pricing before use. The describe tool reports that parts of the source are not yet parsed, so results may be incomplete.

Installation

In SourceWeft

  1. Open Texas Rrc Wellbores in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.tppflow%2Ftexas-rrc-wellbores/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "texas-rrc-wellbores": {
      "type": "http",
      "url": "https://mcp.tppflow.com/rrc"
    }
  }
}

Tools

2

describe_texas_wellbores

Describe the Texas RRC wellbore dataset

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.

Takes no parameters.

search_texas_wellbores

Search Texas RRC wellbores

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.

Parameterslimitcountyoffsetpluggeddistrictmin_depthapi_numbercompleted_sincecompleted_beforeorphan_well_hold

Version history

1
  1. v1.0.0LatestSep 28, 2026

Score

72% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Tppflow integrations