_ registry / mcp streamable-http · checked 2h ago

prismix-status

https://prismix.dev

Registry code: 859506c638f850b9

api record

Real-time status for 75+ AI services (OpenAI, Anthropic, Cursor). No auth, CORS-enabled.

from a public catalogue that lists it, not from the operator

endpoint
https://prismix.dev/api/v1/mcp
protocol
streamable-http ·2024-11-05
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 prismix-status live?
Yes — it answered the hub's last check (checked 2h ago). It answered 99% of checks over the last 30 days.
Is prismix-status free to use?
Yes — the hub reached it with no key and no payment.
What tools does prismix-status have?
3 tools: get_incident_history, list_ai_services, check_ai_status.
Is prismix-status 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
99.4%

90 days 99.5%· all time 99.5%

latency
599ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 632 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
infrastructure & devops monitoring & observability
used for
  • check status of ai services
  • get incident history of an ai service
  • list tracked ai services
takes → gives
text → data
tools
3 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 3 tools
2 open 1 never probed 2 of 3 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.

  • list_ai_services reads open 16h ago

    List all 75+ AI services tracked by Prismix with their current status. Returns service ID, name, category, and operational indicator.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • check_ai_status reads open 16h ago

    Check the current operational status of AI services tracked by Prismix. Returns status indicator (operational/degraded/outage), active incident count, and 30-day uptime. Covers 75+ services: OpenAI, Anthropic, Cursor, Mistral, Perplexity, Google AI, and more. Pass a service name/id to filter, or omit to see all.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "service": {
      "type": "string",
      "description": "Service ID or partial name (e.g. \"openai\", \"anthropic\", \"cursor\"). Case-insensitive. Omit to check all 75+ services at once."
    }
  }
}
    arguments 9 lines
  • get_incident_history reads unknown 16h ago

    Get the recent incident history (last 30 days) for a specific AI service — past outages and degradations with impact level, start time, and resolution/duration. Useful for answering "has Anthropic been reliable lately?" or "how often does Cursor go down?". Also returns the 30-day uptime percentage and total recent-incident count.

    mcp-tool

    {
  "type": "object",
  "required": [
    "service"
  ],
  "properties": {
    "service": {
      "type": "string",
      "description": "Service ID or partial name (e.g. \"anthropic\", \"openai\", \"cursor\"). Case-insensitive. Required."
    }
  }
}
    arguments 12 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 859506c638f850b9.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/859506c638f850b9/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/859506c638f850b9/badge.svg)](https://brick.blue/agent/859506c638f850b9?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
70%

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.