Is the internet OK?
com.istheinternetok/statusVersion 1.0.0Live internet status, security incidents, and dependency and GitHub repo checks. No key.
Status
Responds282 msAnswered our handshake without sign-in.- Last checked
- Nov 14, 2026, 14:02 UTC
- Latency
- 282 ms
- Remotes responding
- 1 of 1
- Sign-in
- No sign-in
- Hosting
- Hosted outside the EU (detected)
- Registry data as of
- Nov 14, 2026, 22:14 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://istheinternetok.com/mcpResponds282 msNo sign-in
Claude Code
claude mcp add --transport http status https://istheinternetok.com/mcpClaude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: status
Remote MCP server URL: https://istheinternetok.com/mcpCursor
{
"mcpServers": {
"status": {
"url": "https://istheinternetok.com/mcp"
}
}
}VS Code
code --add-mcp '{"name":"status","type":"http","url":"https://istheinternetok.com/mcp"}'Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
6 tools
Read-only | Idempotent | Open world | ||
|---|---|---|---|---|
check_repoChecks 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-of, no; unknown when it holds no lockfile we can read), what to update first and what each flaw lets someone do, in plain words. A first look at a big repo takes a few seconds. | No | Yes | Yes | Yes |
check_stackChecks 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. Says the answer on the site's scale (yes, mostly, kind-of, no; unknown when no exact version was sent), which packages to update and to which version. Give packages, product ids, or the text of a lockfile (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, composer.lock; with filename, any of 30+ formats: Cargo.lock, go.mod, uv.lock, Gemfile.lock...). For a public GitHub repo, check_repo reads every lockfile itself. Only names and versions reach the flaw database; nothing about who asked is stored. | No | Yes | Yes | Yes |
events_sinceWhat 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. | No | Yes | Yes | No |
get_incidentOne incident by its id (as list_incidents or internet_status give it, like 2026-10-14-nextjs-rce), open or resolved. | No | Yes | Yes | No |
internet_statusThe 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. | No | Yes | Yes | No |
list_incidentsThe 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. | No | Yes | Yes | No |
Details
- Registry status
- Active
- Published
- Oct 27, 2026
- Updated
- Oct 27, 2026
- Repository
- Not given
- Categories (suggested)
- Developer toolsSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
- GDPR
- Not declared