Remote MCP · Endpoint
FreshProof MCP server
No. FreshProof answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://freshproof.ricardobessellp-11d.workers.dev/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.ricksporto/freshproof
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 282 ms
- Tools exposed
- 4 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Timestamped public URL observations with SHA-256 fingerprints, paid in USDC on Base via x402.
- Repository
- https://github.com/ricksporto/freshproof
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 282 ms |
| 1 day ago | Handshake completed | 625 ms |
| 2 days ago | Handshake completed | 459 ms |
| 3 days ago | Handshake completed | 698 ms |
| 4 days ago | Handshake completed | 323 ms |
| 5 days ago | Handshake completed | 482 ms |
| 6 days ago | Handshake completed | 455 ms |
| 9 days ago | Handshake completed | 319 ms |
| 11 days ago | Handshake completed | 310 ms |
| 14 days ago | Handshake completed | 383 ms |
| 16 days ago | Handshake completed | 319 ms |
| 18 days ago | Handshake completed | 338 ms |
| 20 days ago | Handshake completed | 632 ms |
| 22 days ago | Handshake completed | 434 ms |
| 24 days ago | Handshake completed | 279 ms |
| 26 days ago | Handshake completed | 304 ms |
| 27 days ago | Handshake completed | 604 ms |
| 29 days ago | Handshake completed | 582 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.
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 FreshProof and makes no claim about it beyond what these checks measured.