Remote MCP · Endpoint

Lower My Bill MCP server

No. Lower My Bill answered an MCP handshake 35 minutes ago.

UpLast checked 35 minutes ago

Server URL

https://goodturn-mcp.pages.dev/lowermybill/mcp

The last check completed an MCP handshake.

Registry name
io.github.GoodTurnStudio/lowermybill
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
210 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Call scripts to lower bills in the US and UK, low-cost plans you may qualify for, and when to call.
Listing
From the official MCP registry (active).
Recent checks of Lower My Bill
CheckedResultHandshake
35 minutes agoHandshake completed210 ms
9 days agoHandshake completed50 ms
10 days agoHandshake completed165 ms
11 days agoHandshake completed54 ms
12 days agoHandshake completed99 ms
14 days agoHandshake completed75 ms
14 days agoHandshake completed54 ms
15 days agoHandshake completed211 ms
17 days agoHandshake completed68 ms
19 days agoHandshake completed76 ms
21 days agoHandshake completed41 ms
24 days agoHandshake completed42 ms
26 days agoHandshake completed34 ms
28 days agoHandshake completed23 ms

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

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 Lower My Bill and makes no claim about it beyond what these checks measured.