Remote MCP · Endpoint
DevStackPulse MCP server
No. DevStackPulse answered an MCP handshake 36 minutes ago.
UpLast checked 36 minutes ago
Server URL
https://stackpulse-mcp.onrender.com/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.raulvallejo/devstackpulse
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 257 ms
- Tools exposed
- 3 tools
- Uptime, last 30 days
- 100% from 12 checks
- Described by its publisher as
- Breaking changes and weekly digests for the APIs and SDKs in your dev stack.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 36 minutes ago | Handshake completed | 257 ms |
| 3 days ago | Handshake completed | 163 ms |
| 13 days ago | Handshake completed | 287 ms |
| 14 days ago | Handshake completed | 285 ms |
| 15 days ago | Handshake completed | 140 ms |
| 16 days ago | Handshake completed | 251 ms |
| 17 days ago | Handshake completed | 176 ms |
| 18 days ago | Handshake completed | 117 ms |
| 19 days ago | Handshake completed | 131 ms |
| 20 days ago | Handshake completed | 140 ms |
| 22 days ago | Handshake completed | 140 ms |
| 25 days ago | Handshake completed | 284 ms |
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 DevStackPulse and makes no claim about it beyond what these checks measured.