Remote MCP · Endpoint

com.tppflow/texas-rrc-wellbores MCP server

No. com.tppflow/texas-rrc-wellbores answered an MCP handshake 8 hours ago.

UpLast checked 8 hours ago

Server URL

https://mcp.tppflow.com/rrc

The last check completed an MCP handshake.

Registry name
com.tppflow/texas-rrc-wellbores
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
342 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Texas RRC oil & gas wellbores: API numbers, completion dates, depth, plug status
Listing
From the official MCP registry (active).
Recent checks of com.tppflow/texas-rrc-wellbores
CheckedResultHandshake
8 hours agoHandshake completed342 ms
2 days agoHandshake completed320 ms
4 days agoHandshake completed328 ms
6 days agoHandshake completed141 ms
8 days agoHandshake completed346 ms
10 days agoHandshake completed136 ms
12 days agoHandshake completed367 ms
13 days agoHandshake completed306 ms
14 days agoHandshake completed363 ms
16 days agoHandshake completed373 ms
18 days agoHandshake completed313 ms
20 days agoHandshake completed350 ms
21 days agoHandshake completed308 ms
23 days agoHandshake completed359 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 14 responding of 14.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with com.tppflow/texas-rrc-wellbores and makes no claim about it beyond what these checks measured.