_ registry / mcp streamable-http · checked 12m ago

phpray

https://phpray.dev

Registry code: b5eb764797019da7

api record

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

endpoint
https://phpray.dev/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is phpray live?
Yes — it answered the hub's last check (checked 12m ago). It answered 100% of checks over the last 30 days.
Is phpray free to use?
Not measured yet.
What tools does phpray have?
10 tools: phpray_sites, phpray_overview, phpray_components, phpray_trace, phpray_compare, phpray_slow_pages, phpray_slow_queries, phpray_errors, ….
Is phpray safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 97.8%· all time 97.8%

latency
351ms

last good check

priced tools
0

of 10 tools

_ answered our checks, 90 days 277 checks · signed record
  • down → live
  • degraded → down· fetch failed
  • live → degraded· fetch failed
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
infrastructure & devops monitoring & observability
used for
  • find slow pages on a php site
  • find slow sql queries
  • see php errors on a site
  • compare performance before and after a deploy
  • trace one php request
takes → gives
text → data
tools
10 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 10 tools
10 never probed 0 of 10 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • phpray_sites reads unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • phpray_overview reads unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "site_id"
  ],
  "properties": {
    "site_id": {
      "type": "string",
      "description": "Site id from phpray_sites."
    },
    "window_minutes": {
      "type": "integer",
      "description": "How far back to look, in minutes. Default 60."
    }
  }
}
    arguments 16 lines
  • phpray_components reads unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "site_id"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "description": "How many components to return. Default 20."
    },
    "site_id": {
      "type": "string",
      "description": "Site id from phpray_sites."
    },
    "window_minutes": {
      "type": "integer",
      "description": "How far back to look. Default 1440."
    }
  }
}
    arguments 20 lines
  • phpray_trace reads unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "trace_id"
  ],
  "properties": {
    "trace_id": {
      "type": "string",
      "description": "Trace id from phpray_traces."
    }
  }
}
    arguments 12 lines
  • phpray_compare reads unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "site_id"
  ],
  "properties": {
    "to_a": {
      "type": "integer",
      "description": "End of range A, unix seconds."
    },
    "to_b": {
      "type": "integer",
      "description": "End of range B, unix seconds."
    },
    "from_a": {
      "type": "integer",
      "description": "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": {
      "type": "integer",
      "description": "Start of range B, unix seconds."
    },
    "site_id": {
      "type": "string",
      "description": "Site id from phpray_sites."
    }
  }
}
    arguments 28 lines
  • phpray_slow_pages reads unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "site_id"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "description": "How many URLs to return. Default 25."
    },
    "site_id": {
      "type": "string",
      "description": "Site id from phpray_sites."
    },
    "window_minutes": {
      "type": "integer",
      "description": "How far back to look. Default 1440."
    }
  }
}
    arguments 20 lines
  • phpray_slow_queries reads unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "site_id"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "description": "How many queries to return. Default 20."
    },
    "site_id": {
      "type": "string",
      "description": "Site id from phpray_sites."
    },
    "window_minutes": {
      "type": "integer",
      "description": "How far back to look. Default 1440."
    }
  }
}
    arguments 20 lines
  • phpray_errors reads unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "site_id"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "description": "How many to return. Default 20."
    },
    "site_id": {
      "type": "string",
      "description": "Site id from phpray_sites."
    },
    "window_minutes": {
      "type": "integer",
      "description": "How far back to look. Default 1440."
    }
  }
}
    arguments 20 lines
  • phpray_traces reads unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "site_id"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "description": "How many to return. Default 50."
    },
    "min_ms": {
      "type": "integer",
      "description": "Only requests slower than this."
    },
    "status": {
      "type": "integer",
      "description": "Only this HTTP status, e.g. 500."
    },
    "site_id": {
      "type": "string",
      "description": "Site id from phpray_sites."
    },
    "window_minutes": {
      "type": "integer",
      "description": "How far back to look. Default 1440."
    }
  }
}
    arguments 28 lines
  • phpray_alerts reads unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id b5eb764797019da7.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/b5eb764797019da7/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/b5eb764797019da7/badge.svg)](https://brick.blue/agent/b5eb764797019da7?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.