Remote MCP · Endpoint
agent4.io MCP server
No. agent4.io answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://api.agent4.io/v1/mcp
The last check completed an MCP handshake.
- Registry name
- io.agent4/agent4-tenant
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 215 ms
- Tools exposed
- 50 tools
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- Build and run grounded business agents over MCP: agents, knowledge bases, skills, Storylines.
- Website
- https://agent4.io/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 215 ms |
| 2 days ago | Handshake completed | 215 ms |
| 4 days ago | Handshake completed | 214 ms |
| 5 days ago | Handshake completed | 247 ms |
| 7 days ago | Handshake completed | 222 ms |
| 8 days ago | Handshake completed | 236 ms |
| 9 days ago | Handshake completed | 216 ms |
| 12 days ago | Handshake completed | 217 ms |
| 13 days ago | Handshake completed | 221 ms |
| 15 days ago | Handshake completed | 224 ms |
| 16 days ago | Handshake completed | 215 ms |
| 18 days ago | Handshake completed | 217 ms |
| 19 days ago | Handshake completed | 217 ms |
| 20 days ago | Handshake completed | 219 ms |
| 20 days ago | Handshake completed | 213 ms |
| 21 days ago | Handshake completed | 215 ms |
| 22 days ago | Handshake completed | 260 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 agent4.io and makes no claim about it beyond what these checks measured.