Texas RRC oil & gas wellbores: API numbers, completion dates, depth, plug status
Connect Remote server
claude mcp add --transport http texas-rrc-wellbores https://mcp.tppflow.com/rrc --header "Authorization: Bearer <YOUR_API_KEY>"{
"mcpServers": {
"texas-rrc-wellbores": {
"url": "https://mcp.tppflow.com/rrc",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}{
"servers": {
"texas-rrc-wellbores": {
"type": "http",
"url": "https://mcp.tppflow.com/rrc",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}Settings > Connectors > Add custom connector
URL: https://mcp.tppflow.com/rrcReplace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools 2 found in our last check
describe_texas_wellboresFree, 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 bef…
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. 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 2…
Headers
| Name | Description |
|---|---|
AuthorizationOptional, secret | Bearer <api_key>. Optional: describe_texas_wellbores is free and unlimited, and search_texas_wellbores returns 25 real rows per call without a key (20 queries/day). A key removes the caps and enables pagination and bulk search. |
Details
| Endpoint | https://mcp.tppflow.com/rrc (Streamable HTTP) |
| First published | 28 Sep 2026 |
| Last updated | 28 Sep 2026 |
| Registry name | com.tppflow/texas-rrc-wellbores |
More search and web servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.