Salesforce (advanced-communities) MCP Server

@advanced-communities/salesforce-mcp-server npm v1.6.6

Published by @advanced-communities — 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.

MCP server enabling AI assistants to interact with Salesforce orgs through the Salesforce CLI

Trust grade
A
93/100
Last scanned get badge →
Trust
A · 93/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 93/100

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:

PointsAdoption-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 5

high Tool "run_code_analyzer" exposes command/code executionMTC-CAP-001

Tool "run_code_analyzer" appears to run shell commands or evaluate code (keyword "run_code" in tool name). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.

Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.

Location: tool run_code_analyzer

high Shell/command execution in server code (build/tools/records.js)MTC-SRC-002

In the server's implementation (`build/tools/records.js:5`): 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: ort { exec } from "node:child_process"; import { platform } from "node:os"; import z from "zod"; /** * Wraps a Zod obje

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 build/tools/records.js

high Shell/command execution in server code (build/utils/sfCommand.js)MTC-SRC-002

In the server's implementation (`build/utils/sfCommand.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: ort { exec } from "node:child_process"; import { platform } from "node:os"; import { existsSync } from "node:fs"; 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 build/utils/sfCommand.js

medium Untrusted input can drive an external actionMTC-FLOW-005

Untrusted-input tools ([apex_log_list, apex_get_log]) co-exist with external-action tools ([run_code_analyzer]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.

Evidence: untrusted [apex_log_list, apex_get_log] → sinks [run_code_analyzer]

Fix: Require confirmation for state-changing/egress actions triggered after processing untrusted content.

Location: flow apex_log_list → run_code_analyzer

low Mutating tool "run_code_analyzer" declares no destructiveHintMTC-CAP-005

Tool "run_code_analyzer" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool run_code_analyzer

Tools 41

Each tool and what it can reach — statically extracted from the published source.

  • apex_get_logingests untrusted input
  • apex_log_listingests untrusted input
  • run_code_analyzerruns code / shell
  • assign_permission_setno sensitive capability
  • assign_permission_set_licenseno sensitive capability
  • clear_default_orgno sensitive capability
  • create_recordno sensitive capability
  • delete_recordno sensitive capability
  • deploy_startno sensitive capability
  • display_userno sensitive capability
Show 31 more tools ↓
  • execute_anonymous_apexno sensitive capability
  • generate_classno sensitive capability
  • generate_componentno sensitive capability
  • generate_frontdoor_urlno sensitive capability
  • generate_triggerno sensitive capability
  • get_apex_code_coverageno sensitive capability
  • get_apex_test_resultsno sensitive capability
  • get_default_orgno sensitive capability
  • get_server_permissionsno sensitive capability
  • install_skillno sensitive capability
  • list_code_analyzer_rulesno sensitive capability
  • list_connected_salesforce_orgsno sensitive capability
  • list_metadatano sensitive capability
  • list_metadata_typesno sensitive capability
  • login_into_orgno sensitive capability
  • logoutno sensitive capability
  • openno sensitive capability
  • open_recordno sensitive capability
  • package_installno sensitive capability
  • package_uninstallno sensitive capability
  • query_recordsno sensitive capability
  • query_records_to_fileno sensitive capability
  • run_apex_testsno sensitive capability
  • scanner_runno sensitive capability
  • scanner_run_dfano sensitive capability
  • schema_generate_tabno sensitive capability
  • search_recordsno sensitive capability
  • set_default_orgno sensitive capability
  • sobject_describeno sensitive capability
  • sobject_listno sensitive capability
  • update_recordno sensitive capability

Toxic flows 1

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

What this scan could not see

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.

VersionScoreFindingsEngineScanned
v1.6.6 latest A 93/100 5 1.13.0 2026-09-07

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.

MCP Trust Score: A · 93/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/advanced-communities-salesforce-mcp-server/badge.svg)](https://mcptrustchecker.com/registry/advanced-communities-salesforce-mcp-server)
HTML
<a href="https://mcptrustchecker.com/registry/advanced-communities-salesforce-mcp-server"><img src="https://mcptrustchecker.com/registry/advanced-communities-salesforce-mcp-server/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/advanced-communities-salesforce-mcp-server/badge.json via https://img.shields.io/endpoint?url=…

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 @advanced-communities/salesforce-mcp-server --online

Use the free API → How scoring works

Other implementations of Salesforce 26

Independent packages implementing the same tool, scanned with the same engine. Compare all 27 side by side →

More in Business & CRM