Remote MCP · Endpoint
Andru MCP server
No. Andru answered an MCP handshake 19 minutes ago.
UpLast checked 19 minutes ago
Server URL
https://mcp-server-andru-intelligence.onrender.com/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.geter-andru/andru-intelligence
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 258 ms
- Tools exposed
- 36 tools
- Uptime, last 30 days
- 100% from 12 checks
- Described by its publisher as
- Revenue intelligence for complex B2B growth.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 19 minutes ago | Handshake completed | 258 ms |
| 10 days ago | Handshake completed | 158 ms |
| 10 days ago | Handshake completed | 139 ms |
| 11 days ago | Handshake completed | 162 ms |
| 13 days ago | Handshake completed | 134 ms |
| 14 days ago | Handshake completed | 234 ms |
| 14 days ago | Handshake completed | 219 ms |
| 15 days ago | Handshake completed | 130 ms |
| 17 days ago | Handshake completed | 297 ms |
| 19 days ago | Handshake completed | 370 ms |
| 21 days ago | Handshake completed | 350 ms |
| 24 days ago | Credentials required | — |
The last 12 checks. Full history is kept for 30 days; the all-time counter stands at 12 responding of 12.
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 Andru and makes no claim about it beyond what these checks measured.