Remote MCP · Endpoint
Pugi MCP server
No. Pugi answered an MCP handshake 46 minutes ago.
UpLast checked 46 minutes ago
Server URL
https://api.pugi.io/api/agent/v1/mcp
The last check completed an MCP handshake.
- Registry name
- io.pugi/pugi
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 514 ms
- Tools exposed
- 15 tools
- Uptime, last 30 days
- 100% from 12 checks
- Described by its publisher as
- AI product team: builds and publishes websites from a brief, logos, security checks.
- Website
- https://pugi.io/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 46 minutes ago | Handshake completed | 514 ms |
| 3 days ago | Handshake completed | 577 ms |
| 12 days ago | Handshake completed | 375 ms |
| 13 days ago | Handshake completed | 343 ms |
| 14 days ago | Handshake completed | 358 ms |
| 15 days ago | Handshake completed | 496 ms |
| 16 days ago | Handshake completed | 417 ms |
| 17 days ago | Handshake completed | 252 ms |
| 18 days ago | Handshake completed | 346 ms |
| 19 days ago | Handshake completed | 364 ms |
| 22 days ago | Handshake completed | 613 ms |
| 25 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 Pugi and makes no claim about it beyond what these checks measured.