Remote MCP · Endpoint
FreshContext MCP server
No. FreshContext answered an MCP handshake 2 hours ago.
UpLast checked 2 hours ago
Server URL
https://api.freshcontext.dev/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.PrinceGabriel-lgtm/freshcontext
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 240 ms
- Tools exposed
- 22 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Context integrity for AI agents: evaluate freshness, confidence, provenance, and decision readiness.
- Website
- https://freshcontext.dev/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 240 ms |
| 1 day ago | Handshake completed | 170 ms |
| 3 days ago | Handshake completed | 186 ms |
| 3 days ago | Handshake completed | 177 ms |
| 4 days ago | Handshake completed | 170 ms |
| 5 days ago | Handshake completed | 304 ms |
| 7 days ago | Handshake completed | 259 ms |
| 10 days ago | Handshake completed | 186 ms |
| 12 days ago | Handshake completed | 198 ms |
| 15 days ago | Handshake completed | 280 ms |
| 17 days ago | Handshake completed | 310 ms |
| 19 days ago | Handshake completed | 233 ms |
| 21 days ago | Handshake completed | 190 ms |
| 23 days ago | Handshake completed | 217 ms |
| 25 days ago | Handshake completed | 291 ms |
| 26 days ago | Handshake completed | 178 ms |
| 28 days ago | Handshake completed | 332 ms |
| 29 days ago | Handshake completed | 239 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 FreshContext and makes no claim about it beyond what these checks measured.