Remote MCP · Endpoint
AgentFlow MCP server
No. AgentFlow answered an MCP handshake 2 hours ago.
UpLast checked 2 hours ago
Server URL
https://agentflow.watch/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.leonidahqadmin-cell/agentflow
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 377 ms
- Tools exposed
- 6 tools
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- Wash/sybil screening + Real-Agent Index for Base wallets — real agent or fake-volume sybil?
- Website
- https://agentflow.watch/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 377 ms |
| 2 days ago | Handshake completed | 195 ms |
| 4 days ago | Handshake completed | 219 ms |
| 5 days ago | Handshake completed | 149 ms |
| 7 days ago | Handshake completed | 312 ms |
| 8 days ago | Handshake completed | 186 ms |
| 9 days ago | Handshake completed | 252 ms |
| 12 days ago | Handshake completed | 160 ms |
| 13 days ago | Handshake completed | 173 ms |
| 15 days ago | Handshake completed | 162 ms |
| 17 days ago | Handshake completed | 214 ms |
| 18 days ago | Handshake completed | 273 ms |
| 19 days ago | Handshake completed | 168 ms |
| 20 days ago | Handshake completed | 140 ms |
| 20 days ago | Handshake completed | 163 ms |
| 21 days ago | Handshake completed | 259 ms |
| 23 days ago | Handshake completed | 232 ms |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.
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 AgentFlow and makes no claim about it beyond what these checks measured.