io.github.presendapp/presend-deps

Est-ce que io.github.presendapp/presend-deps est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.presendapp/presend-deps » 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 5 outils

• maintainer_change_check≈ 311 tokens

  Publisher-change analysis is npm only. Also reports whether the package exists (found) and its age (first_published, package_age_days, new_package if first published less than 30 days ago), for npm and for PyPI; on PyPI only existence and age are available. Flags a previously unseen human publisher taking over a package after 180+ days of inactivity, within the last 365 days (the event-stream attack pattern). npm trusted publishing (verified OIDC identity, not just a bot-like account name), pre-release, and handovers to a publisher who already maintains another widely used package (100k+ weekly downloads) are reported but not flagged. Does not detect hijacked existing accounts; a heuristic for review, not proof.

  Paramètres, retour & exemple (2)

  Paramètres

  • package · string · requis
    Package name, e.g. lodash
  • ecosystem · string · requis
    npm (full analysis) or pypi (existence and age only).

  Exemple d'appel

  {"name": "maintainer_change_check", "arguments": {"package": "texte", "ecosystem": "texte"}}

  Exemple de retour

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

• repo_health_check≈ 216 tokens

  Maintenance signals for a GitHub repository given as owner/name: stars, forks, open issues, license, archived and fork flags, creation date and age, days since last push, topics. Use it to judge whether a dependency looks maintained or abandoned. For an npm or PyPI package whose repository you do not know, supply_chain_check resolves it from registry metadata and includes these signals. GitHub only; missing or private repositories return found: false.

  Paramètres, retour & exemple (1)

  Paramètres

  • repo · string · requis
    GitHub repository in owner/name format, e.g. lodash/lodash.

  Exemple d'appel

  {"name": "repo_health_check", "arguments": {"repo": "texte"}}

  Exemple de retour

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

• supply_chain_check≈ 490 tokens

  Call this before installing or adding a package (npm install, pip install, a new entry in a manifest), especially one whose name you recalled or that a model suggested. One-call risk check: combines vulnerability_check (OSV.dev), typosquat_check, maintainer_change_check (npm only) and repo_health_check (when the GitHub repo can be resolved) into one overall verdict. A package that does not exist on npm or PyPI gets overall_risk 'package_not_found': the name may be invented and should not be installed. A package first published less than 30 days ago gets the 'new_package' flag and overall_risk 'review_recommended': new packages are where invented and look-alike names get registered, so the name is worth confirming against the project's own documentation before installing (on PyPI the age is that of the oldest release still published; being new does not make a package malicious). Use the individual tools to investigate one signal. Vulnerabilities are checked for the given version, or the latest published one (version_checked, version_source). If a check could not run (rate limit, upstream error), it is listed in unavailable_checks and overall_risk is 'incomplete', never 'no_signals_found'. Also flags a version marked deprecated on npm or yanked on PyPI.

  Paramètres, retour & exemple (3)

  Paramètres

  • package · string · requis
    Package name to check.
  • version · string · optionnel
    Exact version to check for known vulnerabilities. Optional: defaults to the latest published version (npm and PyPI).
  • ecosystem · string · requis
    Package ecosystem, e.g. npm. maintainer-change-check only runs for npm.

  Exemple d'appel

  {"name": "supply_chain_check", "arguments": {"package": "texte", "ecosystem": "texte"}}

  Exemple de retour

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

• typosquat_check≈ 246 tokens

  Call before installing a package whose name you typed or recalled. Checks whether an npm or PyPI package name is a near-miss of a well-known package (typosquatting), with an edit-distance threshold scaled to name length; names of 3 characters or fewer are not fuzzy-matched. Uses a curated list of popular names, so a clean result does not prove a package is safe. It does not check that the package exists: supply_chain_check does.

  Paramètres, retour & exemple (2)

  Paramètres

  • package · string · requis
    Package name to check for likely typosquatting of a well-known package in the given ecosystem.
  • ecosystem · string · requis
    Package ecosystem, e.g. npm or PyPI.

  Exemple d'appel

  {"name": "typosquat_check", "arguments": {"package": "texte", "ecosystem": "texte"}}

  Exemple de retour

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

• vulnerability_check≈ 244 tokens

  Checks a package (optionally a specific version) against OSV.dev for known vulnerabilities: npm, PyPI, Go, crates.io, Maven, RubyGems, Packagist and NuGet. For npm and PyPI, a name that does not exist returns found: false and vulnerable: null, never a clean result. Use supply_chain_check for a combined verdict.

  Paramètres, retour & exemple (3)

  Paramètres

  • package · string · requis
    Package name to check against OSV.dev for known CVEs.
  • version · string · optionnel
    Omit to check all versions of the package.
  • ecosystem · string · requis
    Package ecosystem, e.g. npm, PyPI, Go, crates.io, Maven, RubyGems, Packagist, or NuGet.

  Exemple d'appel

  {"name": "vulnerability_check", "arguments": {"package": "texte", "ecosystem": "texte"}}

  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://presend.pages.dev/mcp-deps