Is the internet OK?
Server Details
Live internet status, security incidents, and dependency and GitHub repo checks. No key.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 6 tools
check_repo and check_stack clearly overlap in purpose (checking dependencies against flaws), but the descriptions draw a workable line: a GitHub repo URL vs. packages/lockfile text. list_incidents and internet_status also both surface open incidents, though internet_status is framed as a live service dashboard and list_incidents as a ranked incident feed, which mostly separates them. get_incident is cleanly distinct.
All snake_case with a clear verb_noun pattern for actions (check_repo, check_stack, get_incident, list_incidents). Deviations are minor: events_since is verb+preposition and internet_status is noun+noun, but both read naturally and stay in the same convention.
Six tools is well scoped for this server: two checking tools, three incident/status browsing tools, and one delta-feed tool. Each earns its place with no filler.
The surface covers the lifecycle reasonably: check repos/stacks, list and get incidents (open or resolved by id), live service status, and a changelog. Minor gaps exist — no way to look up a specific service's status by name or to search incidents by package/product, so discovery of resolved incidents relies on events_since or list order.
Available Tools
6 toolscheck_repoIs this repo OK?ARead-onlyIdempotentInspect
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-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.
Inputs: repo (required), full.
check_stackAm I affected?ARead-onlyIdempotentInspect
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. 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.
Inputs: full, filename, lockfile, packages, +1 more.
events_sinceWhat changedARead-onlyIdempotentInspect
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.
Inputs: since.
get_incidentOne incidentARead-onlyIdempotentInspect
One incident by its id (as list_incidents or internet_status give it, like 2026-10-14-nextjs-rce), open or resolved.
Inputs: id (required).
internet_statusIs the internet OK?ARead-onlyIdempotentInspect
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.
Inputs: no named parameters.
list_incidentsOpen incidentsARead-onlyIdempotentInspect
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.
Inputs: severity.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Is GitHub, npm, Cloudflare or your AI provider down right now? 20 status pages, one call.
Live cloud/SaaS outages, provider reliability and exploited CVEs from official status pages and CISA
Dependency releases, TLS and domain expiry, and vendor status pages from one endpoint.
Live status probes plus published uptime and incident history for 280+ APIs and cloud services.
Related MCP Servers
- AlicenseAqualityDmaintenanceLive operational status for 2,400+ major software services — AWS, GitHub, Stripe, OpenAI, Cloudflare, and more — pulled from each provider's official status page and returned as a normalised up / degraded / down result for any service you ask about.51MIT
- AlicenseNot gradedqualityBmaintenanceProvides live infrastructure monitoring for AI agents, including domain health checks, MCP server security posture, email blacklists, broken-link scans, and cloud vendor status. No signup or API key needed for public tools.MIT
- AlicenseAqualityBmaintenanceEnables querying the current state, incident history, resolution times, and feed URLs for over 1,100 SaaS/cloud vendor status pages.7MIT
- AlicenseCqualityCmaintenanceMonitor the real-time status of 200+ popular APIs and services. Check if services like GitHub, Stripe, AWS, and Slack are experiencing outages or degraded performance directly from your AI assistant.59 npm1MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.