Remote MCP · Endpoint

pound.one MCP server

No. pound.one answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://pound.one/mcp

The last check completed an MCP handshake.

Registry name
one.pound/pound-one
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
190 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
UK inflation, take-home pay and public spending calculators with sources and shareable results.
Listing
From the official MCP registry (active).
Recent checks of pound.one
CheckedResultHandshake
1 hour agoHandshake completed190 ms
2 days agoHandshake completed153 ms
5 days agoHandshake completed376 ms
7 days agoHandshake completed500 ms
9 days agoHandshake completed172 ms
11 days agoHandshake completed447 ms
13 days agoHandshake completed191 ms
15 days agoHandshake completed247 ms
17 days agoHandshake completed142 ms
18 days agoHandshake completed312 ms
19 days agoHandshake completed354 ms
20 days agoHandshake completed162 ms
23 days agoHandshake completed138 ms
24 days agoHandshake completed220 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 pound.one and makes no claim about it beyond what these checks measured.