Remote MCP · Endpoint
PeppolStatus MCP server
No. PeppolStatus answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://mcp.peppolstatus.com/
The last check completed an MCP handshake.
- Registry name
- com.peppolstatus/api
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 281 ms
- Tools exposed
- 65 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- Peppol market intelligence and network monitoring: migrations, provider churn, leads, and uptime.
- Website
- https://peppolstatus.com/mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 281 ms |
| 18 hours ago | Handshake completed | 271 ms |
| 2 days ago | Handshake completed | 280 ms |
| 3 days ago | Handshake completed | 318 ms |
| 4 days ago | Handshake completed | 606 ms |
| 5 days ago | Handshake completed | 469 ms |
| 6 days ago | Handshake completed | 325 ms |
| 7 days ago | Handshake completed | 374 ms |
| 10 days ago | Handshake completed | 245 ms |
| 13 days ago | Handshake completed | 484 ms |
| 15 days ago | Handshake completed | 430 ms |
| 17 days ago | Handshake completed | 237 ms |
| 19 days ago | Handshake completed | 230 ms |
| 21 days ago | Handshake completed | 53 ms |
| 23 days ago | Handshake completed | 251 ms |
| 25 days ago | Handshake completed | 269 ms |
| 27 days ago | Handshake completed | 436 ms |
| 28 days ago | Handshake completed | 288 ms |
| 29 days ago | Handshake completed | 370 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 30 responding of 30.
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 PeppolStatus and makes no claim about it beyond what these checks measured.