dev.phpray/phpray

dev.phpray/phpray · v0.15.6 · data-and-databases

dev.phpray/phpray is healthy: it completed an MCP handshake in 3008 ms and exposes 10 tools. It scores 62/100.

Ask an agent why a PHP site is slow: every request with its SQL, HTTP calls, errors and N+1.

Endpoint: https://phpray.dev/mcp (streamable-http)

Repository · Website · JSON · Add to my inventory

Score 62/100

health17 / 25
authEase15 / 15
toolQuality15 / 15
maintenance7 / 15
adoption0 / 10
usage0 / 10
security8 / 10

Scoring v0.3, computed 2026-10-15T02:36:22.716Z.

Health history

Checked (UTC)StatusLatencyError
2026-10-14T23:25:44.302ZHealthy3008

Tools (10)

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.