Is repoctx MCP server safe?

Yes, with the usual care.

B71/100grade B

Safe to use. Minor gaps such as a missing repository or slower maintenance.

No critical or high findings in the latest scan.

How repoctx compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score: 71/100; higher than 36% of 48,255 servers
Tools that change things: 8%; typical: 0%. Fewer write tools means less an agent can break

What its tools let an agent do: 12 read · 1 change

scanner v0.1.9 · 2026-09-24 · same rubric, same numbers if you re-run it

3 medium

Code scan50 source files scanned10/25
–Live reliabilityno gateway calls yet and no remote to proben/a
–Tool poisoningtools not inspected (local package is not executed); not countedn/a
Auth qualitylocal package, no credentials required12/15
Maintenancelast push 0 days ago15/15
Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10

mediumnpm install lifecycle script presentinstall.script

package.json: …: { "start": "node src/cli.js", "postinstall": "node scripts/postinstall.mjs", "mc…

mediumeval / new Function usedexec.eval

src/cli.js: …Hub PR gate", "", "Accuracy eval (v2):", " repoctx eval --accuracy …

Overall 71/100. Components that don't apply are left out of the denominator. Any critical finding is an F.Rubric Appeal a finding JSON

Sem
Entity-level code intelligence: semantic diff, impact analysis, blame, and context for AI agents
not reviewed
Widely used
B