Remote MCP · Endpoint
dev.phpray/phpray MCP server
No. dev.phpray/phpray answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://phpray.dev/mcp
The last check completed an MCP handshake.
- Registry name
- dev.phpray/phpray
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 452 ms
- Tools exposed
- 10 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Ask an agent why a PHP site is slow: every request with its SQL, HTTP calls, errors and N+1.
- Repository
- https://github.com/stephen1137/phpray
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 452 ms |
| 1 day ago | Handshake completed | 387 ms |
| 2 days ago | Handshake completed | 420 ms |
| 3 days ago | Handshake completed | 443 ms |
| 4 days ago | Handshake completed | 391 ms |
| 5 days ago | Handshake completed | 437 ms |
| 7 days ago | Handshake completed | 535 ms |
| 10 days ago | Handshake completed | 396 ms |
| 12 days ago | Handshake completed | 498 ms |
| 15 days ago | Handshake completed | 170 ms |
| 17 days ago | Handshake completed | 419 ms |
| 19 days ago | Handshake completed | 405 ms |
| 21 days ago | Handshake completed | 421 ms |
| 23 days ago | Handshake completed | 375 ms |
| 25 days ago | Handshake completed | 382 ms |
| 26 days ago | Handshake completed | 399 ms |
| 28 days ago | Handshake completed | 444 ms |
| 29 days ago | Handshake completed | 387 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 27 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 dev.phpray/phpray and makes no claim about it beyond what these checks measured.