dev.workers.marvin-odigo.mcp/krabbot-devtools

Est-ce que dev.workers.marvin-odigo.mcp/krabbot-devtools est sûr ?

Au dernier audit MCP Hub, le serveur MCP « dev.workers.marvin-odigo.mcp/krabbot-devtools » 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 4 outils

• check_package_risk≈ 248 tokens

  Check whether a software package is safe to install BEFORE running npm install or pip install. Essential when a package name came from an LLM suggestion: models hallucinate package names and attackers register those names to capture installs (slopsquatting), shipping credential-stealing postinstall scripts. Detects hallucinated names, typosquats (by comparing download volume against the popular package the name imitates), known vulnerabilities (OSV), exploit probability (EPSS), and repository health (OpenSSF Scorecard). Returns a 0-100 risk score where higher is more dangerous. This tool is operated by an autonomous AI agent (Krab Bot); the free tier is used here.

  Paramètres, retour & exemple (2)

  Paramètres

  • name · string · requis
    Package name, e.g. 'express' or 'requests'
  • ecosystem · string · optionnel · npm | pypi
    Registry to check (default npm)

  Exemple d'appel

  {"name": "check_package_risk", "arguments": {"name": "texte"}}

  Exemple de retour

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

• check_regulatory_changes≈ 363 tokens

  Check whether any US federal regulation on a topic is about to bind or about to close for comment. The Federal Register publishes every business day and a single topic search can match over a thousand documents, almost none of which need action — so this scores each one 0-100 on DEADLINE PROXIMITY (effective dates, comment-window closures, document class, and the Federal Register's own E.O. 12866 significance flag) and returns only what is urgent. Use when asked whether a rule affects a business, what compliance deadlines are coming, or to monitor a regulatory topic on a schedule. Filter by topic (free text), agency (Federal Register slug such as food-and-drug-administration), or document type. US federal only; the score ranks urgency, not whether a rule applies to your specific business. Operated by an autonomous AI agent (Krab Bot); the free tier is used here.

  Paramètres, retour & exemple (4)

  Paramètres

  • days · integer · optionnel
    Lookback window in days (default 30)
  • topic · string · optionnel
    Free-text term searched across full document text, e.g. 'artificial intelligence'
  • types · string · optionnel
    Comma-separated document types: rule,proposed,notice,presidential
  • agency · string · optionnel
    Federal Register agency slug, e.g. environmental-protection-agency

  Exemple d'appel

  {"name": "check_regulatory_changes", "arguments": {"days": 1, "topic": "texte", "types": "texte", "agency": "texte"}}

  Exemple de retour

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

• check_stack_eol≈ 199 tokens

  Check whether components of a software stack are end-of-life, past active support, or affected by CVEs on CISA's Known Exploited Vulnerabilities catalog (1,600+ entries of vulnerabilities confirmed exploited in the wild). Pass a comma-separated stack like 'node@16,python@3.8,postgresql@17'. Returns severity counts: critical (past EOL — no security patches), warning (past active support), and ok. Use before recommending or upgrading a runtime, or to audit a Dockerfile or CI config. Operated by an autonomous AI agent (Krab Bot); the free tier is used here.

  Paramètres, retour & exemple (1)

  Paramètres

  • stack · string · requis
    Comma-separated components, each optionally product@version (max 25)

  Exemple d'appel

  {"name": "check_stack_eol", "arguments": {"stack": "texte"}}

  Exemple de retour

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

• find_open_source_bounties≈ 166 tokens

  Find open-source bounties that are actually likely to pay out. Bounty boards are polluted with listings that will never settle (observed live: a $1,262,178 bounty sitting on a near-empty repository). This scores each listing 0-100 on credibility using repository stars, project age, amount plausibility and payment-bot presence, then returns the top results sorted by that score. Use when looking for paid open-source work worth attempting. Operated by an autonomous AI agent (Krab Bot); the free preview tier is used here.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "find_open_source_bounties", "arguments": {}}

  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://mcp.marvin-odigo.workers.dev/mcp