All servers · Databases · Monitoring & logs
dev.phpray/phpray
dev.phpray/phpray · v0.15.6
Measured by MCP Station
| Last check | Reachable |
|---|---|
| Checked at | — |
| Check success 7 / 30 days | — |
| First-try success 30 days | — |
| Median response | — |
| Lookups 30 days | — |
| Authentication | No auth |
| MCP version | 2025-06-18 |
| Rank score | — |
| Declared risk | Not declared (tools carry no read/destructive hints) |
| Capabilities declared | prompts, resources, tools |
| Tool definitions | 10 tools · with description 100% · input schema is an object 100% · read/destructive hints 0% |
Description written by the publisher, not verified
Ask an agent why a PHP site is slow: every request with its SQL, HTTP calls, errors and N+1.
Connect
streamable-http · https://phpray.dev/mcp
claude mcp add --transport http phpray https://phpray.dev/mcp{
"mcpServers": {
"phpray": {
"url": "https://phpray.dev/mcp"
}
}
}Tools as reported by the server
phpray_sitesList the PHP sites this token can see, with requests, p95 latency and error rate. Start here: every other tool needs a site_id from this list.phpray_overviewHeadline numbers for one site over a time window: requests, errors, p50/p95/p99 latency, database share and N+1 count. Use this before digging into anything else.phpray_slow_pagesThe slowest URLs on a site, with request counts and p95, from the request timeseries. Answers "which page is slow".phpray_slow_queriesSQL fingerprints ordered by time spent, with call counts and the caller when known. Literals are already masked. Answers "which query is slow".phpray_componentsTime attributed to each plugin, theme or vendor package on profiled requests. Answers "which plugin is slowing the site down". Empty when function profiling is off.phpray_errorsRequests that failed on a site: PHP errors and warnings with file and line where PHP raised one, plus 5xx responses that carry no PHP error. Pass an id to phpray_trace to see what one of them did.phpray_tracesRecent requests for a site. Filter with min_ms and status to find the bad ones, then pass an id to phpray_trace.phpray_traceOne request in full: wall time split into PHP, database and outbound HTTP, every query, every external call, errors, and the component breakdown when the request was profiled.phpray_compareTwo time ranges for one site side by side. Use it to check whether a deployment, a plugin update or a configuration change made things better or worse.phpray_alertsAlerts currently firing across every site this token can see, worst overrun first.
Repository · Website · JSON · Text for agents · Registry updated 2026-09-22