Remote MCP · Endpoint

Fresh402 Agent Intelligence MCP server

No. Fresh402 Agent Intelligence answered an MCP handshake 55 minutes ago.

UpLast checked 55 minutes ago

Server URL

https://fresh402.kirilllabs.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.kirillradchenko96/fresh402
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
319 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Web/API change intelligence; bounded Base facts. Free Register, seven paid tools; x402/MPP/prepaid.
Listing
From the official MCP registry (active).
Recent checks of Fresh402 Agent Intelligence
CheckedResultHandshake
55 minutes agoHandshake completed319 ms
1 day agoHandshake completed447 ms
2 days agoHandshake completed916 ms
5 days agoHandshake completed444 ms
8 days agoHandshake completed638 ms
10 days agoHandshake completed399 ms
12 days agoHandshake completed482 ms
14 days agoHandshake completed880 ms
16 days agoHandshake completed291 ms
18 days agoHandshake completed614 ms
20 days agoHandshake completed532 ms
22 days agoHandshake completed523 ms
23 days agoHandshake completed122 ms

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

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