90trust / 100

Phpray

by phpray.dev in Developer tools

MCP serverPassing, checked 6 h ago

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

https://phpray.dev/mcp

Last 30 days

All checks passedSome failedAll failedNot checked
Uptime
100%
Response time
229 ms typical, 229 ms slowest 5%
Last check
6 h ago
Next check
in 21 min

How to call it

Add it to any MCP client that supports remote servers.

{
  "mcpServers": {
    "phpray": {
      "type": "http",
      "url": "https://phpray.dev/mcp"
    }
  }
}

10 tools

  • phpray_sites

    List 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_overview

    Headline 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_pages

    The slowest URLs on a site, with request counts and p95, from the request timeseries. Answers "which page is slow".

  • phpray_slow_queries

    SQL fingerprints ordered by time spent, with call counts and the caller when known. Literals are already masked. Answers "which query is slow".

  • phpray_components

    Time 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_errors

    Requests 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_traces

    Recent requests for a site. Filter with min_ms and status to find the bad ones, then pass an id to phpray_trace.

  • phpray_trace

    One 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_compare

    Two 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_alerts

    Alerts currently firing across every site this token can see, worst overrun first.

Security scan

  • No findings. We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks

WhenResultHTTPTime
6 h agoPassed200229 ms