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

status-io-mcp

https://status-io.usefulapi.io

Registry code: 5fc7e2ef966194ef

api record

Tools for Status.io, hosted by usefulapi.io. Read-only tools never change data; ask the user before a tool that creates, changes or deletes Status.io data. Free plan: 100 tool calls per month. Run statusio_usage_status to see the calls used this month. If the user asks for something none of these tools can do, tell the user and, with their OK, run statusio_request_feature to record the request. Pro (unlimited calls, $9/month or $90/year): when the user wants more calls or reaches the limit, run statusio_upgrade; it returns a Stripe Checkout link for the user to open.…

endpoint
https://status-io.usefulapi.io/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is status-io-mcp live?
Yes — it answered the hub's last check (checked 11h ago). It answered 100% of checks over the last 30 days.
Is status-io-mcp free to use?
No — it asks for a key or a login before it will serve.
What tools does status-io-mcp have?
20 tools: statusio_get_incident, statusio_list_active_incidents, statusio_list_resolved_incidents, statusio_get_incident_message, statusio_get_status_summary, statusio_list_components, statusio_list_incidents, statusio_list_maintenance_ids, ….
Is status-io-mcp safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
278ms

last good check

priced tools
0

of 20 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 20 tools
20 auth-required 20 of 20 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.

  • statusio_get_incident auth-required never probed

    One incident in full: components, containers, infrastructure affected and all its messages. GET /incident/{statuspage_id}/{incident_id}.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "incident_id"
      ],
      "properties": {
        "incident_id": {
          "type": "string",
          "pattern": "^[A-Za-z0-9_-]{1,64}$",
          "description": "Incident id (from statusio_list_incidents or the active/resolved lists)."
        },
        "statuspage_id": {
          "type": "string",
          "pattern": "^[A-Za-z0-9_-]{1,64}$",
          "description": "Status page id. Defaults to the status page chosen when you connected."
        }
      }
    }
    arguments 19 lines
  • statusio_list_active_incidents auth-required 11h ago

    Active (unresolved) incidents with their messages and affected components. GET /incident/list/active/{statuspage_id}.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "page": {
          "type": "integer",
          "maximum": 100000,
          "description": "Page number, from 1 (default 1). Status.io reports no totals: ask for the next page until a page comes back empty.",
          "exclusiveMinimum": 0
        },
        "statuspage_id": {
          "type": "string",
          "pattern": "^[A-Za-z0-9_-]{1,64}$",
          "description": "Status page id. Defaults to the status page chosen when you connected."
        }
      }
    }
    arguments 17 lines
  • statusio_list_resolved_incidents auth-required never probed

    Resolved incidents (history) with their messages and affected components. GET /incident/list/resolved/{statuspage_id}.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "page": {
          "type": "integer",
          "maximum": 100000,
          "description": "Page number, from 1 (default 1). Status.io reports no totals: ask for the next page until a page comes back empty.",
          "exclusiveMinimum": 0
        },
        "statuspage_id": {
          "type": "string",
          "pattern": "^[A-Za-z0-9_-]{1,64}$",
          "description": "Status page id. Defaults to the status page chosen when you connected."
        }
      }
    }
    arguments 17 lines
  • statusio_get_incident_message auth-required never probed

    One message (update) of an incident: text, state, status, time and the user who posted it. GET /incident/message/{statuspage_id}/{message_id}.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "message_id"
      ],
      "properties": {
        "message_id": {
          "type": "string",
          "pattern": "^[A-Za-z0-9_-]{1,64}$",
          "description": "Incident message id (from statusio_get_incident)."
        },
        "statuspage_id": {
          "type": "string",
          "pattern": "^[A-Za-z0-9_-]{1,64}$",
          "description": "Status page id. Defaults to the status page chosen when you connected."
        }
      }
    }
    arguments 19 lines
  • statusio_get_status_summary auth-required 11h ago

    The current state of the status page in one call: overall status, every component and container with its status code and last update, open incidents and active/upcoming maintenance. Start here. GET /status/summary/{statuspage_id}.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "statuspage_id": {
          "type": "string",
          "pattern": "^[A-Za-z0-9_-]{1,64}$",
          "description": "Status page id. Defaults to the status page chosen when you connected."
        }
      }
    }
    arguments 11 lines
  • statusio_list_components auth-required 11h ago

    List the components of the status page and the containers (data centers / locations) attached to each, with ids. Component and container ids are needed to update a status or to say what an incident affects ('<component_id>-<container_id>'). GET /component/list/{statuspage_id}.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "statuspage_id": {
          "type": "string",
          "pattern": "^[A-Za-z0-9_-]{1,64}$",
          "description": "Status page id. Defaults to the status page chosen when you connected."
        }
      }
    }
    arguments 11 lines
  • statusio_list_incidents auth-required never probed

    The ids of all active and resolved incidents (ids only, no details): a quick way to see which incidents exist. Fetch one with statusio_get_incident. GET /incidents/{statuspage_id}.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "statuspage_id": {
          "type": "string",
          "pattern": "^[A-Za-z0-9_-]{1,64}$",
          "description": "Status page id. Defaults to the status page chosen when you connected."
        }
      }
    }
    arguments 11 lines
  • statusio_list_maintenance_ids auth-required never probed

    The ids of all active, closed and upcoming maintenance events (ids only). Fetch one with statusio_get_maintenance. GET /maintenances/{statuspage_id}.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "statuspage_id": {
          "type": "string",
          "pattern": "^[A-Za-z0-9_-]{1,64}$",
          "description": "Status page id. Defaults to the status page chosen when you connected."
        }
      }
    }
    arguments 11 lines
  • statusio_list_maintenance auth-required never probed

    Maintenance events in one state, with messages and affected components: pending (scheduled, not started), active (in progress) or closed (finished). GET /maintenance/list/{pending|active|closed}/{statuspage_id}.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "state"
      ],
      "properties": {
        "page": {
          "type": "integer",
          "maximum": 100000,
          "description": "Page number, from 1 (default 1). Status.io reports no totals: ask for the next page until a page comes back empty.",
          "exclusiveMinimum": 0
        },
        "state": {
          "enum": [
            "pending",
            "active",
            "closed"
          ],
          "type": "string",
          "description": "pending = scheduled and not started, active = in progress, closed = finished."
        },
        "statuspage_id": {
          "type": "string",
          "pattern": "^[A-Za-z0-9_-]{1,64}$",
          "description": "Status page id. Defaults to the status page chosen when you connected."
        }
      }
    }
    arguments 29 lines
  • statusio_get_maintenance auth-required never probed

    One maintenance event in full, with all messages and the infrastructure affected. GET /maintenance/{statuspage_id}/{maintenance_id}.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "maintenance_id"
      ],
      "properties": {
        "statuspage_id": {
          "type": "string",
          "pattern": "^[A-Za-z0-9_-]{1,64}$",
          "description": "Status page id. Defaults to the status page chosen when you connected."
        },
        "maintenance_id": {
          "type": "string",
          "pattern": "^[A-Za-z0-9_-]{1,64}$",
          "description": "Maintenance id (from statusio_list_maintenance_ids or statusio_list_maintenance)."
        }
      }
    }
    arguments 19 lines
  • statusio_get_maintenance_message auth-required never probed

    One message of a maintenance event. GET /maintenance/message/{statuspage_id}/{message_id}.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "message_id"
      ],
      "properties": {
        "message_id": {
          "type": "string",
          "pattern": "^[A-Za-z0-9_-]{1,64}$",
          "description": "Maintenance message id (from statusio_get_maintenance)."
        },
        "statuspage_id": {
          "type": "string",
          "pattern": "^[A-Za-z0-9_-]{1,64}$",
          "description": "Status page id. Defaults to the status page chosen when you connected."
        }
      }
    }
    arguments 19 lines
  • statusio_list_subscribers auth-required never probed

    List the people and endpoints subscribed to the status page (email addresses, phone numbers, webhook hosts) with ids and their granular preferences. This is personal data of your subscribers. Webhook URLs are shortened to their host, because they can carry secrets. GET /subscriber/list/{statuspage_id}.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "statuspage_id": {
          "type": "string",
          "pattern": "^[A-Za-z0-9_-]{1,64}$",
          "description": "Status page id. Defaults to the status page chosen when you connected."
        }
      }
    }
    arguments 11 lines
  • statusio_update_component_status auth-required never probed

    WRITE: change the PUBLIC status of one component/container pair (for example to degraded_performance) without creating an incident. It changes what visitors of your status page see right away. Set it back to operational when done. Ids from statusio_list_components. POST /component/status/update.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "component_id",
        "container_id",
        "status",
        "details"
      ],
      "properties": {
        "status": {
          "enum": [
            "operational",
            "planned_maintenance",
            "degraded_performance",
            "partial_service_disruption",
            "service_disruption",
            "security_issue"
          ],
          "type": "string",
          "description": "New status level."
        },
        "details": {
          "type": "string",
          "maxLength": 10000,
          "minLength": 1,
          "description": "Short message shown with the status change."
        },
        "component_id": {
          "type": "string",
          "pattern": "^[A-Za-z0-9_-]{1,64}$",
          "description": "Component id."
        },
        "container_id": {
          "type": "string",
          "pattern": "^[A-Za-z0-9_-]{1,64}$",
          "description": "Container id; it must be attached to that component."
        },
        "statuspage_id": {
          "type": "string",
          "pattern": "^[A-Za-z0-9_-]{1,64}$",
          "description": "Status page id. Defaults to the status page chosen when you connected."
        }
      }
    }
    arguments 45 lines
  • statusio_create_incident auth-required never probed

    WRITE: open a new incident on the PUBLIC status page. It is visible to every visitor immediately and sets the status of the affected components. No subscriber, Slack, Teams, IRC or Twitter notification is sent unless you switch it on (notify_*). Returns the new incident id. Say what is affected with all_infrastructure_affected or infrastructure_affected pairs. POST /incident/create.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "name",
        "details",
        "status"
      ],
      "properties": {
        "name": {
          "type": "string",
          "maxLength": 300,
          "minLength": 1,
          "description": "Short incident title."
        },
        "state": {
          "enum": [
            "investigating",
            "identified",
            "monitoring"
          ],
          "type": "string",
          "description": "Incident state (default investigating)."
        },
        "status": {
          "enum": [
            "operational",
            "degraded_performance",
            "partial_service_disruption",
            "service_disruption",
            "security_issue"
          ],
          "type": "string",
          "description": "Status the affected components get."
        },
        "details": {
          "type": "string",
          "maxLength": 10000,
          "minLength": 1,
          "description": "Message describing the incident."
        },
        "notify_irc": {
          "type": "boolean",
          "description": "Also post to your connected IRC channel (default false)."
        },
        "notify_sms": {
          "type": "boolean",
          "description": "Also text your SMS subscribers (default false)."
        },
        "notify_email": {
          "type": "boolean",
          "description": "Also email your email subscribers (default false)."
        },
        "notify_slack": {
          "type": "boolean",
          "description": "Also post to your connected Slack channels (default false)."
        },
        "statuspage_id": {
          "type": "string",
          "pattern": "^[A-Za-z0-9_-]{1,64}$",
          "description": "Status page id. Defaults to the status page chosen when you connected."
        },
        "notify_msteams": {
          "type": "boolean",
          "description": "Also post to your connected Microsoft Teams channels (default false)."
        },
        "notify_webhook": {
          "type": "boolean",
          "description": "Also call your webhook subscribers (default false)."
        },
        "message_subject": {
          "type": "string",
          "maxLength": 300,
          "minLength": 1,
          "description": "Subject line for the email notification."
        },
        "post_to_twitter": {
          "type": "boolean",
          "description": "Also post to your connected Twitter/X account (default false)."
        },
        "infrastructure_affected": {
          "type": "array",
          "items": {
            "type": "string",
            "pattern": "^[A-Za-z0-9_]+-[A-Za-z0-9_]+$",
            "maxLength": 140
          },
          "maxItems": 200,
          "description": "Affected pairs, each '<component_id>-<container_id>' (ids from statusio_list_components)."
        },
        "all_infrastructure_affected": {
          "type": "boolean",
          "description": "true = every component and container is affected. Otherwise give infrastructure_affected."
        }
      }
    }
    arguments 96 lines
  • statusio_update_incident auth-required never probed

    WRITE: post a new update message on an existing incident and set its state and component status. The message is public at once. No subscriber or channel notification is sent unless you switch it on (notify_*). To close an incident use statusio_resolve_incident. POST /incident/update.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "incident_id",
        "details",
        "status",
        "state"
      ],
      "properties": {
        "state": {
          "enum": [
            "investigating",
            "identified",
            "monitoring"
          ],
          "type": "string",
          "description": "Incident state now."
        },
        "status": {
          "enum": [
            "operational",
            "degraded_performance",
            "partial_service_disruption",
            "service_disruption",
            "security_issue"
          ],
          "type": "string",
          "description": "Status the affected components get now."
        },
        "details": {
          "type": "string",
          "maxLength": 10000,
          "minLength": 1,
          "description": "Message describing this update."
        },
        "notify_irc": {
          "type": "boolean",
          "description": "Also post to your connected IRC channel (default false)."
        },
        "notify_sms": {
          "type": "boolean",
          "description": "Also text your SMS subscribers (default false)."
        },
        "incident_id": {
          "type": "string",
          "pattern": "^[A-Za-z0-9_-]{1,64}$",
          "description": "Incident id."
        },
        "notify_email": {
          "type": "boolean",
          "description": "Also email your email subscribers (default false)."
        },
        "notify_slack": {
          "type": "boolean",
          "description": "Also post to your connected Slack channels (default false)."
        },
        "statuspage_id": {
          "type": "string",
          "pattern": "^[A-Za-z0-9_-]{1,64}$",
          "description": "Status page id. Defaults to the status page chosen when you connected."
        },
        "notify_msteams": {
          "type": "boolean",
          "description": "Also post to your connected Microsoft Teams channels (default false)."
        },
        "notify_webhook": {
          "type": "boolean",
          "description": "Also call your webhook subscribers (default false)."
        },
        "message_subject": {
          "type": "string",
          "maxLength": 300,
          "minLength": 1,
          "description": "Subject line for the email notification."
        },
        "post_to_twitter": {
          "type": "boolean",
          "description": "Also post to your connected Twitter/X account (default false)."
        }
      }
    }
    arguments 82 lines
  • statusio_resolve_incident auth-required never probed

    WRITE: resolve an incident with a closing message. The affected components return to operational and the incident moves to history. No notification is sent unless you switch it on (notify_*). POST /incident/resolve.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "incident_id",
        "details"
      ],
      "properties": {
        "details": {
          "type": "string",
          "maxLength": 10000,
          "minLength": 1,
          "description": "Message describing the resolution."
        },
        "notify_irc": {
          "type": "boolean",
          "description": "Also post to your connected IRC channel (default false)."
        },
        "notify_sms": {
          "type": "boolean",
          "description": "Also text your SMS subscribers (default false)."
        },
        "incident_id": {
          "type": "string",
          "pattern": "^[A-Za-z0-9_-]{1,64}$",
          "description": "Incident id."
        },
        "notify_email": {
          "type": "boolean",
          "description": "Also email your email subscribers (default false)."
        },
        "notify_slack": {
          "type": "boolean",
          "description": "Also post to your connected Slack channels (default false)."
        },
        "statuspage_id": {
          "type": "string",
          "pattern": "^[A-Za-z0-9_-]{1,64}$",
          "description": "Status page id. Defaults to the status page chosen when you connected."
        },
        "notify_msteams": {
          "type": "boolean",
          "description": "Also post to your connected Microsoft Teams channels (default false)."
        },
        "notify_webhook": {
          "type": "boolean",
          "description": "Also call your webhook subscribers (default false)."
        },
        "message_subject": {
          "type": "string",
          "maxLength": 300,
          "minLength": 1,
          "description": "Subject line for the email notification."
        },
        "post_to_twitter": {
          "type": "boolean",
          "description": "Also post to your connected Twitter/X account (default false)."
        }
      }
    }
    arguments 60 lines
  • statusio_schedule_maintenance auth-required never probed

    WRITE: schedule a planned maintenance on the PUBLIC status page. It is visible to visitors as upcoming maintenance. Subscribers are told only if you switch on notify_now / notify_72_hr / notify_24_hr / notify_1_hr (all default off). With automation true Status.io starts and ends it by itself at the planned times. Returns the maintenance id. POST /maintenance/schedule.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "name",
        "details",
        "start",
        "end"
      ],
      "properties": {
        "end": {
          "type": "string",
          "description": "Planned end, 'YYYY-MM-DD HH:mm' (24-hour); after the start."
        },
        "name": {
          "type": "string",
          "maxLength": 300,
          "minLength": 1,
          "description": "Short maintenance title."
        },
        "start": {
          "type": "string",
          "description": "Planned start, 'YYYY-MM-DD HH:mm' (24-hour). Status.io's reference does not state the time zone of this input: check the scheduled time in your dashboard."
        },
        "details": {
          "type": "string",
          "maxLength": 10000,
          "minLength": 1,
          "description": "Message describing the maintenance."
        },
        "automation": {
          "type": "boolean",
          "description": "Start and end the maintenance automatically at the planned times (default false)."
        },
        "notify_now": {
          "type": "boolean",
          "description": "Tell subscribers right away (default false)."
        },
        "notify_1_hr": {
          "type": "boolean",
          "description": "Remind subscribers 1 hour before the start (default false)."
        },
        "notify_24_hr": {
          "type": "boolean",
          "description": "Remind subscribers 24 hours before the start (default false)."
        },
        "notify_72_hr": {
          "type": "boolean",
          "description": "Remind subscribers 72 hours before the start (default false)."
        },
        "statuspage_id": {
          "type": "string",
          "pattern": "^[A-Za-z0-9_-]{1,64}$",
          "description": "Status page id. Defaults to the status page chosen when you connected."
        },
        "message_subject": {
          "type": "string",
          "maxLength": 300,
          "minLength": 1,
          "description": "Subject line for the email notifications."
        },
        "automation_stop_text": {
          "type": "string",
          "maxLength": 10000,
          "minLength": 1,
          "description": "Message posted when the maintenance ends (with automation)."
        },
        "automation_start_text": {
          "type": "string",
          "maxLength": 10000,
          "minLength": 1,
          "description": "Message posted when the maintenance starts (with automation)."
        },
        "infrastructure_affected": {
          "type": "array",
          "items": {
            "type": "string",
            "pattern": "^[A-Za-z0-9_]+-[A-Za-z0-9_]+$",
            "maxLength": 140
          },
          "maxItems": 200,
          "description": "Affected pairs, each '<component_id>-<container_id>' (ids from statusio_list_components)."
        },
        "all_infrastructure_affected": {
          "type": "boolean",
          "description": "true = every component and container is affected. Otherwise give infrastructure_affected."
        }
      }
    }
    arguments 89 lines
  • statusio_start_maintenance auth-required never probed

    WRITE: start a scheduled maintenance now; it moves from pending to active and the affected components show planned maintenance. The message is public at once. No notification is sent unless you switch it on (notify_*). POST /maintenance/start.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "maintenance_id",
        "details"
      ],
      "properties": {
        "details": {
          "type": "string",
          "maxLength": 10000,
          "minLength": 1,
          "description": "Message describing this maintenance update."
        },
        "notify_irc": {
          "type": "boolean",
          "description": "Also post to your connected IRC channel (default false)."
        },
        "notify_sms": {
          "type": "boolean",
          "description": "Also text your SMS subscribers (default false)."
        },
        "notify_email": {
          "type": "boolean",
          "description": "Also email your email subscribers (default false)."
        },
        "notify_slack": {
          "type": "boolean",
          "description": "Also post to your connected Slack channels (default false)."
        },
        "statuspage_id": {
          "type": "string",
          "pattern": "^[A-Za-z0-9_-]{1,64}$",
          "description": "Status page id. Defaults to the status page chosen when you connected."
        },
        "maintenance_id": {
          "type": "string",
          "pattern": "^[A-Za-z0-9_-]{1,64}$",
          "description": "Maintenance id."
        },
        "notify_msteams": {
          "type": "boolean",
          "description": "Also post to your connected Microsoft Teams channels (default false)."
        },
        "notify_webhook": {
          "type": "boolean",
          "description": "Also call your webhook subscribers (default false)."
        },
        "message_subject": {
          "type": "string",
          "maxLength": 300,
          "minLength": 1,
          "description": "Subject line for the email notification."
        },
        "post_to_twitter": {
          "type": "boolean",
          "description": "Also post to your connected Twitter/X account (default false)."
        }
      }
    }
    arguments 60 lines
  • statusio_update_maintenance auth-required never probed

    WRITE: post a new status message on an active maintenance event. The message is public at once. No notification is sent unless you switch it on (notify_*). POST /maintenance/update.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "maintenance_id",
        "details"
      ],
      "properties": {
        "details": {
          "type": "string",
          "maxLength": 10000,
          "minLength": 1,
          "description": "Message describing this maintenance update."
        },
        "notify_irc": {
          "type": "boolean",
          "description": "Also post to your connected IRC channel (default false)."
        },
        "notify_sms": {
          "type": "boolean",
          "description": "Also text your SMS subscribers (default false)."
        },
        "notify_email": {
          "type": "boolean",
          "description": "Also email your email subscribers (default false)."
        },
        "notify_slack": {
          "type": "boolean",
          "description": "Also post to your connected Slack channels (default false)."
        },
        "statuspage_id": {
          "type": "string",
          "pattern": "^[A-Za-z0-9_-]{1,64}$",
          "description": "Status page id. Defaults to the status page chosen when you connected."
        },
        "maintenance_id": {
          "type": "string",
          "pattern": "^[A-Za-z0-9_-]{1,64}$",
          "description": "Maintenance id."
        },
        "notify_msteams": {
          "type": "boolean",
          "description": "Also post to your connected Microsoft Teams channels (default false)."
        },
        "notify_webhook": {
          "type": "boolean",
          "description": "Also call your webhook subscribers (default false)."
        },
        "message_subject": {
          "type": "string",
          "maxLength": 300,
          "minLength": 1,
          "description": "Subject line for the email notification."
        },
        "post_to_twitter": {
          "type": "boolean",
          "description": "Also post to your connected Twitter/X account (default false)."
        }
      }
    }
    arguments 60 lines
  • statusio_finish_maintenance auth-required never probed

    WRITE: finish an active maintenance event; it moves to history and the affected components return to operational. The message is public at once. No notification is sent unless you switch it on (notify_*). POST /maintenance/finish.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "maintenance_id",
        "details"
      ],
      "properties": {
        "details": {
          "type": "string",
          "maxLength": 10000,
          "minLength": 1,
          "description": "Message describing this maintenance update."
        },
        "notify_irc": {
          "type": "boolean",
          "description": "Also post to your connected IRC channel (default false)."
        },
        "notify_sms": {
          "type": "boolean",
          "description": "Also text your SMS subscribers (default false)."
        },
        "notify_email": {
          "type": "boolean",
          "description": "Also email your email subscribers (default false)."
        },
        "notify_slack": {
          "type": "boolean",
          "description": "Also post to your connected Slack channels (default false)."
        },
        "statuspage_id": {
          "type": "string",
          "pattern": "^[A-Za-z0-9_-]{1,64}$",
          "description": "Status page id. Defaults to the status page chosen when you connected."
        },
        "maintenance_id": {
          "type": "string",
          "pattern": "^[A-Za-z0-9_-]{1,64}$",
          "description": "Maintenance id."
        },
        "notify_msteams": {
          "type": "boolean",
          "description": "Also post to your connected Microsoft Teams channels (default false)."
        },
        "notify_webhook": {
          "type": "boolean",
          "description": "Also call your webhook subscribers (default false)."
        },
        "message_subject": {
          "type": "string",
          "maxLength": 300,
          "minLength": 1,
          "description": "Subject line for the email notification."
        },
        "post_to_twitter": {
          "type": "boolean",
          "description": "Also post to your connected Twitter/X account (default false)."
        }
      }
    }
    arguments 60 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.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 5fc7e2ef966194ef.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/5fc7e2ef966194ef/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/5fc7e2ef966194ef/badge.svg)](https://brick.blue/agent/5fc7e2ef966194ef?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ 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
0

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 131 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.

123 more sit on this domain. All of them.