Remote MCP · Endpoint

ProofPrice MCP server

No. ProofPrice answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes ago

Server URL

https://proofprice.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.proofprice/pricepaid
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
210 ms
Tools exposed
39 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Prices people actually paid, from official open data: homes, rents, fuel, energy, food, medicines.
Listing
From the official MCP registry (active).
Recent checks of ProofPrice
CheckedResultHandshake
34 minutes agoHandshake completed210 ms
9 days agoHandshake completed89 ms
10 days agoHandshake completed237 ms
11 days agoHandshake completed119 ms
12 days agoHandshake completed249 ms
14 days agoHandshake completed153 ms
14 days agoHandshake completed168 ms
15 days agoHandshake completed115 ms
17 days agoHandshake completed95 ms
19 days agoHandshake completed112 ms
21 days agoHandshake completed73 ms
24 days agoHandshake completed175 ms
26 days agoHandshake completed869 ms
28 days agoHandshake completed67 ms

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

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