dev.phpray/phpray
REMOTE · PHPRAY.DEV · SCANNED SEP 28
Ask an agent why a PHP site is slow: every request with its SQL, HTTP calls, errors and N+1.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 10 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability87
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1204 tokens (~100/item across 12 items; 10 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the dev.phpray/phpray MCP server?
dev.phpray/phpray is a hosted endpoint at https://phpray.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · phpray.dev
claude mcp add --transport http dev-phpray-phpray 'https://phpray.dev/mcp'
{
"mcpServers": {
"dev-phpray-phpray": {
"url": "https://phpray.dev/mcp"
}
}
} {
"servers": {
"dev-phpray-phpray": {
"type": "http",
"url": "https://phpray.dev/mcp"
}
}
} [mcp_servers.dev-phpray-phpray] url = "https://phpray.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-phpray-phpray": {
"type": "remote",
"url": "https://phpray.dev/mcp",
"enabled": true
}
}
} openclaw mcp add dev-phpray-phpray --url 'https://phpray.dev/mcp' --transport streamable-http
mcp_servers:
dev-phpray-phpray:
url: "https://phpray.dev/mcp" {
"McpServers": {
"dev-phpray-phpray": {
"Transport": "http",
"Url": "https://phpray.dev/mcp"
}
}
} assistant mcp add dev-phpray-phpray -t streamable-http -u 'https://phpray.dev/mcp'
{
"mcpServers": {
"dev-phpray-phpray": {
"type": "http",
"url": "https://phpray.dev/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +1
- Prompt “co_jest_wolne” was removed ▼ functional
- Prompt “co_sie_psuje” was removed ▼ functional
- Prompt “co_sie_zmienilo” was removed ▼ functional
- Prompt “ktora_wtyczka” was removed ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Schema quality: fail → pass ▲ functional
- The server now declares the “resources” capability functional
- New prompt “what_got_worse” functional
- New prompt “what_is_failing” functional
- New prompt “what_is_slow” functional
- New prompt “which_plugin_costs_most” functional
- New resource “Install PHPRay on your own PHP site” functional
- New resource “What this demo account is, and what it is not” functional
- Server version: 0.15.6 → 0.15.7 functional
- 22 Sept 26 67
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 28 Sept 2026 · Probed https://phpray.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=phpray.dev | CN=YE1,O=Let's Encrypt,C=US | 18 Sept 2026 | 17 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6b7f0b3e00873ae48c9b31fef9154b4652f |
| SANs: *.phpray.dev, phpray.dev | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of phpray.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| phpray.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://phpray.dev/mcp | Verified | 200 | |
| http (plaintext) | http://phpray.dev/mcp | HTTPS enforced | 308 | https://phpray.dev/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
phpray_alerts ~26
Alerts currently firing across every site this token can see, worst overrun first.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
phpray_compare ~137
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.
| Name | Type | Req | Description |
|---|---|---|---|
| from_a | integer | – | Start of range A (the earlier one), unix seconds. Without any range: the day before yesterday's 24 h against the last 24 h. |
| from_b | integer | – | Start of range B, unix seconds. |
| site_id | string | yes | Site id from phpray_sites. |
| to_a | integer | – | End of range A, unix seconds. |
| to_b | integer | – | End of range B, unix seconds. |
No output schema declared.
No examples provided.
phpray_components ~89
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many components to return. Default 20. |
| site_id | string | yes | Site id from phpray_sites. |
| window_minutes | integer | – | How far back to look. Default 1440. |
No output schema declared.
No examples provided.
phpray_errors ~102
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many to return. Default 20. |
| site_id | string | yes | Site id from phpray_sites. |
| window_minutes | integer | – | How far back to look. Default 1440. |
No output schema declared.
No examples provided.
phpray_overview ~83
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.
| Name | Type | Req | Description |
|---|---|---|---|
| site_id | string | yes | Site id from phpray_sites. |
| window_minutes | integer | – | How far back to look, in minutes. Default 60. |
No output schema declared.
No examples provided.
phpray_sites ~42
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
phpray_slow_pages ~87
The slowest URLs on a site, with request counts and p95, from the request timeseries. Answers "which page is slow".
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many URLs to return. Default 25. |
| site_id | string | yes | Site id from phpray_sites. |
| window_minutes | integer | – | How far back to look. Default 1440. |
No output schema declared.
No examples provided.
phpray_slow_queries ~88
SQL fingerprints ordered by time spent, with call counts and the caller when known. Literals are already masked. Answers "which query is slow".
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many queries to return. Default 20. |
| site_id | string | yes | Site id from phpray_sites. |
| window_minutes | integer | – | How far back to look. Default 1440. |
No output schema declared.
No examples provided.
phpray_trace ~60
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.
| Name | Type | Req | Description |
|---|---|---|---|
| trace_id | string | yes | Trace id from phpray_traces. |
No output schema declared.
No examples provided.
phpray_traces ~114
Recent requests for a site. Filter with min_ms and status to find the bad ones, then pass an id to phpray_trace.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many to return. Default 50. |
| min_ms | integer | – | Only requests slower than this. |
| site_id | string | yes | Site id from phpray_sites. |
| status | integer | – | Only this HTTP status, e.g. 500. |
| window_minutes | integer | – | How far back to look. Default 1440. |
No output schema declared.
No examples provided.
What is the dev.phpray/phpray MCP server?
dev.phpray/phpray is an MCP server listed in the public MCP registry as dev.phpray/phpray. Ask an agent why a PHP site is slow: every request with its SQL, HTTP calls, errors and N+1. This page covers its hosted endpoint (https://phpray.dev/mcp).
Is the dev.phpray/phpray MCP server safe to use?
dev.phpray/phpray scores 70 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the dev.phpray/phpray MCP server expose?
dev.phpray/phpray exposes 10 tools: phpray_sites, phpray_overview, phpray_slow_pages, phpray_slow_queries, phpray_components, and 5 more. Their descriptions and schemas cost roughly 828 tokens of context every time the server is loaded.
Does the dev.phpray/phpray MCP server require authentication?
No. We connected to dev.phpray/phpray without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the dev.phpray/phpray MCP server still maintained?
dev.phpray/phpray is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.