Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

API Status Check

REMOTE · APISTATUSCHECK.COM

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

0 this week 82 Trust /100

Last scanned (14 hours ago)

Scores higher than 81% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Monitoring and Observability

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability83
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 916 tokens (~114/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 8 Nov 26 0
    • Stability: 0.97 → pass security
  • 7 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 5 Nov 26 0
    • Stability: 0.97 → pass security
  • 4 Nov 26 0
    • Stability: pass → 0.97 functional
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://apistatuscheck.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=apistatuscheck.com CN=YR1,O=Let's Encrypt,C=US 25 Sept 2026 24 Dec 2026 RSA 2048 SHA256-RSA 6f41235681d6a3a94c0cc221143bd70e1b4
SANs: apistatuscheck.com
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of apistatuscheck.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
apistatuscheck.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://apistatuscheck.com/api/mcp Verified 200
http (plaintext) http://apistatuscheck.com/api/mcp HTTPS enforced 308 https://apistatuscheck.com/api/mcp
MCP tools · 8 exposed · ~747 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_api_status ~82

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.

NameTypeReqDescription
slugstringyesAPI slug, e.g. "openai". Use search_apis to resolve a name.

No output schema declared.

No examples provided.

get_incident_history ~158

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.

NameTypeReqDescription
limitinteger–Max incidents (default 25).
servicestringyesAPI slug, e.g. "openai". Use search_apis to resolve a name.
windowstring–Time window: 7d, 30d, 90d, 180d, 365d, all (default 90d).

No output schema declared.

No examples provided.

get_uptime_history ~93

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

NameTypeReqDescription
rangestring–Window to return data points for (default 24h).
slugstringyesAPI slug, e.g. "openai".

No output schema declared.

No examples provided.

list_apis ~105

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.

NameTypeReqDescription
categorystring–Category slug to filter by, e.g. "ai" — omit for all categories.
limitinteger–Max results (default 25).

No output schema declared.

No examples provided.

list_categories ~29

Category slugs and how many monitored APIs sit in each. Use the slugs with list_apis.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_down_apis ~55

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

rank_reliability ~152

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.

NameTypeReqDescription
servicesarrayyesAPI slugs to compare, e.g. ["openai","anthropic","vercel"].
windowstring–Time window: 7d, 30d, 90d, 180d, 365d, all (default 90d).

No output schema declared.

No examples provided.

search_apis ~73

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.

NameTypeReqDescription
limitinteger–Max results (default 25).
querystringyesFree-text query, e.g. "openai" or "payments".

No output schema declared.

No examples provided.

Install

How do I install the API Status Check MCP server?

API Status Check is a hosted endpoint at https://apistatuscheck.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · apistatuscheck.com

# add to Claude Code
claude mcp add --transport http shibley-apistatuscheck 'https://apistatuscheck.com/api/mcp'
Common questions

What is the API Status Check MCP server?

API Status Check is an MCP server listed in the public MCP registry as io.github.shibley/apistatuscheck. Live status probes plus published uptime and incident history for 280+ APIs and cloud services. This page covers its hosted endpoint (https://apistatuscheck.com/api/mcp).

Is the API Status Check MCP server safe to use?

API Status Check scores 82 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the API Status Check MCP server expose?

API Status Check exposes 8 tools: list_apis, search_apis, get_api_status, list_down_apis, get_uptime_history, and 3 more. Their descriptions and schemas cost roughly 747 tokens of context every time the server is loaded.

Does the API Status Check MCP server require authentication?

No. We connected to API Status Check without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the API Status Check MCP server still maintained?

API Status Check is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the API Status Check MCP server?

VerifyMCP ran 12 checks on API Status Check, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about API Status Check: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.