app.repopilot/repopilot

Est-ce que app.repopilot/repopilot est sûr ?

Au dernier audit MCP Hub, le serveur MCP « app.repopilot/repopilot » 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 8 outils

• analyze_repo≈ 997 tokens

  CALL to investigate behavior in public source: supply question and relevant path_hints found from actual usages, for up to four files with commit-pinned line citations. checked_sha selects a commit; base_sha adds before/after excerpts; pr selects a public PR and observes its head's GitHub check runs. source_ranges retrieves missing context at pinned revisions, up to 40 lines per range. Selection is bounded, not exhaustive or proof of compatibility. Without question, returns repository_brief with saved purpose, main parts, starting files, setup, revisions and gaps. Pass exactly one of repo or package. Example: {repo:'expressjs/multer',question:'How are file size limits handled?',path_hints:['lib/make-middleware.js']}.

  Paramètres, retour & exemple (9)

  Paramètres

  • pr · integer · optionnel
    Public PR number in repo. Requires question. Omit base_sha.
  • repo · string · optionnel
    Public GitHub repository as owner/repo or a github.com URL.
  • owner · string · optionnel
    Repository owner, when repo carries only the bare name. Optional: prefer the single owner/repo form in repo.
  • package · string · optionnel
    npm package name, for example lodash or npm:@scope/pkg. To judge a specific VERSION rather than the package as a whole, use evaluate_dependency_change instead.
  • base_sha · string · optionnel
    Compare source at this base commit; omit when using pr.
  • question · string · optionnel
  • path_hints · array · optionnel
    Scope retrieval to these repository-relative files or directories. Requires question.
  • checked_sha · string · optionnel
    Immutable head revision; required with source_ranges.
  • source_ranges · array · optionnel
    Read only these exact ranges, at most two per file/side and 40 lines per range. Requires question and checked_sha; base side also requires base_sha. Paths must fall within path_hints when supplied. Omit pr for base ranges.

  Exemple d'appel

  {"name": "analyze_repo", "arguments": {"pr": 1, "repo": "texte", "owner": "texte", "package": "texte", "base_sha": "texte", "question": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"tool": "texte", "agent": {}, "status": "texte", "schema_version": "texte", "repository_brief": "texte"}}

• check_change_risk≈ 860 tokens

  CALL before merging a pull request or after producing a local diff. Returns a deterministic 0-10 change-shape score with receipts for size, spread, missing tests, sensitive paths, hotspots, and blast radius. Pass repo+pr OR diff; repo may accompany diff for cached hotspot context. This prioritizes review and never approves a merge.

  Paramètres, retour & exemple (8)

  Paramètres

  • pr · number|string · optionnel
    Positive pull request number, used with repo.
  • diff · string · optionnel
    Raw unified git diff to score directly.
  • repo · string · optionnel
    owner/repo or a github.com URL.
  • files · array · optionnel
    Privacy-preserving changed-file facts; contains no source or diff hunks.
  • proofs · array · optionnel
  • base_sha · string · optionnel
  • head_sha · string · optionnel
  • contract_id · string · optionnel
    Optional short-lived contract_id returned by plan_repo_task.

  Exemple d'appel

  {"name": "check_change_risk", "arguments": {"pr": 1, "diff": "texte", "repo": "texte", "files": [], "proofs": [], "base_sha": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"tool": "texte", "agent": {}, "status": "texte", "schema_version": "texte"}}

• check_dependency≈ 495 tokens

  CALL when the user or agent is about to add, upgrade, trust, fork, or deploy an npm package or public GitHub repository. Returns a lean repository-level recommendation, confidence, evidence gaps, CVEs, maintenance, ownership, license, CI/tests, Scorecard, freshness, and next actions. DO NOT use for code navigation. Pass exactly one of repo or package. A favourable result does not validate an exact package version or compatibility.

  Paramètres, retour & exemple (3)

  Paramètres

  • repo · string · optionnel
    Public GitHub repository as owner/repo or a github.com URL.
  • owner · string · optionnel
    Repository owner, when repo carries only the bare name. Optional: prefer the single owner/repo form in repo.
  • package · string · optionnel
    npm package name, for example lodash or npm:@scope/pkg. To judge a specific VERSION rather than the package as a whole, use evaluate_dependency_change instead.

  Exemple d'appel

  {"name": "check_dependency", "arguments": {"repo": "texte", "owner": "texte", "package": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"tool": "texte", "agent": {}, "status": "texte", "schema_version": "texte"}}

• compare_repos≈ 396 tokens

  CALL when the user is choosing between exactly two dependencies or repositories. Returns the preferred candidate for each use case, material trade-offs, confidence, and evidence gaps. Each target is owner/repo, a GitHub URL, an npm package name, or npm:@scope/pkg. Cached full analyses are preferred; a miss uses bounded live GitHub/OpenSSF evidence with limited confidence and explicit unknowns rather than guessing.

  Paramètres, retour & exemple (2)

  Paramètres

  • a · string · requis
    First repo or npm package target.
  • b · string · requis
    Second repo or npm package target.

  Exemple d'appel

  {"name": "compare_repos", "arguments": {"a": "texte", "b": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"tool": "texte", "agent": {}, "status": "texte", "schema_version": "texte"}}

• evaluate_dependency_change≈ 1904 tokens

  CALL immediately before adding or upgrading an npm dependency. Answers "is this exact version safe to take on" from registry metadata, advisory deltas (for the version itself and for every package in the dependency tree a fresh install resolves to), provenance, license, and repository evidence, and returns blockers, warnings, a recommendation, and a verification plan. Example: {"dependency":"lodash","to_version":"4.17.21"} — every field is top-level, never nested under a "change" key. Only `dependency` is required — omit to_version to evaluate the latest published version, exactly as `npm install <pkg>` would. to_version also accepts a dist-tag ("latest") or a SemVer range ("^4.17.0"); it resolves to one exact version, reported back in change.to_version. Everything RepoPilot can infer is inferred, and every default, repair, and resolution is listed in input_adjustments. Evaluates only; never installs or edits anything.

  Paramètres, retour & exemple (8)

  Paramètres

  • intent · string · optionnel
    Optional free text describing why you are making this change. Advisory only; it changes no verdict.
  • project · object · optionnel
    Optional, source-free facts about the project you are changing. Supplying it adds Node/peer/license compatibility and a command-level verification plan. Omit it entirely and compatibility comes back "unknown" - read that as not checked, never as no problem found. Every field is optional; anything missing is defaulted and reported in input_adjustments, never rejected. Never send source code.
  • dependency · string · requis
    A STRING: the npm package name on its own, with no version and no surrounding object — "lodash", "@types/node". Not {"name":...}, not {"lodash":"^4.17.0"}, not a list, and never wrapped in a top-level {"change":{...}} object — every field here is top-level. The version goes in to_version, the currently installed one in from_version.
  • to_version · string|number · optionnel
    The version you intend to install — an exact version ("4.18.1"), a dist-tag ("latest"), or a SemVer range ("^4.17.0"). A quoted string is preferred; a bare JSON number ("to_version": 19) is also accepted and read as the string "19". Omit to evaluate the latest published version.
  • from_version · string|number|null · optionnel
    The version currently installed, or omitted when adding a new dependency. A bare JSON number is accepted the same way as to_version. Supplying it produces a before/after advisory comparison.
  • policy_profile · string · optionnel · permissive | balanced | strict
    Named team dependency policy. Strict requires provenance and denies package install hooks. Must be spelled exactly — a near-miss spelling is rejected rather than guessed, because reading it wrong would answer under a policy you did not ask for.
  • dependency_type · string · optionnel · runtime | development | optional | peer
    Where the dependency goes, in THESE words: "runtime" for a dependencies entry, "development" for devDependencies. The manifest and CLI spellings ("dev", "devDependencies", "--save-dev", "prod") are mapped onto these and reported in input_adjustments.
  • package_manager · string · optionnel · npm | pnpm | yarn | bun
    Optional. Only affects the commands and lockfile named in the verification plan. Inferred from project.lockfile_path when you send a project snapshot, and assumed to be npm otherwise.

  Exemple d'appel

  {"name": "evaluate_dependency_change", "arguments": {"dependency": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"tool": "texte", "agent": {}, "status": "texte", "schema_version": "texte"}}

• get_artifact≈ 620 tokens

  CALL before substantial code work in an unfamiliar repository when the agent needs key files, entry points, architecture hypotheses, a reading order, and verify-before-trusting guidance. Returns the cached CLAUDE.md-style artifact or Cursor rules. Do not call again if the artifact is already in context. Takes NO artifact id: name the repository itself. Minimal call: {"repo":"vercel/next.js"}. Pass exactly one of repo or package, each a plain string.

  Paramètres, retour & exemple (4)

  Paramètres

  • repo · string · optionnel
    Public GitHub repository as owner/repo or a github.com URL.
  • owner · string · optionnel
    Repository owner, when repo carries only the bare name. Optional: prefer the single owner/repo form in repo.
  • format · string · optionnel · markdown | cursor
    Optional. markdown for CLAUDE.md-style guidance (the default); cursor for .mdc rules.
  • package · string · optionnel
    npm package name, for example lodash or npm:@scope/pkg. To judge a specific VERSION rather than the package as a whole, use evaluate_dependency_change instead.

  Exemple d'appel

  {"name": "get_artifact", "arguments": {"repo": "texte", "owner": "texte", "format": "markdown", "package": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"tool": "texte", "agent": {}, "status": "texte", "schema_version": "texte"}}

• plan_repo_task≈ 749 tokens

  CALL before editing an unfamiliar public repository, or to find where a bug or feature lives. Pass the issue or task text (up to 4000 characters; include the error and expected behaviour) and checked_sha when you know it. Returns files ranked for the task at that commit (provenance task_localizer), the owning layer, a bounded reading order, dependency consumers, test/verification obligations, analyzed-vs-checked SHA relation, evidence provenance, and a short-lived verification contract. To rank files, task text is sent to RepoPilot's model provider; it is never persisted or echoed. Rankings are suggestions: read the files before acting.

  Paramètres, retour & exemple (8)

  Paramètres

  • repo · string · optionnel
    Public GitHub repository as owner/repo or a github.com URL.
  • task · string · requis
  • owner · string · optionnel
    Repository owner, when repo carries only the bare name. Optional: prefer the single owner/repo form in repo.
  • intent · object · optionnel
  • package · string · optionnel
    npm package name, for example lodash or npm:@scope/pkg. To judge a specific VERSION rather than the package as a whole, use evaluate_dependency_change instead.
  • max_files · integer · optionnel
  • path_hints · array · optionnel
    Optional repository-relative files or directories to prioritize.
  • checked_sha · string · optionnel

  Exemple d'appel

  {"name": "plan_repo_task", "arguments": {"task": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"tool": "texte", "agent": {}, "status": "texte", "schema_version": "texte"}}

• verify_dependency_change≈ 2186 tokens

  CALL after changing the manifest/lockfile and running local checks. Compares the exact evaluated target with the resolved result and caller-reported proof receipts, checks every version in resolved_changes for advisories (list all packages the lockfile change added or changed), reports missing/failed evidence and residual risk, and labels receipts as caller asserted. It never runs commands or stores diff/check output.

  Paramètres, retour & exemple (4)

  Paramètres

  • diff · string · optionnel
  • after · object · requis
  • checks · array · requis
  • evaluation · object · requis
    The verification_context object exactly as evaluate_dependency_change returned it, passed back unchanged. Its signature covers every field, so edit nothing inside it. Sending the whole evaluate result instead is accepted; the receipt is read out of its verification_context.

  Exemple d'appel

  {"name": "verify_dependency_change", "arguments": {"after": {}, "checks": [], "evaluation": {}}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"tool": "texte", "agent": {}, "status": "texte", "schema_version": "texte"}}

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://repopilot.app/api/mcp