com.tppflow/texas-rrc-wellbores
REMOTE · MCP.TPPFLOW.COM · SCANNED OCT 1
Texas RRC oil & gas wellbores: API numbers, completion dates, depth, plug status
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 366 tokens (~183/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the com.tppflow/texas-rrc-wellbores MCP server?
com.tppflow/texas-rrc-wellbores is a hosted endpoint at https://mcp.tppflow.com/rrc, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.tppflow.com
claude mcp add --transport http com-tppflow-texas-rrc-wellbores 'https://mcp.tppflow.com/rrc'
{
"mcpServers": {
"com-tppflow-texas-rrc-wellbores": {
"url": "https://mcp.tppflow.com/rrc"
}
}
} {
"servers": {
"com-tppflow-texas-rrc-wellbores": {
"type": "http",
"url": "https://mcp.tppflow.com/rrc"
}
}
} [mcp_servers.com-tppflow-texas-rrc-wellbores] url = "https://mcp.tppflow.com/rrc"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-tppflow-texas-rrc-wellbores": {
"type": "remote",
"url": "https://mcp.tppflow.com/rrc",
"enabled": true
}
}
} openclaw mcp add com-tppflow-texas-rrc-wellbores --url 'https://mcp.tppflow.com/rrc' --transport streamable-http
mcp_servers:
com-tppflow-texas-rrc-wellbores:
url: "https://mcp.tppflow.com/rrc" {
"McpServers": {
"com-tppflow-texas-rrc-wellbores": {
"Transport": "http",
"Url": "https://mcp.tppflow.com/rrc"
}
}
} assistant mcp add com-tppflow-texas-rrc-wellbores -t streamable-http -u 'https://mcp.tppflow.com/rrc'
{
"mcpServers": {
"com-tppflow-texas-rrc-wellbores": {
"type": "http",
"url": "https://mcp.tppflow.com/rrc"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 1 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- 28 Sept 26 56
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 1 Oct 2026 · Probed https://mcp.tppflow.com/rrc
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=tppflow.com | CN=WE1,O=Google Trust Services,C=US | 19 Aug 2026 | 17 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | f8fdf7e559023c8e0e30f99a84b26af0 |
| SANs: tppflow.com, *.tppflow.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.tppflow.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| tppflow.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.tppflow.com/rrc | Verified | 200 | |
| http (plaintext) | http://mcp.tppflow.com/rrc | Inconclusive | 406 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
describe_texas_wellbores Describe the Texas RRC wellbore dataset ~81
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_texas_wellbores Search Texas RRC wellbores ~155
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.
| Name | Type | Req | Description |
|---|---|---|---|
| api_number | – | – | – |
| completed_before | – | – | – |
| completed_since | – | – | – |
| county | – | – | – |
| district | – | – | – |
| limit | – | – | – |
| min_depth | – | – | – |
| offset | integer | – | – |
| orphan_well_hold | – | – | – |
| plugged | – | – | – |
No output schema declared.
No examples provided.
What is the com.tppflow/texas-rrc-wellbores MCP server?
com.tppflow/texas-rrc-wellbores is an MCP server listed in the public MCP registry as com.tppflow/texas-rrc-wellbores. Texas RRC oil & gas wellbores: API numbers, completion dates, depth, plug status. This page covers its hosted endpoint (https://mcp.tppflow.com/rrc).
Is the com.tppflow/texas-rrc-wellbores MCP server safe to use?
com.tppflow/texas-rrc-wellbores scores 58 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.tppflow/texas-rrc-wellbores MCP server expose?
com.tppflow/texas-rrc-wellbores exposes 2 tools: describe_texas_wellbores, search_texas_wellbores. Their descriptions and schemas cost roughly 236 tokens of context every time the server is loaded.
Does the com.tppflow/texas-rrc-wellbores MCP server require authentication?
No. We connected to com.tppflow/texas-rrc-wellbores without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the com.tppflow/texas-rrc-wellbores MCP server still maintained?
com.tppflow/texas-rrc-wellbores is still listed as active in the MCP registry. We last reached this channel on 1 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.