Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

sf-intelligence: offline Salesforce MCP server

NPM · SF-INTELLIGENCE

Ask your AI what breaks before you change Salesforce. Offline, read-only, cited answers.

Available components

+3 this week 85 Trust /100

Last scanned (20 hours ago)

Scores higher than 87% of npm servers

Category CRM and Sales

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 33 of 145 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to PranavNagrecha/Salesforce-Intelligence). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 15 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability76
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 213 tokens (~213/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management63
  • Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 0
    • Package version: 0.5.0 → 0.8.0 functional
  • 30 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 26 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 24 Oct 26 −5
    • CVE-2023-54404 affects this package: high ▼ security
    • Known CVEs: pass → fail ▼ security
  • 23 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 4 Nov 2026 · Analysed npm/sf-intelligence@0.8.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo PranavNagrecha/Salesforce-Intelligence
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/PranavNagrecha/Salesforce-Intelligence/.github/workflows/publish.yml@refs/tags/v0.8.0
Rekor log index 3326317235
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:c1216a3d570ec7f0b148bb94e755093c595152dfdf7125f46a4c2fee6778f9b6942c5dba4cba962e0ba28fca72547e9ef4b53a36a5c0fc756a9900641

Background: How many MCP packages publish verified provenance →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 145 packages
Packages resolved 145
Stale 33
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 1 exposed · ~81 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
sfi.setup_status ~81

Report why sf-intelligence has no usable knowledge base in this session (none built yet, an unfinished build, or a configured vault path that does not exist), and the exact ordered commands to fix it. Read-only; runs nothing. Call this before telling the user anything about their Salesforce org — in this state the server has no org data at all.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the sf-intelligence: offline Salesforce MCP server server?

sf-intelligence: offline Salesforce MCP server runs locally as an npm package, launched with npx -y sf-intelligence. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · sf-intelligence

# add to Claude Code
claude mcp add pranavnagrecha-salesforce-intelligence -- npx -y sf-intelligence
Common questions

What is the sf-intelligence: offline Salesforce MCP server server?

sf-intelligence: offline Salesforce MCP server is listed in the public MCP registry as io.github.PranavNagrecha/salesforce-intelligence. Ask your AI what breaks before you change Salesforce. Offline, read-only, cited answers. This page covers its npm package (sf-intelligence).

Is the sf-intelligence: offline Salesforce MCP server server safe to use?

sf-intelligence: offline Salesforce MCP server scores 85 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 4 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the sf-intelligence: offline Salesforce MCP server server expose?

sf-intelligence: offline Salesforce MCP server exposes 1 tool: sfi.setup_status. Their descriptions and schemas cost roughly 81 tokens of context every time the server is loaded.

Is the sf-intelligence: offline Salesforce MCP server server still maintained?

sf-intelligence: offline Salesforce MCP server is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the sf-intelligence: offline Salesforce MCP server server under?

sf-intelligence: offline Salesforce MCP server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.