Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

RepoPilot

REMOTE · REPOPILOT.APP · SCANNED SEP 20

Repository evidence for agents before they adopt dependencies, enter codebases, compare, or merge.

Available components

remote · repopilot.app 84
0 this week 84 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability62
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 2369 tokens (~296/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Tools include usage examples.Pass
Stability & Change Management94
  • Stability check failed: schema churn in the 30 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage93
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 75% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the RepoPilot MCP server?

RepoPilot is a hosted endpoint at https://repopilot.app/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · repopilot.app

# add to Claude Code
claude mcp add --transport http app-repopilot-repopilot 'https://repopilot.app/api/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "app-repopilot-repopilot": {
      "url": "https://repopilot.app/api/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "app-repopilot-repopilot": {
      "type": "http",
      "url": "https://repopilot.app/api/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.app-repopilot-repopilot]
url = "https://repopilot.app/api/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-repopilot-repopilot": {
      "type": "remote",
      "url": "https://repopilot.app/api/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add app-repopilot-repopilot --url 'https://repopilot.app/api/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  app-repopilot-repopilot:
    url: "https://repopilot.app/api/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "app-repopilot-repopilot": {
      "Transport": "http",
      "Url": "https://repopilot.app/api/mcp"
    }
  }
}
# add to Vellum
assistant mcp add app-repopilot-repopilot -t streamable-http -u 'https://repopilot.app/api/mcp'
// mcp.json
{
  "mcpServers": {
    "app-repopilot-repopilot": {
      "type": "http",
      "url": "https://repopilot.app/api/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 18 Sept 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “get_artifact” rewrote its description, which is the text the model reads security
    • Server version: 2.5.1 → 2.5.4 functional
    • “analyze_repo” added an optional parameter “owner” cosmetic
    • “check_dependency” added an optional parameter “owner” cosmetic
    • “get_artifact” added an optional parameter “owner” cosmetic
    • “plan_repo_task” added an optional parameter “owner” cosmetic
    • “get_artifact” reworded the description of “format” cosmetic
  • 4 Sept 26 0
    • A breaking change shipped without a version bump: still 2.5.1 ▼ security
    • Tool “evaluate_dependency_change” rewrote its description, which is the text the model reads security
    • “evaluate_dependency_change” changed the type of “from_version”: string|null → string|number|null ▼ functional
    • “evaluate_dependency_change” changed the type of “to_version”: string → string|number ▼ functional
    • “evaluate_dependency_change” reworded the description of “dependency” cosmetic
    • “evaluate_dependency_change” reworded the description of “from_version” cosmetic
    • “evaluate_dependency_change” reworded the description of “to_version” cosmetic
  • 3 Sept 26 −1
    • Stability: pass → fail ▼ security
  • 1 Sept 26 0
    • Stability: 0.97 → pass security
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: excellent → good functional
    • Server version: 2.5.0 → 2.5.1 functional
    • “evaluate_dependency_change” reworded the description of “dependency” cosmetic
    • “evaluate_dependency_change” reworded the description of “dependency_type” cosmetic
    • “evaluate_dependency_change” reworded the description of “to_version” cosmetic
    • “verify_dependency_change” reworded the description of “evaluation” cosmetic
  • 31 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Aug 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “evaluate_dependency_change” rewrote its description, which is the text the model reads security
    • “evaluate_dependency_change” added a required parameter “dependency”, so existing callers break ▼ functional
    • “evaluate_dependency_change” dropped the required parameter “change” ▼ functional
    • Server version: 2.4.0 → 2.5.0 functional
    • “evaluate_dependency_change” added an optional parameter “dependency_type” cosmetic
    • “evaluate_dependency_change” added an optional parameter “from_version” cosmetic
    • “evaluate_dependency_change” added an optional parameter “package_manager” cosmetic
    • “evaluate_dependency_change” added an optional parameter “to_version” cosmetic
    • “evaluate_dependency_change” reworded the description of “intent” cosmetic
    • “evaluate_dependency_change” reworded the description of “policy_profile” cosmetic
    • “evaluate_dependency_change” reworded the description of “project” cosmetic
  • 27 Aug 26 +1
    • Server version: 2.3.0 → 2.4.0 functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Probed https://repopilot.app/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=repopilot.app CN=YR1,O=Let's Encrypt,C=US 7 Sept 2026 6 Dec 2026 RSA 2048 SHA256-RSA 52791323cf15fda88288c4ecae68fabcd0a
SANs: repopilot.app
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of repopilot.app. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
app. present 23684 8 Verified
repopilot.app. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline' https://va.vercel-scripts.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob: https:; font-src 'self' data:; connect-src 'self' https://api.github.com https://vitals.vercel-insights.com; frame-ancestors 'none'; form-action 'self'; base-uri 'self'; object-src 'none'; upgrade-insecure-requests
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), interest-cohort=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://repopilot.app/api/mcp Verified 200
http (plaintext) http://repopilot.app/api/mcp HTTPS enforced 308 https://repopilot.app/api/mcp
MCP tools · 8 exposed · ~1,882 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
analyze_repo ~165

CALL when entering an unfamiliar repository or deciding whether to depend on, fork, learn from, or deploy it. Returns a concise four-use-case brief, watchouts, evidence confidence, architecture summary, freshness, and next actions without dumping the full generated artifact. Use get_artifact when file-level orientation is needed. Pass exactly one of repo or package.

NameTypeReqDescription
ownerstring–Repository owner, when repo carries only the bare name. Optional: prefer the single owner/repo form in repo.
packagestring–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.
repostring–Public GitHub repository as owner/repo or a github.com URL.
NameTypeReqDescription
agentobjectyes–
schema_versionstringyes–
statusstringyes–
toolstringyes–

No examples provided.

check_change_risk ~186

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.

NameTypeReqDescription
base_shastring––
contract_idstring–Optional short-lived contract_id returned by plan_repo_task.
diffstring–Raw unified git diff to score directly.
filesarray–Privacy-preserving changed-file facts; contains no source or diff hunks.
head_shastring––
prnumber|string–Positive pull request number, used with repo.
proofsarray––
repostring–owner/repo or a github.com URL.
NameTypeReqDescription
agentobjectyes–
schema_versionstringyes–
statusstringyes–
toolstringyes–

No examples provided.

check_dependency ~184

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.

NameTypeReqDescription
ownerstring–Repository owner, when repo carries only the bare name. Optional: prefer the single owner/repo form in repo.
packagestring–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.
repostring–Public GitHub repository as owner/repo or a github.com URL.
NameTypeReqDescription
agentobjectyes–
schema_versionstringyes–
statusstringyes–
toolstringyes–

No examples provided.

compare_repos ~117

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.

NameTypeReqDescription
astringyesFirst repo or npm package target.
bstringyesSecond repo or npm package target.
NameTypeReqDescription
agentobjectyes–
schema_versionstringyes–
statusstringyes–
toolstringyes–

No examples provided.

evaluate_dependency_change ~673

CALL immediately before adding or upgrading an npm dependency. Answers "is this exact version safe to take on" from registry metadata, advisory deltas, 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.

NameTypeReqDescription
dependencystringyesA 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-leve…
dependency_typestring–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 m…
from_versionstring|number|null–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.
intentstring–Optional free text describing why you are making this change. Advisory only; it changes no verdict.
package_managerstring–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.
policy_profilestring–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 wou…
projectobject–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…
to_versionstring|number–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 acce…
NameTypeReqDescription
agentobjectyes–
schema_versionstringyes–
statusstringyes–
toolstringyes–
{"dependency":"lodash","to_version":"4.17.21"}
{"dependency":"express","from_version":"4.18.2","to_version":"^5.0.0"}
{"dependency":"zod","policy_profile":"strict","project":{"direct_dependencies":{"zod":"^3.22.0"},"installed_versions":{"zod":"3.22.4"},"node_version":"20.11.0","package_manager":"pnpm","scripts":["build","test"]},"to_version":"3.23.8"}
get_artifact ~217

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.

NameTypeReqDescription
formatstring–Optional. markdown for CLAUDE.md-style guidance (the default); cursor for .mdc rules.
ownerstring–Repository owner, when repo carries only the bare name. Optional: prefer the single owner/repo form in repo.
packagestring–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.
repostring–Public GitHub repository as owner/repo or a github.com URL.
NameTypeReqDescription
agentobjectyes–
schema_versionstringyes–
statusstringyes–
toolstringyes–
{"repo":"vercel/next.js"}
{"format":"cursor","repo":"vercel/next.js"}
{"package":"lodash"}
plan_repo_task ~201

CALL before editing an unfamiliar public repository. Returns a bounded reading order, relevant files, dependency consumers, test/verification obligations, analyzed-vs-checked SHA relation, evidence provenance, and a short-lived verification contract. Task text is used only for bounded local matching and is never persisted raw.

NameTypeReqDescription
checked_shastring––
intentobject––
max_filesinteger––
ownerstring–Repository owner, when repo carries only the bare name. Optional: prefer the single owner/repo form in repo.
packagestring–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.
path_hintsarray–Optional repository-relative files or directories to prioritize.
repostring–Public GitHub repository as owner/repo or a github.com URL.
taskstringyes–
NameTypeReqDescription
agentobjectyes–
schema_versionstringyes–
statusstringyes–
toolstringyes–

No examples provided.

verify_dependency_change ~139

CALL after changing the manifest/lockfile and running local checks. Compares the exact evaluated target with the resolved result and caller-reported proof receipts, reports missing/failed evidence and residual risk, and labels receipts as caller asserted. It never runs commands or stores diff/check output.

NameTypeReqDescription
afterobjectyes–
checksarrayyes–
diffstring––
evaluationobjectyesThe 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 resul…
NameTypeReqDescription
agentobjectyes–
schema_versionstringyes–
statusstringyes–
toolstringyes–

No examples provided.

Common questions

What is the RepoPilot MCP server?

RepoPilot is an MCP server listed in the public MCP registry as app.repopilot/repopilot. Repository evidence for agents before they adopt dependencies, enter codebases, compare, or merge. This page covers its hosted endpoint (https://repopilot.app/api/mcp).

Is the RepoPilot MCP server safe to use?

RepoPilot scores 84 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the RepoPilot MCP server expose?

RepoPilot exposes 8 tools: check_dependency, evaluate_dependency_change, verify_dependency_change, analyze_repo, plan_repo_task, and 3 more. Their descriptions and schemas cost roughly 1,882 tokens of context every time the server is loaded.

Does the RepoPilot MCP server require authentication?

No. We connected to RepoPilot without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the RepoPilot MCP server still maintained?

RepoPilot is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.