Remote MCP · Endpoint

Ampworth MCP server

No. Ampworth answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://ampworth.com/mcp

The last check completed an MCP handshake.

Registry name
com.ampworth/ampworth
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
153 ms
Tools exposed
15 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
UK solar PV and heat pump calculators, with guides, on one server. Follows the MCS methods. No key.
Listing
From the official MCP registry (active).
Recent checks of Ampworth
CheckedResultHandshake
1 hour agoHandshake completed153 ms
8 days agoHandshake completed201 ms
9 days agoHandshake completed160 ms
11 days agoHandshake completed286 ms
12 days agoHandshake completed182 ms
13 days agoHandshake completed161 ms
14 days agoHandshake completed160 ms
14 days agoHandshake completed166 ms
16 days agoHandshake completed189 ms
19 days agoHandshake completed174 ms
21 days agoHandshake completed248 ms
24 days agoHandshake completed171 ms
26 days agoHandshake completed158 ms
28 days agoHandshake completed256 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 Ampworth and makes no claim about it beyond what these checks measured.