Is the internet OK?

com.istheinternetok/status · v1.0.0 · developer-tools

Is the internet OK? is healthy: it completed an MCP handshake in 809 ms and exposes 6 tools.

Live internet status, security incidents, and dependency and GitHub repo checks. No key.

Endpoint: https://istheinternetok.com/mcp (streamable-http)

No repository listed · Website · JSON · Add to my inventory

Facts

Checked (UTC)	Status	Latency	Error
2026-10-28T00:25:08.852Z	Healthy	809

`internet_status`	The live status of the whole internet: a one-sentence answer, every watched service (Cloudflare, AWS, Google Workspace, Discord, PlayStation Network, OpenAI, GitHub...) with its state and its group, and the open security incidents with what to do. Refreshed every 5 minutes.
`list_incidents`	The open incidents (critical flaws, big outages, supply-chain attacks), worst first, each with its impact, what to do, the affected packages and products, and its page.
`events_since`	What changed since a date, oldest first: incidents created, updated or resolved, and big services going down or coming back. Keep `next` and pass it as `since` next time to watch.
`get_incident`	One incident by its id (as list_incidents or internet_status give it, like 2026-10-14-nextjs-rce), open or resolved.
`check_stack`	Checks a project's dependencies and a person's apps. Every package with an exact version (as a lockfile pins it) is checked against every known flaw (OSV.dev, CISA's exploited list), and the incidents this site explains come first; a range, no version, or an app is only compared with those incidents
`check_repo`	Checks a public GitHub repo: every package its lockfiles pin at its latest commit, in every folder and 14 ecosystems (npm, PyPI, crates.io, Go, Maven, NuGet, RubyGems, Packagist, Pub, Swift, Hex, Hackage, CRAN, Julia), against every known flaw. Says the answer on the site's scale (yes, mostly, kind-