mcpbeat Sign in

Phonon MCP Server

not responding

Phonon is listed as active in the registry but did not answer our last check.

Monitoring + status pages set up by talking to Claude. Auto-detects 30+ SDKs and your URLs.

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 91 days of history · worst day 0%
91 days agonow
0.0%
Uptime 24h
0 of 91 checks
—
Tools
hidden behind auth
90 ms
Response time
average over 24h
open, no key
Access
streamable-http

Phonon does not always answer

Over the last week it answered 0.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.

run in your terminal
claude mcp add phonon --transport http https://phonon-mcp.qxie13.workers.dev/mcp
Settings → Connectors → Add custom connector, then paste this address
https://phonon-mcp.qxie13.workers.dev/mcp
~/.codex/config.toml
[mcp_servers.phonon]
url = "https://phonon-mcp.qxie13.workers.dev/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "phonon": {
      "url": "https://phonon-mcp.qxie13.workers.dev/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "phonon": {
      "type": "http",
      "url": "https://phonon-mcp.qxie13.workers.dev/mcp"
    }
  }
}

Endpoints

URLTransportStateLatencyChecked
https://phonon-mcp.qxie13.workers.dev/mcp streamable-http answering 90 ms 12 min ago

Alternatives to Phonon

same job, measured the same way
Phare
by phare

Manage the uptime monitoring, incidents and status pages of your Phare organization.

answering
Pingwell
by pingwell

Uptime checks, cron heartbeats, status pages and alerts, set up by your agent.

answering
Sentinel
by rootstuff

Uptime, SSL, DNS and domain monitoring you can talk to from Claude or any MCP client.

answering
Staygreen
by phuryn

Uptime monitoring and status pages for apps built with coding agents: status, incidents, setup.

154 installs/wk answering
Hyperping
by hyperping

Uptime, API and server monitoring with outages, reporting, on-call and status pages.

69 tools answering
StatOSS
by statoss

Status pages and uptime monitoring: read status, monitors and incidents; open incidents.

answering
losclouds
by losclouds

Cloud and SaaS service status, plus your team's monitors, status pages, incidents, and alerts.

answering
Statuser
by statuser-cloud

Monitor services, manage incidents and status pages in Statuser.cloud from your AI assistant.

1 033 installs/wk answering

Phonon — questions

Answers built from our own checks of this server.

Is Phonon working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 91 checks got a reply (0.0%), average response time 90 ms. The bar chart above shows every period we have measured.
Is Phonon still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
The registry lists Phonon as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Phonon?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Phonon need an API key?
No. Phonon completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. This is what we observed, not what the docs claim.