Responded16 / 22 checks passed
Remote MCP server to run your Atako AI agents: chat, projects, files, integrations and channels.
- Passed: Handshake
- Passed: Tools listed
- Passed: Updated recently
Median latency 132 ms · Last checked
Independent monitoring
Health & checks
Outdated check
Last connection measurement is over 24 hours old. Current availability is unknown.
Last checked| Test area | Passed | Failed | Unmeasured |
|---|---|---|---|
ConnectionCan a client connect and discover tools? | 5 | 0 | 0 |
Reliability & speedDoes it respond consistently and quickly? | 0 | 0 | 4 |
Access & authenticationWhat is required to use this server? | 1 | 0 | 2 |
Tool qualityAre the tool definitions usable by an agent? | 4 | 0 | 0 |
Publisher identityCan the publisher be traced to its source? | 3 | 1 | 2 |
Unmeasured means there is not enough evidence to decide. How these checks work
Inspect individual checks 22 recorded
Core
- Pass
- Pass
- Pass
- Pass
- Pass
Performance
- Not measured
- Not measured
- Not measured
- Not measured
Access
- Pass
- Not measured
- Not measured
Tools
- Pass
- Pass
- Pass
- Pass
Publisher
- Pass
- Pass
- Fail
- Not measured
- Pass
- Not measured
Start using Is the internet OK?
Connect to this server
Choose your client, copy the configuration, then enable the server in your client’s MCP settings.
Run this command in your terminal, then restart Claude Code.
Claude Code
claude mcp add --transport http is-the-internet-ok https://istheinternetok.com/mcpCapabilities
Tools 6
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-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.
Discoveredcheck_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. 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.
Discoveredevents_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.
Discoveredget_incident
One incident by its id (as list_incidents or internet_status give it, like 2026-10-14-nextjs-rce), open or resolved.
Discoveredinternet_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.
Discoveredlist_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.
DiscoveredRecent measurements
Probe history
| Checked | Result | Response | Tools |
|---|---|---|---|
| Connected | 746 ms | 6 |