Offlocal MCP Server
@offlocal/mcp
npm
v0.4.1
Published by @offlocal — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
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 − 7 = 93. 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 |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
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 2
high Shell/command execution in server code (dist/actions.js)MTC-SRC-002
In the server's implementation (`dist/actions.js:52`): 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: const data = await exec(); audit("success"); return { ...base, status: "ok", policy_decision: "allo
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/actions.js
low Unconstrained path parameter "path" on "list_github_repo_files"MTC-CAP-008
Tool "list_github_repo_files" takes a path parameter "path" with no constraint. Without a canonicalize-and-contain check (not visible statically), this permits ../ traversal outside the intended root.
Fix: Resolve and verify the path stays within an allowed root; reject traversal sequences.
Location: tool list_github_repo_files · inputSchema.properties.path
Tools 38
Each tool and what it can reach — statically extracted from the published source.
get_app_logsingests untrusted inputget_github_repo_readmeingests untrusted inputget_railway_logsingests untrusted inputget_vercel_deployment_logsingests untrusted inputget_vercel_logsingests untrusted inputlist_github_repo_filesreads sensitive dataquery_supabasereads sensitive dataread_project_memoryingests untrusted inputadd_environmentno sensitive capabilitycheck_policyno sensitive capability
Show 28 more tools ↓
create_projectno sensitive capabilitycreate_railway_deploymentno sensitive capabilitycreate_stripe_priceno sensitive capabilitycreate_stripe_productno sensitive capabilitycreate_vercel_deploymentno sensitive capabilityget_github_repo_contextno sensitive capabilityget_latest_deployment_logsno sensitive capabilityget_project_contextno sensitive capabilityget_provider_mappingno sensitive capabilityget_railway_deploymentsno sensitive capabilityget_railway_project_contextno sensitive capabilityget_supabase_project_contextno sensitive capabilityget_vercel_deployment_statusno sensitive capabilityget_vercel_deploymentsno sensitive capabilityget_vercel_project_contextno sensitive capabilitylist_audit_logno sensitive capabilitylist_environmentsno sensitive capabilitylist_policy_rulesno sensitive capabilitylist_projectsno sensitive capabilitylist_provider_mappingsno sensitive capabilitylist_stripe_productsno sensitive capabilitylist_supabase_projectsno sensitive capabilitymap_provider_resourceno sensitive capabilityselect_projectno sensitive capabilityset_policy_ruleno sensitive capabilityset_railway_env_varno sensitive capabilityset_vercel_env_varno sensitive capabilitywrite_project_memoryno 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 1
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 |
|---|---|---|---|---|
v0.4.1 latest |
A 93/100 | 2 | 1.8.0 | 2026-07-23 |
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 @offlocal/mcp --onlineMore in Developer Tools
Security scan results for the 1stay MCP server.
Security scan results for the Adguard Home MCP server.
Security scan results for the Ado Browser MCP server.
Security scan results for the Adobe Experience Dev MCP server.
Security scan results for the Aemet MCP server.
Security scan results for the Affinity Mcp Bridge MCP server.