Remote MCP · Endpoint

app.rowb.septic-log/maintenance MCP server

No. app.rowb.septic-log/maintenance answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://septic-log.rowb.app/mcp

The last check completed an MCP handshake.

Registry name
app.rowb.septic-log/maintenance
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
458 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Septic maintenance record: log inspections and pump-outs; next due date under EPA intervals. No AI.
Listing
From the official MCP registry (active).
Recent checks of app.rowb.septic-log/maintenance
CheckedResultHandshake
1 hour agoHandshake completed458 ms
2 days agoHandshake completed499 ms
4 days agoHandshake completed810 ms
6 days agoHandshake completed409 ms
8 days agoHandshake completed441 ms
10 days agoHandshake completed774 ms
12 days agoHandshake completed413 ms
14 days agoHandshake completed445 ms
15 days agoHandshake completed430 ms
16 days agoHandshake completed812 ms
18 days agoHandshake completed472 ms
20 days agoHandshake completed411 ms
22 days agoHandshake completed423 ms
24 days agoHandshake completed484 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 app.rowb.septic-log/maintenance and makes no claim about it beyond what these checks measured.