Data, search and analytics
texas-rrc-wellbores
texas-rrc-wellbores was answering at the last check. Checked on 2026-10-05 (daily check).
Texas RRC oil & gas wellbores: API numbers, completion dates, depth, plug status
Agents use servers like this to search, query and report on data.
1 read-only1 change data0 high risk
https://mcp.tppflow.com/rrc
Follow (RSS): status changes, tool-list changes, new advisories and owner verification, in any feed reader.
Status
Newest check: answered with tools, from the daily check, 2026-10-05, 869 ms.
From one check a day over the last 4 days. Servers whose owner verified them are checked every 5 minutes. Sign-in and payment answers count as up.
Last 30 days
2026-09-062026-10-05
answered with toolssign-in or payment askednot answeringnot checked
Compare: the most reliable servers in Data, search and analytics, ranked by days answering.
Tools
2 tools: 1 read-only, 1 change data, 0 high risk (delete, pay, send or run code).
- read-only
- Only reads or looks things up. Safe for an agent to call on its own.
- changes data
- Creates, edits or sends something. Worth a person's approval the first time.
- high risk
- Can delete, pay, send on your behalf or run code. Hard or impossible to undo.
Connecting costs an agent about 497 tokens of tool definitions and a 869 ms handshake.
- changes data
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 25 rows or using of... - read-only
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 before search_texas_w...
Levels are automated estimates from each tool's public name, description and annotations, and can be wrong. Descriptions as the server publishes them.
Trust and supply chain
No owner has verified this server yet.
From the checks: No tool declares risk annotations.
No tool change since tracking began on 2026-10-02.
Badge
Live: status, days reachable, the tokens its tool list costs an agent. For a README:
[](https://7it.co.il/7maps/s/mcp.tppflow.com/rrc)
Other styles: add ?style=uptime (30-day uptime), ?style=stars (agents’ rating) or ?style=verified (owner mark) to the image address, or ?style=top (shows "top 10%" when the server ranks in the top tenth of its category by days answering; otherwise the standard badge).
Is this badge genuine? Anyone can check what a genuine badge for this server says right now: /7maps/verify/badge?server=mcp.tppflow.com%2Frrc (add the same &style= for another style).
Own this server? Verify that it is yours.
Status widget
A live status card for a status page, docs or a dashboard: current status, the 30-day strip, uptime and handshake time.
Script (renders where it is placed, in its own shadow DOM):
<script src="https://7it.co.il/7maps/widget/mcp.tppflow.com/rrc.js" async></script>
Or an iframe:
<iframe src="https://7it.co.il/7maps/widget/mcp.tppflow.com/rrc" title="7Maps status" width="360" height="176" style="border:0;max-width:100%" loading="lazy"></iframe>
The widget is drawn only from 7it.co.il. Is a status shown elsewhere genuine? Check it: /7maps/verify/badge?server=mcp.tppflow.com%2Frrc.
Add ?theme=light or ?theme=dark to either address (default: follows the visitor's setting). Refreshed every 5 minutes. Open the card · script.
For AI agents
Before connecting, an agent can ask 7Maps for this server's full condition, every tool's risk level and what changed since a person approved it: the road_conditions, watch and route tools on https://7it.co.il/7maps/mcp, paid per call in USDC via x402. About 7Maps.
7Maps by 7IT maps the MCP servers AI agents use, from public listings. Observations with a date, not a judgement. Methodology · How we collect, and opting out.