Repolens MCP Server
@sameermir/repolens-mcp
npm
v1.0.2
Source verified
Published by sameer2191 — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.
Local-first repository intelligence MCP server with multi-agent setup, executable agent hook reminders, persistent config, project catalog, fleet summaries, cross-repo graphing, fleet graph artifacts, graph package bootstrap, optional startup auto-indexin
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 6 = 94. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 5
high Shell/command execution in server code (dist/src/core/store.js)MTC-SRC-002
In the server's implementation (`dist/src/core/store.js:2`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: spawnSync } from "node:child_process"; import path from "node:path"; import { DatabaseSync } from "node:sqlite"; import
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/src/core/store.js
high Shell/command execution in server code (dist/src/core/watcher.js)MTC-SRC-002
In the server's implementation (`dist/src/core/watcher.js:1`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: { execFile } from "node:child_process"; import crypto from "node:crypto"; import fs from "node:fs"; import path from "no
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/src/core/watcher.js
low Shell/command execution in packaging/dev tooling (scripts/installer-audit.mjs)MTC-SRC-002
In a packaging/dev/install script (shipped, but not the server runtime) (`scripts/installer-audit.mjs:3`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: spawnSync } from "node:child_process"; import fs from "node:fs"; import os from "node:os"; import path from "node:path"
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server scripts/installer-audit.mjs
low Shell/command execution in packaging/dev tooling (scripts/package-contents-gate.mjs)MTC-SRC-002
In a packaging/dev/install script (shipped, but not the server runtime) (`scripts/package-contents-gate.mjs:3`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: ecFileSync } from "node:child_process"; import fs from "node:fs"; const requiredFiles = [ "README.md", "LICENSE",
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server scripts/package-contents-gate.mjs
low Shell/command execution in packaging/dev tooling (scripts/run-tsc.mjs)MTC-SRC-002
In a packaging/dev/install script (shipped, but not the server runtime) (`scripts/run-tsc.mjs:3`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: spawnSync } from "node:child_process"; import path from "node:path"; import { fileURLToPath } from "node:url"; const r
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server scripts/run-tsc.mjs
Tools 38
Each tool and what it can reach — statically extracted from the published source.
agent_setupno sensitive capabilityarchitecture_reportno sensitive capabilitybenchmark_repositoryno sensitive capabilitycontext_packno sensitive capabilitycross_repo_graphno sensitive capabilitydelete_decisionno sensitive capabilitydelete_projectno sensitive capabilitydetect_changesno sensitive capabilityexport_graph_packageno sensitive capabilityfind_communitiesno sensitive capability
Show 28 more tools ↓
find_dead_codeno sensitive capabilityfind_dependency_cyclesno sensitive capabilityfind_referencesno sensitive capabilityfleet_summaryno sensitive capabilityget_architectureno sensitive capabilityget_code_snippetno sensitive capabilityget_graph_schemano sensitive capabilitygraph_snapshotno sensitive capabilityimpact_analysisno sensitive capabilityimport_graph_packageno sensitive capabilityindex_repositoryno sensitive capabilityindex_statusno sensitive capabilityingest_tracesno sensitive capabilitylist_decisionsno sensitive capabilitylist_projectsno sensitive capabilitymanage_configno sensitive capabilityquery_graphno sensitive capabilityremember_decisionno sensitive capabilityscan_secretsno sensitive capabilitysearch_codeno sensitive capabilitysearch_graphno sensitive capabilitysearch_symbolsno sensitive capabilitysemantic_searchno sensitive capabilitytrace_pathno sensitive capabilitytrace_symbolno sensitive capabilityupdate_decisionno sensitive capabilityvector_searchno sensitive capabilityversion_statusno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (38 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 2
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v1.0.2 latest |
A 94/100 | 5 | 1.13.0 | 2026-09-09 |
v1.0.1 |
A 93/100 | 5 | 1.12.1 | 2026-07-27 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan @sameermir/repolens-mcp --onlineMore in Developer Tools
Hotel booking MCP server — 300K+ properties, real confirmation numbers, loyalty programs. Builders monetize every booking via Stripe Connect. The first MCP server that completes real hotel reservations inside AI conversations.
Manage AdGuard Home through AI assistants
Read-only Azure DevOps for MCP clients using only your existing browser session — no PAT, no Azure CLI. Browse work items, pull requests, comments, attachments and Artifacts feeds across every project, repo and feed you can access.
MCP server for Adobe Experience Manager Assets integration development
Servidor MCP para el tiempo oficial de España (API pública OpenData de AEMET). Predicción, observación y avisos como herramientas MCP tipadas.
A standalone MCP stdio bridge for Affinity by Canva's local MCP SSE server.