bc-code-intelligence-mcp
npm
v1.7.6
Published by jeremyvyska — 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.
BC Code Intelligence MCP Server - Complete Specialist Bundle with AI-driven expert consultation, seamless handoffs, and context-preserving workflows
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.
In the server's implementation (`dist/config/config-validator.js:391`): Reading private keys / cloud credentials, or serializing the whole environment, is a sensitive-data source that becomes exfiltration when combined with any egress. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: suggestion: 'Use ~/.ssh/id_rsa format' }); } break; case
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/config/config-validator.js
In the server's implementation (`dist/layers/git-layer.js:317`): 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: cSync } = await import("child_process"); try { execSync("gh --version", { stdio: "ignore" });
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/layers/git-layer.js
Each tool and what it can reach — statically extracted from the published source.
analysis_focusno sensitive capabilityapp_sourceno sensitive capabilityapp_takeoverno sensitive capabilityarchitecture_reviewno sensitive capabilityaudit_scopeno sensitive capabilitybug_contextno sensitive capabilitybug_investigationno sensitive capabilitycode_locationno sensitive capabilitycode_optimizationno sensitive capabilitycurrent_structureno sensitive capabilitycurrent_versionno sensitive capabilitydata_flow_tracingno sensitive capabilitydev_onboardingno sensitive capabilityexperience_levelno sensitive capabilityfocus_areano sensitive capabilityfull_reviewno sensitive capabilityintegration_designno sensitive capabilityintegration_typeno sensitive capabilityissue_severityno sensitive capabilitymodularization_goalno sensitive capabilitymonolith_to_modulesno sensitive capabilityperf_reviewno sensitive capabilityperformance_concernno sensitive capabilityreview_depthno sensitive capabilityreview_targetno sensitive capabilityscopeno sensitive capabilitysecurity_auditno sensitive capabilityspec_analysisno sensitive capabilityspec_sourceno sensitive capabilitytakeover_contextno sensitive capabilitytarget_versionno sensitive capabilitytesting_scopeno sensitive capabilitytesting_strategyno sensitive capabilitytrace_scopeno sensitive capabilitytrace_targetno sensitive capabilityupgrade_planningno sensitive capabilityScan 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.7.6 latest |
A 93/100 | 2 | 1.13.0 | 2026-09-07 |
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.
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 bc-code-intelligence-mcp --online
Free public tax reference data — GST/VAT, income, company and capital-gains tax rules for 50+ countries.
The approval gate for unattended UCP buying agents — a policy/approval MCP proxy in front of a merchant's UCP checkout endpoint.
Autotask PSA MCP server. Generic entity query/get/create/update across the full REST API plus convenience tools for tickets, companies, contacts, projects, tasks and time entries. AI-safe with readonly mode and destructive-action confirmation. stdio + opt
MCP server for B2C Commerce developer experience tools
Search, compare and contact real-world companies through a public MCP business directory.
Norwegian business register (Brønnøysundregistrene) as an MCP server — companies, roles, subunits and annual accounts, with the register's silent traps encoded as guards.