Skip to content

API Status Check MCP server

io.github.shibley/apistatuscheckshibleystreamable-httpv0.2.3Scanned

Live status probes plus published uptime and incident history for 280+ APIs and cloud services.

8 tools: 1 change things and 7 only read.

Tools: 0 delete, 0 irreversible, 1 write, 7 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here changes things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the API Status Check MCP server can do

The API Status Check MCP server is published by the GitHub account shibley. It has 8 tools. It can create or change data (1 tool: rank_reliability), but cannot delete data. 7 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 20, 2026, version 0.2.3.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

8 tools

Changes things 1Claude Code: ask
  • rank_reliabilityGiven several service slugs, return a scorecard ranked worst-first: incident count, total downtime minutes, mean time to resolve, and the longest incident over a window.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Given several service slugs, return a scorecard ranked worst-first: incident count, total downtime minutes, mean time to resolve, and the longest incident over a window. Use this to answer "which vendor in my stack is least reliable?" — it compares services across vendors, which a vendor’s own monitoring tool cannot. Services with no archive are listed separately as uncovered instead of being ranked as flawless.
Only reads 7Show 7 read-only tools
  • get_api_statusProbe a monitored API endpoint at call time and return up/degraded/down with the response time.No findings

    Why it is in this group

    • The name "get_api_status" says "get": a word for reading.
    Description, as the server wrote it
    Probe a monitored API endpoint at call time and return up/degraded/down with the response time. This is the tool to reach for when a user asks "is X down?" — it makes a real request rather than reading the hourly cache.
  • get_incident_historyReal incidents a vendor published on its own status page, newest first, with start/end times, duration, severity, affected components and a link to the vendor’s incident page.No findings

    Why it is in this group

    • The name "get_incident_history" says "get": a word for reading.
    Description, as the server wrote it
    Real incidents a vendor published on its own status page, newest first, with start/end times, duration, severity, affected components and a link to the vendor’s incident page. Use this for "has X been flaky lately?" — it is the vendor’s own record, not our probes. Services without a public Statuspage endpoint return covered:false rather than an empty list.
  • get_uptime_historyUptime percentages, response-time stats and recorded data points for one API over a time range.No findings

    Why it is in this group

    • The name "get_uptime_history" says "get": a word for reading.
    Description, as the server wrote it
    Uptime percentages, response-time stats and recorded data points for one API over a time range. History is retained for 30 days; an API added recently will have few or no data points, which reads as null percentages rather than 100%.
  • list_apisList the APIs and developer platforms this service monitors, optionally filtered by category.No findings

    Why it is in this group

    • The name "list_apis" says "list": a word for reading.
    Description, as the server wrote it
    List the APIs and developer platforms this service monitors, optionally filtered by category. Statuses come from the most recently published monitor snapshot, not a live probe, and can be up to a day old — check monitorCheckedAt, and call get_api_status when the caller needs the status right now.
  • list_categoriesCategory slugs and how many monitored APIs sit in each.No findings

    Why it is in this group

    • The name "list_categories" says "list": a word for reading.
    Description, as the server wrote it
    Category slugs and how many monitored APIs sit in each. Use the slugs with list_apis.
  • list_down_apisEverything the most recent monitor run found down or degraded, across all categories.No findings

    Why it is in this group

    • The name "list_down_apis" says "list": a word for reading.
    Description, as the server wrote it
    Everything the most recent monitor run found down or degraded, across all categories. Returns an empty list when the monitor snapshot is missing or stale — an empty list is therefore not proof that everything is healthy; check monitorLastRun.
  • search_apisFind monitored APIs by name, slug, category or description.No findings

    Why it is in this group

    • The name "search_apis" says "search": a word for reading.
    Description, as the server wrote it
    Find monitored APIs by name, slug, category or description. Use this to resolve a product name the user mentioned into the slug the other tools take.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:10 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
1
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://apistatuscheck.com/api/mcp: tools/list returned 8 tools to an anonymous client, including rank_reliability (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 0.2.3. Values in angle brackets are yours to fill in.

claude mcp add --transport http apistatuscheck https://apistatuscheck.com/api/mcp
claude mcp add --transport http apistatuscheck https://apistatuscheck.com/api/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__apistatuscheck__list_apis",
      "mcp__apistatuscheck__search_apis",
      "mcp__apistatuscheck__get_api_status",
      "mcp__apistatuscheck__list_down_apis",
      "mcp__apistatuscheck__get_uptime_history",
      "mcp__apistatuscheck__get_incident_history",
      "mcp__apistatuscheck__list_categories"
    ],
    "ask": [
      "mcp__apistatuscheck__rank_reliability"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as apistatuscheck. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.shibley/apistatuscheck/verify?hash=845cb298c0ed5a1fb5fc2e66fbd3d645ddc5c42afbad5d53b8bd61a819e111df" | jq -e '.changed == false'

Pinned hash 845cb298c0ed, from Nov 20, 2026, 12:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.shibley/apistatuscheck/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.shibley/apistatuscheck
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.shibley/apistatuscheck.svg)](https://radar.anlyon.com/servers/io.github.shibley/apistatuscheck)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:49 UTC.

API Status Check MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the API Status Check MCP server safe?

No scan can promise that. What its definitions show: 8 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the API Status Check MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the API Status Check MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the API Status Check MCP server have?

8 tools: 1 write, 7 read. rank_reliability, list_apis, search_apis, get_api_status, list_down_apis, get_uptime_history, get_incident_history and list_categories.

Does the API Status Check MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the API Status Check MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the API Status Check MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 20, 2026.