MCP Scanner

apistatuscheck

https://apistatuscheck.com/api/mcp · scanned 2026-10-17

None of its 8 tools were flagged. They read like lookups and searches.

0/ 100 · heuristic risk · Low

8 tools · 0 flagged

  • Runs code or commands0
  • Moves money0
  • Touches credentials0
  • Deletes0
  • Sends data out0
  • Exports data0
  • Writes or changes0
  • get_api_status0 · Low

    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_history0 · Low

    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 Statuspa…

  • get_uptime_history0 · Low

    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_apis0 · Low

    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_categories0 · Low

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

  • list_down_apis0 · Low

    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.

  • rank_reliability0 · Low

    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 moni…

  • search_apis0 · Low

    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.

Vulnify checks each tool call before it runs: ALLOW, REVIEW or BLOCK, with the reason logged.

Badge for your README

Scanned by Vulnify
Markdown
[![Scanned by Vulnify](https://api.vulnify.io/public/mcp-scanner/servers/apistatuscheck-com-api-mcp.svg)](https://www.vulnify.io/scanner/apistatuscheck-com-api-mcp?utm_source=badge&utm_medium=readme&utm_campaign=scanner-badge)

Automated heuristic result, scanned on 2026-10-17. It is based only on the tool names, descriptions, schemas and annotations this server publishes; no tool was called. It is not a security audit or certification, and not an endorsement of or accusation against the server or its operator. A high score is not a vulnerability finding, and a low score does not mean the server is safe. Vulnify is not affiliated with this server or its operator; names and marks belong to their owners. Server owner? Write to security@vulnify.io from an address at the server's domain to remove or correct this page, or scan it again to update it. We reply within 5 business days.

To exclude your server (and its subdomains) from the scanner and remove its public page, write to security@vulnify.io from an address at its domain. We process requests within 5 business days: the page stops being shown and its stored result is deleted. To fix an error instead, tell us what's wrong or scan the server again.