Real-time status for 75+ AI services (OpenAI, Anthropic, Cursor). No auth, CORS-enabled.
Prismix MCP server exists for a simple reason — assistants are far more useful when they can act on Prismix directly instead of describing what you should do. Real-time status for 75+ AI services (OpenAI, Anthropic, Cursor). No auth, CORS-enabled.
A Model Context Protocol (MCP) server exposing real-time operational status for 75+ AI services — OpenAI, Anthropic, Cursor, GitHub Copilot, Gemini, Mistral, Perplexity, DeepSeek, Hugging Face, and more. Powered by Prismix, which monitors each provider's official status feed around the clock.
Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
Once Prismix is connected, these are the calls the assistant has available:
Cursor — Add to .cursor/mcp.json in your project (or ~/.cursor/mcp.json globally):check_ai_status — Returns per service: status indicator (Operational / Degraded / Partial outage / Major outage), active incident count, 30-day uptime %, responseget_incident_history — Recent incident history (last 30 days) for one service — past outages and degradations with impact level, start time, and resolution/duration, pluslist_ai_services — Enumerates all 75+ tracked services with ID, name, category, and current indicator. Useful for discovering exact service IDsAmong the AI and media services options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Prismix's toolset — Cursor, check_ai_status, get_incident_history and 1 more — is a fair guide to whether it matches your workflow. It is maintained by Prismor; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Cursor | Add to .cursor/mcp.json in your project (or ~/.cursor/mcp.json globally): |
| check_ai_status | Returns per service: status indicator (Operational / Degraded / Partial outage / Major outage), active incident count, 30-day uptime %, response latency, and a link to the full incident history. |
| get_incident_history | Recent incident history (last 30 days) for one service — past outages and degradations with impact level, start time, and resolution/duration, plus the 30-day uptime %. |
| list_ai_services | Enumerates all 75+ tracked services with ID, name, category, and current indicator. Useful for discovering exact service IDs. |
{
"mcpServers": {
"prismix-status": {
"url": "https://prismix.dev/api/v1/mcp"
}
}
}Configuration as documented by the project. Restart the client after saving.
Build a programmable telecommunications stack for connecting telephony services with the Internet via a cloud-based utility.
Search built for AI, not humans — semantic web search that returns model-ready content, plus code context.
Answers, not links — delegate questions to Perplexity's search-grounded models and get cited responses back.
Give your assistant a voice — text-to-speech, voice cloning and audio tools from the ElevenLabs API.
Give your assistant a real code sandbox — isolated cloud VMs for actually running the code it writes.
The ML hub in your context window — search models, datasets, papers and run Spaces from the official server.