Back to search
100
MCP live MCP 2025-06-18 streamable-http

dev.phpray/phpray

dev.phpray/phpray

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

Watch this dependency Share evidence report
Uptime
100.0%
5 direct probes · 30d
Response
1561ms
last probe
Tools
10
callable
Resources
2
readable
Prompts
4
available
Primary URL
https://phpray.dev/mcp
Score: 100/100
Handshake verified by our own probe.
pass Answers the MCP handshake 50/50
The handshake and the list calls succeeded on the primary URL.
pass Lists tools, resources or prompts 30/30
10 tools, 2 resources, 4 prompts returned.
pass 3 or more catalogue items 10/10
16 items in total; 3 or more earns these points.
pass Describes itself 10/10
92 characters; more than 30 earns these points.

Tools · 10

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.

Resources · 2

Install PHPRay on your own PHP site

How the person you are helping gets this on their own server, including shared hosting where no agent can be installed.

phpray://install
What this demo account is, and what it is not

The scope and limits of the public read-only account these tools answer from.

phpray://demo

Prompts · 4

what_is_slow

Walk the fleet, find the site that hurts most and say why — in plain words.

which_plugin_costs_most

Attribute request time to WordPress plugins and themes, with the numbers.

what_is_failing

Check alerts and failing requests, and separate real breakage from scanner noise.

what_got_worse

Compare two time windows to see whether a deploy or an update made things slower.

How to use

Claude Desktop or claude.ai: add a custom connector (Customize → Connectors; on Team and Enterprise plans an owner adds it under Organization settings → Connectors) with this server URL: https://phpray.dev/mcp

Cursor or Cline: add to your MCP config:

{
  "mcpServers": {
    "dev.phpray/phpray": {
      "url": "https://phpray.dev/mcp",
      "transport": "streamable-http"
    }
  }
}