salesforce-mcp-jsforce (imazhar101/salesforce-mcp-jsforce) is an MCP server listed on the M8ven Trust Index. It scores 60 out of 100, grade C. It declares 9 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Caution
60/100

salesforce-mcp-jsforce

Enables SOQL queries, SOSL search, and record CRUD operations on a single Salesforce org via MCP, with optional read-only mode.

→ imazhar101/salesforce-mcp-jsforce· listed on glama

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

imazhar101

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Glamanot scored here

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
⚠️
Known vulnerabilities in dependencies: 3 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 2 credentials: SF_ACCESS_TOKEN, SF_CLIENT_SECRET
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// tools this server exposes9 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

salesforce_identity

Return the identity (user, org, instance) of the supplied token. Use this to confirm the connection is authenticated.

salesforce_query

Run a SOQL query and return matching records.

salesforce_search

Run a SOSL full-text search across objects.

salesforce_list_objects

List all sObjects available in the org with their key metadata.

salesforce_describe_object

Describe an sObject: its fields, types, picklist values, and references (trimmed payload).

salesforce_get_record

Retrieve a single record by Id, optionally limited to specific fields.

salesforce_create_record

Create a new record on the given object.

salesforce_update_record

Update fields on an existing record.

salesforce_delete_record

Delete a record by Id.

// known CVEs in dependencies3 high

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

high@modelcontextprotocol/sdk@1.12.0GHSA-345p-7cg4-v4c7

@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse

high@modelcontextprotocol/sdk@1.12.0GHSA-8r9q-7v3j-jr4g

Anthropic's MCP TypeScript SDK has a ReDoS vulnerability

high@modelcontextprotocol/sdk@1.12.0GHSA-w48q-cv73-mx4w

Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
🔐 secretSF_ACCESS_TOKEN+ SF_INSTANCE_URL environment variables, or
configSF_API_VERSION62.0 REST API version
configSF_CALLBACK_PORT
configSF_CLIENT_IDECA consumer key for login
🔐 secretSF_CLIENT_SECRETonly for confidential apps
configSF_INSTANCE_URLSF_ACCESS_TOKEN + environment variables, or
configSF_LOGIN_URL
configSF_MCP_CONFIG_DIR
configSF_MCP_TRANSPORT
configSF_READONLYSet =1 to register the read tools only.
configSF_SCOPEapi refresh_token OAuth scopes
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

9/9 tools missing one or more hints — salesforce_identity (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); salesforce_query (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); salesforce_search (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +6 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool inputs are validated

6/9 tool handlers declare input schemas (67%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tests exist

No test files found

Add tests that exercise each declared tool.

Production dependencies are patched

0 critical, 3 high severity in production deps — @modelcontextprotocol/sdk@1.12.0 (high), @modelcontextprotocol/sdk@1.12.0 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 5 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/imazhar101/salesforce-mcp-jsforce?variant=verified)](https://m8ven.ai/mcp/imazhar101/salesforce-mcp-jsforce)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: e937f1cbc1b0f375c722f79a45e86890c7dcc803
code hash: 29eeedb089e222356ff7322c3c621b314a9196af276fe80572e3bfc3cef7f956
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client