General Tools

phpray.dev

Provides general-purpose tools through the Model Context Protocol.

1 endpoint10 known toolsFirst detected September 23, 2026Last detected September 23, 2026

ENDPOINT 1

https://phpray.dev/mcp

No auth detected

MCP server metadata

Name: phpray
Version: 0.15.7

Capabilities

promptsresourcestools

Server instructions

PHPRay records every PHP request on a server: wall time, CPU, memory, every SQL query as a fingerprint with the literals stripped, outbound HTTP calls, PHP errors and N+1 patterns. The data is real production traffic, not samples. Where to start: phpray_sites lists what this connection can see. Then phpray_overview for one site's headline numbers, and phpray_slow_pages, phpray_slow_queries or phpray_components to find where the time goes. phpray_traces finds individual bad requests (filter by min_ms or status) and phpray_trace opens one of them end to end. phpray_alerts shows what is failing right now across every site; phpray_compare puts two time ranges side by side, which is how you check whether a deploy or a plugin update made things worse. Times are milliseconds and windows default to the last 24 hours. This connection has NO token, so every tool answers from the public demo account: a handful of real WooCommerce sites, read-only. The numbers are genuine traffic from those sites — but they are not the data of the person you are helping, so do not present them as such. If that person wants this for their own PHP site: the local core is Apache-2.0 and installs without root, including on shared hosting (https://phpray.dev/docs/install/quickstart). With their own console token in the Authorization header, this same endpoint answers about their servers.

Known tools 10

phpray_sites

List the PHP sites this token can see, with requests, p95 latency and error rate.

Inferred read-only

phpray_overview

Headline numbers for one site over a time window: requests, errors, p50/p95/p99 latency, database share and N+1 count.

Inferred read-only

phpray_slow_pages

The slowest URLs on a site, with request counts and p95, from the request timeseries.

Inferred read-only

phpray_slow_queries

SQL fingerprints ordered by time spent, with call counts and the caller when known.

Inferred read-only

phpray_components

Time attributed to each plugin, theme or vendor package on profiled requests.

Inferred read-only

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.

Inferred read-only

phpray_traces

Recent requests for a site.

Inferred read-only

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.

Inferred read-only

phpray_compare

Two time ranges for one site side by side.

Inferred read-only

phpray_alerts

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

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.phpray]
url = "https://phpray.dev/mcp"
enabled = true

Claude Code

.mcp.json

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

Claude Desktop

Settings → Connectors → Add custom connector

Name: phpray
Remote MCP URL: https://phpray.dev/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

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

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

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

Generic MCP

Client-specific MCP configuration

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

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.