io.notworking/notworking

Est-ce que io.notworking/notworking est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.notworking/notworking » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 2 outils

• check_status≈ 388 tokens

  Is it down or blocking agents for everyone, or just you? Use when a site, URL, MCP server or skill isn't working: down, unreachable or an outage, a timeout, blocked (access denied, 403, 429 rate limited, a Cloudflare 'Just a moment' challenge, a CAPTCHA), a login loop, an MCP server that won't connect or a tool that errors, or a skill that fails. Look up a service by the URL you used, an access-path id (clawhub:<owner>/<slug>, skills.sh:<owner>/<repo>/<skill>, an MCP Registry name like io.github.<owner>/<server>) or a service name. Returns a one-sentence summary, the service, every listed access path with a description and failure reports from the last hour (and the last 24 hours and 7 days as context), the what_failed values and how to report. Unlisted targets return their own counts and status, with listed: false.

  Paramètres, retour & exemple (2)

  Paramètres

  • type · ? · optionnel
    Optional, to disambiguate: site, route, mcp or skill
  • target · string · requis
    The URL, access-path id or service name

  Exemple d'appel

  {"name": "check_status", "arguments": {"target": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• report≈ 806 tokens

  Report that an access path failed for you. Use the access-path id from check_status, or the URL you used. Only report failures that came from the service, not ones caused by your own tools, permissions or settings (like a fetch tool that refuses a domain). Anonymous. Never include personal data, booking details, credentials or full URLs with query strings. target is which access path failed; what_failed is how, from this list (the same for every service): site_unreachable: The site or server could not be reached at all, for example a DNS error, a timeout or a 5xx server error.; bot_block: The service refused the agent: an access-denied page, a 403 or 429 error, a bot wall or a challenge page.; robots_disallow: The site's robots.txt asks automated agents not to fetch this page.; captcha: A CAPTCHA or 'are you human?' check stopped the agent.; login_auth: Logging in or authenticating failed, for example a login loop, a new login step or rejected credentials.; api_error: An API the agent used returned an error or an unexpected response.; mcp_error: An MCP server failed to connect, initialise, list its tools or run a tool.; skill_failed: A skill could not be installed, or it ran but errored or produced a wrong result.; payment: A payment or checkout step failed or was blocked.; specific_page: One particular page or step failed while the rest of the service seemed to work.; other: Something else went wrong.

  Paramètres, retour & exemple (6)

  Paramètres

  • note · ? · optionnel
    Optional, at most 280 characters, no personal data. Never shown to other agents.
  • type · ? · optionnel
    Optional: site, route, mcp or skill. Use mcp for an MCP server that isn't in the catalogue, since its name can look like a domain
  • target · string · requis
    The access-path id (or URL) you used
  • country · ? · optionnel
    Optional ISO-3166 alpha-2 country code, like SG
  • agent_type · ? · optionnel
    Optional: which agent you are; 'other' if not listed
  • what_failed · array · requis
    How it failed: one or more values

  Exemple d'appel

  {"name": "report", "arguments": {"target": "texte", "what_failed": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://notworking.io/mcp