Remote MCP · Endpoint
InfraPulse MCP server
No. InfraPulse answered an MCP handshake 2 hours ago.
UpLast checked 2 hours ago
Server URL
https://infrapulse.ai/mcp
The last check completed an MCP handshake.
- Registry name
- ai.infrapulse/infrapulse
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 234 ms
- Tools exposed
- 6 tools
- Uptime, last 30 days
- 83.3% from 18 checks
- Described by its publisher as
- AI agent infrastructure for discovery, authorization, execution, identity, and signed receipts.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 234 ms |
| 1 day ago | Handshake completed | 203 ms |
| 3 days ago | Handshake completed | 228 ms |
| 3 days ago | Handshake completed | 242 ms |
| 4 days ago | Handshake completed | 198 ms |
| 5 days ago | Handshake completed | 229 ms |
| 7 days ago | Handshake completed | 229 ms |
| 10 days ago | Handshake completed | 200 ms |
| 12 days ago | Handshake completed | 210 ms |
| 15 days ago | Handshake completed | 202 ms |
| 17 days ago | Handshake completed | 208 ms |
| 19 days ago | Handshake completed | 191 ms |
| 21 days ago | Failed - the check failed for an unclassified reason | — |
| 23 days ago | Failed - the check failed for an unclassified reason | — |
| 25 days ago | Failed - the check failed for an unclassified reason | — |
| 26 days ago | Handshake completed | 278 ms |
| 28 days ago | Handshake completed | 285 ms |
| 29 days ago | Handshake completed | 266 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 21 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 InfraPulse and makes no claim about it beyond what these checks measured.