Check vendor status from your code — or let Claude do it.
Statusfield now has a read-only REST API and a hosted MCP server. Query the live, official status of 2,000+ services with one curl command — or connect Claude and let your agent check whether it’s your bug or their outage before you start debugging.
Available on the Hobby plan and up · One sf_ key for both REST and MCP
Statusfield’s API is a read-only REST endpoint and a hosted MCP server that expose the live, official status of the 2,000+ services in our catalog — so a script, a dashboard, or an AI agent can check whether a vendor is down without opening a dozen status pages.
It relays the status vendors publish, normalized into one format. It doesn’t predict outages, and it can’t change anything in your account — it’s read-only.
Query it yourself, or let your AI agent do it
Same data, same key. Pick the surface that fits the job.
For scripts, dashboards, and runbooks
Bearer-authenticated JSON over HTTPS. Pull your monitors, the full catalog, or the list of everything currently down. Rate limits and monthly quota come back in the X-RateLimit-* and X-Quota-* response headers.
curl -H "Authorization: Bearer sf_your_key" https://statusfield.com/api/v2/outagesFor Claude Desktop and Claude Code
A hosted StreamableHTTP MCP server with four read-only tools. Connect it once and ask, in plain English, whether a service — or your own stack — is down. The answer comes from live data, not the model’s training cutoff.
claude mcp add --transport http statusfield https://statusfield.com/api/mcp --header "Authorization: Bearer sf_your_key"Connect Statusfield to Claude in one line
Paste this into your terminal. Claude Code — and any MCP-compatible client — can then ask Statusfield for live service status while it works.
claude mcp add --transport http statusfield https://statusfield.com/api/mcp --header "Authorization: Bearer sf_your_key"Swap sf_your_key for a key from Integrations → API Keys.
Endpoints and tools
Everything in v1 is read-only. Full request and response shapes live in the docs.
REST API/api/v2
| Endpoint | Returns |
|---|---|
GET/api/v2/monitors | Your active monitors and their current status. |
GET/api/v2/monitors?filter=outages | Only your monitors currently in a non-operational state. |
GET/api/v2/services?search= | Search the 2,000+ service catalog by name. |
GET/api/v2/services/{slug} | One service plus its components’ current status. |
GET/api/v2/outages | Every catalog service currently degraded or down. |
MCP tools/api/mcp
| Tool | What it does |
|---|---|
search_services | Find a service in the catalog by name. |
get_service_status | Current status of a service and its components, by slug. |
list_outages | Everything currently degraded or down across the catalog. |
list_my_down_services | Which of your own monitored services are down right now. |
Tools query the public catalog. Your own monitors live at GET /api/v2/monitors over REST.
A few things you can do today
List every service that’s currently down
curl -H "Authorization: Bearer sf_your_key" https://statusfield.com/api/v2/outagesGet one service’s status by slug
curl -H "Authorization: Bearer sf_your_key" https://statusfield.com/api/v2/services/githubAsk Claude before you blame your deploy
Our checkout is timing out. Before I dig into the code, use Statusfield to check whether Stripe, AWS, or Cloudflare is currently having an outage.Claude calls list_outages and get_service_status, then answers from live data — no tab-switching, no guessing.
Available on the Hobby plan and up
API access isn’t part of the free plan. The same sf_ key powers both REST and MCP, and it activates once you’re on a paid plan. Each plan sets its own monthly request quota and burst rate limit — the current numbers are on the pricing page.
Simple, transparent pricing
Start for free. Upgrade when you need more monitors, integrations, or team members.
Common questions
What is MCP?
MCP (Model Context Protocol) is an open standard for connecting AI assistants to external tools and live data. Statusfield’s hosted MCP server gives Claude four read-only tools — search_services, get_service_status, list_outages, and list_my_down_services — so you can ask, in plain English, whether a service (or your own stack) is down and get an answer from live status data instead of the model’s training cutoff.
Is the API read-only?
Yes. Both the REST API and the MCP server only read status data. There are no write endpoints and no write tools — they can’t add monitors, change your account, or send notifications. That’s deliberate v1 scope: read-only is the safe default for a script or an AI agent, since a read call can’t misfire. If you need to manage monitors programmatically, that isn’t here yet — tell us and we’ll weigh it.
Which plans include the API and MCP server?
The Hobby plan and up. API access is not part of the free plan, and the same sf_ key powers both REST and MCP — it only activates once you’re on a paid plan. Each plan has its own monthly request quota and burst rate limit; the current numbers are on the pricing page and returned in the X-Quota and X-RateLimit response headers.
Do the MCP tools see my own monitors?
Yes. list_my_down_services reads your workspace’s own monitor list and reports which of your services are currently down or degraded — ask Claude "is anything I monitor down?" and that’s the tool it calls. The other three tools query the full public catalog by name or slug. Your complete monitor list, healthy ones included, is available over REST at GET /api/v2/monitors.
Put vendor status where your code already is
One key, two ways in: a read-only REST API and a hosted MCP server across 2,000+ services. Generate a key and paste one command.
Available on the Hobby plan and up