com.istheinternetok/status

endpoint

https://istheinternetok.com/mcp

protocol

http-sse ·2025-06-18

authentication

none observed

public key

none — nobody has proven they own this listing · is it yours? claim it

karma

0 · newcomer

Is com.istheinternetok/status live?

Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.

Is com.istheinternetok/status free to use?

Yes — the hub reached it with no key and no payment.

What tools does com.istheinternetok/status have?

6 tools: get_incident, check_repo, list_incidents, internet_status, check_stack, events_since.

Is com.istheinternetok/status safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

• internet_status open 1h ago

  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.

  mcp-tool

  1234

  {
    "type": "object",
    "properties": {}
  }

  arguments 4 lines copy
• check_stack open 1h ago

  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.

  mcp-tool

  123456789101112131415161718192021222324252627282930313233343536373839404142434445464748

  {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {
      "full": {
        "type": "boolean",
        "description": "Also every flaw of every package, minor ones included. Without it: the answer, what to update and why."
      },
      "filename": {
        "type": "string",
        "description": "The lockfile's file name (Cargo.lock, go.mod, uv.lock...): reads it with the repo check's own readers, which also tell dev dependencies apart."
      },
      "lockfile": {
        "type": "string",
        "maxLength": 5000000,
        "description": "The whole text of a lockfile or manifest."
      },
      "packages": {
        "type": "array",
        "items": {
          "type": "object",
          "required": [
            "ecosystem",
            "name"
          ],
          "properties": {
            "name": {
              "type": "string"
            },
            "version": {
              "type": "string"
            },
            "ecosystem": {
              "type": "string",
              "description": "One of npm, PyPI, Packagist, Maven, Go, crates.io, RubyGems, NuGet, Docker, GitHub Actions, ConanCenter, Hackage, Pub, SwiftURL, Hex, CRAN, Julia (lowercase works, pip and composer too)."
            }
          }
        }
      },
      "products": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "description": "Product ids people install: chrome, firefox, safari, edge, windows, macos, ios, android, linux, office, whatsapp, zoom, plex, wordpress, php, nodejs, python, openssl, nginx, apache-httpd, ivanti-connect-secure, pan-os, fortimail, fortios, cisco-asa, tidb-cloud."
      }
    }
  }

  arguments 48 lines copy
• events_since open 1h ago

  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.

  mcp-tool

  12345678910

  {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {
      "since": {
        "type": "string",
        "description": "An ISO date; the last 7 days when left out."
      }
    }
  }

  arguments 10 lines copy
• get_incident unknown never probed

  One incident by its id (as list_incidents or internet_status give it, like 2026-10-14-nextjs-rce), open or resolved.

  mcp-tool

  12345678910111213

  {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "id"
    ],
    "properties": {
      "id": {
        "type": "string",
        "description": "The incident id."
      }
    }
  }

  arguments 13 lines copy
• check_repo unknown never probed

  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.

  mcp-tool

  1234567891011121314151617

  {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "repo"
    ],
    "properties": {
      "full": {
        "type": "boolean",
        "description": "Also every flaw of every package (hundreds of KB for a big repo). Without it: the answer, what to update and why, and where the full list is."
      },
      "repo": {
        "type": "string",
        "description": "owner/name, or the repo's GitHub URL: vercel/next.js, https://github.com/pallets/flask"
      }
    }
  }

  arguments 17 lines copy
• list_incidents unknown never probed

  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.

  mcp-tool

  123456789101112131415

  {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {
      "severity": {
        "enum": [
          "critical",
          "major",
          "minor"
        ],
        "type": "string",
        "description": "Only incidents of this severity."
      }
    }
  }

  arguments 15 lines copy

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.