For developers · REST API & MCP

Your monitored services.
In scripts and AI tools.

  • Bring recorded vendor status into scripts and internal tools.
  • Connect AI assistants through MCP.
  • Use one workspace API key for both.

Read-only access · Starter, Pro and Team · Workspace plan limits apply

Statusfield for developers

Example request

curl --request GET \
  'https://statusfield.com/api/v2/services/github' \
  --header 'Authorization: Bearer sf_your_key'

Your workspace must actively monitor GitHub. Otherwise this endpoint returns 403 service_not_monitored.

Illustrative response · abbreviated

200 OK
{
  "data": {
    "name": "GitHub",
    "slug": "github",
    "statusCode": "OPERATIONAL",
    "status": "Operational",
    "components": [
      {
        "name": "GitHub Actions",
        "statusCode": "OPERATIONAL",
        "status": "Operational"
      }
    ]
  }
}

Interactive examples only. No live requests are made, and no API key is needed to explore them.

REST API v2

Read catalog metadata, monitored vendor status and workspace monitors over HTTPS.

Hosted MCP

Connect your AI assistant to three read-only tools. Statusfield hosts the server.

One workspace key

Use one key for REST and MCP, scoped to your workspace and its plan.

Vendor status for your investigation.

Add monitoring context to a runbook, internal dashboard or assistant conversation. Start with the interface that fits how you work.

Search 7,000+ catalog services. Status lookups are limited to services your workspace actively monitors.

Look up a dependency while debugging

Read vendor-reported status and component updates alongside your application telemetry. A vendor incident is context to investigate, not proof of a root cause.

Build a view around your own monitors

List workspace monitors through REST, including custom monitors, or filter for non-operational states. MCP can list your affected monitors too.

Choose your interface

From an example to your first connection.

Use the full guides for authentication, request shapes, client setup and error handling.

Connect once.
Keep access scoped.

API keys belong to the workspace that creates them. Both interfaces read data; they cannot add monitors, change settings or send notifications.

Open API key settings
  1. 1

    Create a workspace key

    On Starter or higher, open Integrations → API Keys. Copy the key when it is created; it is shown only once. You can revoke it from the same screen.

  2. 2

    Connect your tool

    For REST, send the key as a Bearer token. For MCP, configure a remote Streamable HTTP connection to https://statusfield.com/api/mcp with the Authorization header. Keep the key out of prompts and shared files.

  3. 3

    Read within your plan limits

    Use the response headers to track rate limits and monthly quota. On 429 responses, follow Retry-After or X-Quota-Reset as appropriate.

Available on Starter and up.

REST and MCP are included on Starter, Pro and Team, including eligible trials. Basic does not include API or MCP access.

Limits are shared within the workspace. REST requests and MCP tool calls count toward its monthly quota; MCP initialization and tool discovery do not.

See plans and limits

Frequently Asked Questions

Authentication, workspace access and API usage.

What is MCP?
Model Context Protocol (MCP) connects AI assistants to tools and data. Statusfield’s server lets an assistant search the catalog and check the status of your monitored services.
Is the API read-only?
Yes. The REST API and MCP server read recorded status data. They cannot add monitors, change your account, or send notifications.
Which plans include the API and MCP server?
Starter and higher plans, including eligible trials. One API key works for REST and MCP. Request limits depend on your plan; see pricing or the response headers.
Do the MCP tools see my own monitors?
Yes. Use list_my_down_services to find your monitors reporting problems. For your full monitor list, use GET /api/v2/monitors through REST.
Can I read status for any service in the catalog?
Catalog search returns service metadata. Recorded service status requires an active monitor in the API key’s workspace. A REST lookup for an unmonitored service returns 403 service_not_monitored.
Does asking the assistant run a fresh check or diagnose an outage?
No. The tools read status already recorded by Statusfield. A vendor incident can help guide an investigation, but it does not prove why your application failed. An empty problem list is not a test of your whole application or approval to deploy.
How do rate limits and monthly quotas work?
Limits follow the workspace plan. REST requests count toward its monthly quota; for MCP, tools/call is metered while initialize and tools/list are not. Read the X-RateLimit-* and X-Quota-* response headers. Honor Retry-After on a rate limit and X-Quota-Reset when a monthly quota is exhausted.
I have more questions. Where can I get more information?
Email support@statusfield.com with your questions. We can help you understand component coverage, routing rules, integrations, and which plan fits your team.

Still have questions? Email us at support@statusfield.com or set up a meeting. All emails are read by humans.

Keep your workflow connected

Need updates delivered to you?

Use alerts when your team needs a notification, or RSS when a feed fits the way you follow updates.

Bring monitoring context into your next tool.

Create a workspace key, then start with a read-only request.

Get your API key