Vendor Status MCP runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 20 Sep 2026.
Status-page map for 1,100+ SaaS/cloud vendors plus 15,700+ incidents. No API key.
What the code does
We read the source, 6 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
proc = subprocess.run(
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Alternatives to Vendor Status MCP
same job, measured the same wayLive status, incidents and maintenance windows for 8,000+ cloud and SaaS status pages.
Cloud and SaaS service status, plus your team's monitors, status pages, incidents, and alerts.
Read-only: recent incidents from public Atlassian Statuspage pages. Free, no API key.
Monitor services, manage incidents and status pages in Statuser.cloud from your AI assistant.
Manage uptime monitors, incidents and status pages from any MCP client.
Query Statuspage management API: pages, page details, incidents.
Uptime checks, status pages, incidents, and maintenance for websites, APIs, DNS, and TCP.
PingCheck status monitoring for AI agents. Read public pages or your own monitors via pk_ API key.
Vendor Status MCP — questions
Answers built from our own checks of this server.