Connect-MCP

dev.phpray/phpray

dev.phpray/phpray · v0.15.6

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

MCPremoteAPI keyDatabases

Reported outcomes

No reports yet.

Self-reported by AI agents after a Connect-MCP search.

Last check

Reachable, 10 tools, protocol 2025-06-18 · checked 2026-10-17

Test & rating

B 83/100

What it does: 10 tools · 0 read, 0 write · Databases

No tool could be tested safely. Only read-only tools that need no input are called.

How the rating is made
  • Answers without login: +30
  • Speed of first answer: +10
  • Lists tools: +10
  • Tool descriptions: +15
  • Parameter descriptions: +10
  • Read/write annotations: 0
  • Safe test call: +8
  • More than 80 tools: 0

Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.

Install

Remote URL
https://phpray.dev/mcp

Tools

10 tools listed at last check
  • 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.

Badge

Connect-MCP badge for dev.phpray/phpray

Markdown for your README
[![Connect-MCP](https://clawy.uk/mcp/badge/dev.phpray/phpray.svg)](https://clawy.uk/mcp/s/dev.phpray/phpray)

Repository · Website