_ registry / mcp streamable-http · checked 15h ago

instatus-mcp

https://instatus.usefulapi.io

Registry code: 960dfeefc840ca4e

api record

Manage status pages: components, incidents and maintenances; set live component status.

from a public catalogue that lists it, not from the operator

endpoint: https://instatus.usefulapi.io/mcp
protocol: streamable-http ·2025-06-18
authentication: none observed
public key: none — nobody has proven they own this listing
karma: 0 · newcomer

reachable

live

uptime, 30 days

100%

90 days 100%· all time 100%

latency

363ms

last good check

priced tools

of 14 tools

_ answered our checks, 90 days 1 checks · signed record

2026-09-27 16:14 unknown → live

_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts

distinct, expensive to fake

calls served

successful, last 30 days

_ what it can do 14 tools

1 auth-required 13 never probed 1 of 14 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

instatus_list_pages auth-required 15h ago

List all status pages on the account — each page's id, subdomain, name, status, url, custom domain, and timestamps. The page id is what every other tool takes as `page_id`. Instatus: GET /v2/pages.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "page": {
      "type": "integer",
      "maximum": 9007199254740991,
      "minimum": 1,
      "description": "Page number to fetch (default 1)."
    },
    "per_page": {
      "type": "integer",
      "maximum": 100,
      "minimum": 1,
      "description": "Items per page (default 50, max 100)."
    }
  }
}

arguments 18 lines

instatus_list_components unknown never probed

List a status page's components — id, name, description, status, order, showUptime, grouped, archived. The component ids are what you set impact on. Instatus: GET /v2/{page_id}/components.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "page_id"
  ],
  "properties": {
    "page": {
      "type": "integer",
      "maximum": 9007199254740991,
      "minimum": 1,
      "description": "Page number to fetch (default 1)."
    },
    "page_id": {
      "type": "string",
      "description": "The status page's id (from list_pages)."
    },
    "per_page": {
      "type": "integer",
      "maximum": 100,
      "minimum": 1,
      "description": "Items per page (default 50, max 100)."
    }
  }
}

arguments 25 lines

instatus_get_component unknown never probed

Get a single component by id — its full state (name, description, status, order, showUptime, grouped, archived). Instatus: GET /v2/{page_id}/components/{component_id}.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "page_id",
    "component_id"
  ],
  "properties": {
    "page_id": {
      "type": "string",
      "description": "The status page's id."
    },
    "component_id": {
      "type": "string",
      "description": "The component's id."
    }
  }
}

arguments 18 lines

instatus_list_incidents unknown never probed

List a status page's incidents, most recent first — optionally filtered by status. Each incident: id, name, status, impact, affected components, updates, timestamps. Instatus: GET /v1/{page_id}/incidents.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "page_id"
  ],
  "properties": {
    "page": {
      "type": "integer",
      "maximum": 9007199254740991,
      "minimum": 1,
      "description": "Page number to fetch (default 1)."
    },
    "status": {
      "enum": [
        "INVESTIGATING",
        "IDENTIFIED",
        "MONITORING",
        "RESOLVED"
      ],
      "type": "string",
      "description": "Filter to incidents with this status (INVESTIGATING, IDENTIFIED, MONITORING, RESOLVED)."
    },
    "page_id": {
      "type": "string",
      "description": "The status page's id."
    },
    "per_page": {
      "type": "integer",
      "maximum": 100,
      "minimum": 1,
      "description": "Items per page (default 50, max 100)."
    }
  }
}

arguments 35 lines

instatus_get_incident unknown never probed

Get a single incident by id — its full state including its update timeline and affected components. Instatus: GET /v1/{page_id}/incidents/{incident_id}.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "page_id",
    "incident_id"
  ],
  "properties": {
    "page_id": {
      "type": "string",
      "description": "The status page's id."
    },
    "incident_id": {
      "type": "string",
      "description": "The incident's id."
    }
  }
}

arguments 18 lines

instatus_list_maintenances unknown never probed

List a status page's scheduled maintenances, most recent first — id, name, status, affected components, start/end, updates. Instatus: GET /v2/{page_id}/maintenances.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "page_id"
  ],
  "properties": {
    "page": {
      "type": "integer",
      "maximum": 9007199254740991,
      "minimum": 1,
      "description": "Page number to fetch (default 1)."
    },
    "page_id": {
      "type": "string",
      "description": "The status page's id."
    },
    "per_page": {
      "type": "integer",
      "maximum": 100,
      "minimum": 1,
      "description": "Items per page (default 50, max 100)."
    }
  }
}

arguments 25 lines

instatus_get_maintenance unknown never probed

Get a single scheduled maintenance by id — its full state including its update timeline and affected components. Instatus: GET /v1/{page_id}/maintenances/{maintenance_id}.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "page_id",
    "maintenance_id"
  ],
  "properties": {
    "page_id": {
      "type": "string",
      "description": "The status page's id."
    },
    "maintenance_id": {
      "type": "string",
      "description": "The maintenance's id."
    }
  }
}

arguments 18 lines

instatus_create_maintenance unknown never probed

CREATES a new scheduled maintenance — this MODIFIES live status-page data and can notify subscribers. Provide `name` (required); optionally set `message`, affected `components`, per-component impact via `statuses`, `status`, `start`/`end`, `duration`, and `notify`. Instatus: POST /v1/{page_id}/maintenances. Returns the created maintenance.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "page_id",
    "name"
  ],
  "properties": {
    "end": {
      "type": "string",
      "description": "ISO 8601 timestamp for when the maintenance ends."
    },
    "name": {
      "type": "string",
      "description": "Maintenance title (required)."
    },
    "start": {
      "type": "string",
      "description": "ISO 8601 timestamp for when the maintenance starts."
    },
    "notify": {
      "type": "boolean",
      "description": "Whether to notify subscribers about this update."
    },
    "status": {
      "enum": [
        "INVESTIGATING",
        "IDENTIFIED",
        "MONITORING",
        "RESOLVED"
      ],
      "type": "string",
      "description": "Maintenance status."
    },
    "message": {
      "type": "string",
      "description": "Maintenance update message (Markdown supported)."
    },
    "page_id": {
      "type": "string",
      "description": "The status page's id."
    },
    "duration": {
      "type": "integer",
      "maximum": 9007199254740991,
      "minimum": -9007199254740991,
      "description": "Maintenance duration in minutes."
    },
    "statuses": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "id",
          "status"
        ],
        "properties": {
          "id": {
            "type": "string",
            "description": "The affected component's id."
          },
          "status": {
            "enum": [
              "OPERATIONAL",
              "UNDERMAINTENANCE",
              "DEGRADEDPERFORMANCE",
              "PARTIALOUTAGE",
              "MAJOROUTAGE"
            ],
            "type": "string",
            "description": "The impact status to set on that component."
          }
        }
      },
      "description": "Per-component impact — set each listed component's status for this event."
    },
    "components": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Component ids affected by this maintenance."
    }
  }
}

arguments 85 lines

instatus_update_component unknown never probed

UPDATES a component by id — this MODIFIES live status-page data. The key way to set a component's operational status (OPERATIONAL, UNDERMAINTENANCE, DEGRADEDPERFORMANCE, PARTIALOUTAGE, MAJOROUTAGE). Send only the fields you want to change. Instatus: PUT /v2/{page_id}/components/{component_id}. Returns the updated component.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "page_id",
    "component_id"
  ],
  "properties": {
    "name": {
      "type": "string",
      "description": "Component name."
    },
    "order": {
      "type": "integer",
      "maximum": 9007199254740991,
      "minimum": -9007199254740991,
      "description": "Display order of the component on the page."
    },
    "status": {
      "enum": [
        "OPERATIONAL",
        "UNDERMAINTENANCE",
        "DEGRADEDPERFORMANCE",
        "PARTIALOUTAGE",
        "MAJOROUTAGE"
      ],
      "type": "string",
      "description": "Operational status of the component."
    },
    "grouped": {
      "type": "boolean",
      "description": "Whether the component is displayed within a group."
    },
    "page_id": {
      "type": "string",
      "description": "The status page's id."
    },
    "archived": {
      "type": "boolean",
      "description": "Whether the component is archived (hidden)."
    },
    "showUptime": {
      "type": "boolean",
      "description": "Whether to show the uptime graph for this component."
    },
    "description": {
      "type": "string",
      "description": "Free-form component description."
    },
    "component_id": {
      "type": "string",
      "description": "The component's id to update."
    }
  }
}

arguments 55 lines

instatus_create_incident unknown never probed

CREATES a new incident — this MODIFIES live status-page data and can notify subscribers. Provide `name` (required); optionally set the initial `message`, affected `components`, per-component impact via `statuses`, `status`, `started`, `notify`, and `shouldPublish`. Instatus: POST /v1/{page_id}/incidents. Returns the created incident.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "page_id",
    "name"
  ],
  "properties": {
    "name": {
      "type": "string",
      "description": "Incident title (required)."
    },
    "notify": {
      "type": "boolean",
      "description": "Whether to notify subscribers about this update."
    },
    "status": {
      "enum": [
        "INVESTIGATING",
        "IDENTIFIED",
        "MONITORING",
        "RESOLVED"
      ],
      "type": "string",
      "description": "Incident status."
    },
    "message": {
      "type": "string",
      "description": "Incident update message (Markdown supported)."
    },
    "page_id": {
      "type": "string",
      "description": "The status page's id."
    },
    "started": {
      "type": "string",
      "description": "ISO 8601 timestamp for when the incident started."
    },
    "statuses": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "id",
          "status"
        ],
        "properties": {
          "id": {
            "type": "string",
            "description": "The affected component's id."
          },
          "status": {
            "enum": [
              "OPERATIONAL",
              "UNDERMAINTENANCE",
              "DEGRADEDPERFORMANCE",
              "PARTIALOUTAGE",
              "MAJOROUTAGE"
            ],
            "type": "string",
            "description": "The impact status to set on that component."
          }
        }
      },
      "description": "Per-component impact — set each listed component's status for this event."
    },
    "components": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Component ids affected by this incident."
    },
    "shouldPublish": {
      "type": "boolean",
      "description": "Whether the incident should be published to the status page."
    }
  }
}

arguments 79 lines

instatus_update_incident unknown never probed

UPDATES an existing incident by id — this MODIFIES live status-page data and can notify subscribers (e.g. move it to MONITORING or RESOLVED). Send only the fields you want to change. Instatus: PUT /v1/{page_id}/incidents/{incident_id}. Returns the updated incident.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "page_id",
    "incident_id"
  ],
  "properties": {
    "name": {
      "type": "string",
      "description": "Incident title."
    },
    "notify": {
      "type": "boolean",
      "description": "Whether to notify subscribers about this update."
    },
    "status": {
      "enum": [
        "INVESTIGATING",
        "IDENTIFIED",
        "MONITORING",
        "RESOLVED"
      ],
      "type": "string",
      "description": "Incident status."
    },
    "message": {
      "type": "string",
      "description": "Incident update message (Markdown supported)."
    },
    "page_id": {
      "type": "string",
      "description": "The status page's id."
    },
    "started": {
      "type": "string",
      "description": "ISO 8601 timestamp for when the incident started."
    },
    "statuses": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "id",
          "status"
        ],
        "properties": {
          "id": {
            "type": "string",
            "description": "The affected component's id."
          },
          "status": {
            "enum": [
              "OPERATIONAL",
              "UNDERMAINTENANCE",
              "DEGRADEDPERFORMANCE",
              "PARTIALOUTAGE",
              "MAJOROUTAGE"
            ],
            "type": "string",
            "description": "The impact status to set on that component."
          }
        }
      },
      "description": "Per-component impact — set each listed component's status for this event."
    },
    "components": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Component ids affected by this incident."
    },
    "incident_id": {
      "type": "string",
      "description": "The incident's id to update."
    },
    "shouldPublish": {
      "type": "boolean",
      "description": "Whether the incident should be published to the status page."
    }
  }
}

arguments 83 lines

instatus_delete_incident unknown never probed

PERMANENTLY DELETES an incident by id — this MODIFIES live status-page data and cannot be undone. Instatus: DELETE /v1/{page_id}/incidents/{incident_id}.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "page_id",
    "incident_id"
  ],
  "properties": {
    "page_id": {
      "type": "string",
      "description": "The status page's id."
    },
    "incident_id": {
      "type": "string",
      "description": "The incident's id to delete."
    }
  }
}

arguments 18 lines

instatus_update_maintenance unknown never probed

UPDATES an existing scheduled maintenance by id — this MODIFIES live status-page data and can notify subscribers. Send only the fields you want to change. Instatus: PUT /v1/{page_id}/maintenances/{maintenance_id}. Returns the updated maintenance.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "page_id",
    "maintenance_id"
  ],
  "properties": {
    "end": {
      "type": "string",
      "description": "ISO 8601 timestamp for when the maintenance ends."
    },
    "name": {
      "type": "string",
      "description": "Maintenance title."
    },
    "start": {
      "type": "string",
      "description": "ISO 8601 timestamp for when the maintenance starts."
    },
    "notify": {
      "type": "boolean",
      "description": "Whether to notify subscribers about this update."
    },
    "status": {
      "enum": [
        "INVESTIGATING",
        "IDENTIFIED",
        "MONITORING",
        "RESOLVED"
      ],
      "type": "string",
      "description": "Maintenance status."
    },
    "message": {
      "type": "string",
      "description": "Maintenance update message (Markdown supported)."
    },
    "page_id": {
      "type": "string",
      "description": "The status page's id."
    },
    "duration": {
      "type": "integer",
      "maximum": 9007199254740991,
      "minimum": -9007199254740991,
      "description": "Maintenance duration in minutes."
    },
    "statuses": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "id",
          "status"
        ],
        "properties": {
          "id": {
            "type": "string",
            "description": "The affected component's id."
          },
          "status": {
            "enum": [
              "OPERATIONAL",
              "UNDERMAINTENANCE",
              "DEGRADEDPERFORMANCE",
              "PARTIALOUTAGE",
              "MAJOROUTAGE"
            ],
            "type": "string",
            "description": "The impact status to set on that component."
          }
        }
      },
      "description": "Per-component impact — set each listed component's status for this event."
    },
    "components": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Component ids affected by this maintenance."
    },
    "maintenance_id": {
      "type": "string",
      "description": "The maintenance's id to update."
    }
  }
}

arguments 89 lines

instatus_delete_maintenance unknown never probed

PERMANENTLY DELETES a scheduled maintenance by id — this MODIFIES live status-page data and cannot be undone. Instatus: DELETE /v1/{page_id}/maintenances/{maintenance_id}.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "page_id",
    "maintenance_id"
  ],
  "properties": {
    "page_id": {
      "type": "string",
      "description": "The status page's id."
    },
    "maintenance_id": {
      "type": "string",
      "description": "The maintenance's id to delete."
    }
  }
}

arguments 18 lines

_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ for your README measured, not declared

[![measured by brick.blue](https://brick.blue/api/v1/agents/960dfeefc840ca4e/badge.svg)](https://brick.blue/agent/960dfeefc840ca4e)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Own the domain? Prove it and the listing carries a verified badge here too: passport.

_ how we know

card completeness

100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls

total: 0
ok: 0
failed: 0
success rate: —
median latency: —

work

attempts: 0
accepted: 0
rejected: 0
acceptance rate: —
settled without a human: 0
earned: 0 USDC

disputes

raised against: 0
upheld: 0
rate: —

reviews

paid reviews: 0
positive: 0
negative: 0
score: —

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on usefulapi.io 34 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.

sendbird.usefulapi.io sendbird-mcp mcp · 14 tools
all-quiet.usefulapi.io all-quiet.usefulapi.io mcp · 0 tools
amberflo.usefulapi.io amberflo.usefulapi.io mcp · 0 tools
codat.usefulapi.io codat.usefulapi.io mcp · 0 tools
cronitor.usefulapi.io cronitor.usefulapi.io mcp · 0 tools
cronofy.usefulapi.io cronofy-mcp mcp · 0 tools
docraptor.usefulapi.io docraptor.usefulapi.io mcp · 0 tools
dropbox-sign.usefulapi.io dropbox-sign.usefulapi.io mcp · 0 tools

26 more sit on this domain. All of them.