Salesforce-Integration (sumitkrgupta05/Salesforce-Integration) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 5 tools. No publisher has claimed this listing.

Emerging

74/100

Salesforce-Integration

Item: Salesforce-Integration
Rating: 74
Author: M8ven

A production-ready Salesforce integration platform unifying Gemini 3.6 Flash AI, Slack Socket Mode, Gmail, Google Calendar, and Snowflake through Model Context Protocol (MCP).

→ sumitkrgupta05/Salesforce-Integration · listed on github_repo_search

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

⚡ Live Monitored: not connected

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

⚡ Connect GitHub → continuous verification on every push why connect →

Who stands behind it

sumitkrgupta05

Source: github_repo_search

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

GitHub

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

🚨

Secret credentials may flow to a network call

1 flow detected: SLACK_CLIENT_SECRET. We can’t prove the destination matches the brand the credential belongs to.

🔐

You'll be asked for 8 credentials: GEMINI_API_KEY, SF_ACCESS_TOKEN, SF_REFRESH_TOKEN, SLACK_APP_TOKEN, SLACK_BOT_TOKEN, SLACK_CLIENT_SECRET, SLACK_SIGNING_SECRET, SNOWFLAKE_PASSWORD

These are read from process.env at runtime. Make sure you trust where they’ll be sent.

// 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.

configENABLE_SALESFORCE_TOOLS

🔐 secretGEMINI_API_KEY

configGEMINI_MODEL

🔐 secretSF_ACCESS_TOKEN

configSF_CLIENT_ID

configSF_INSTANCE_URL

configSF_LOGIN_URL

configSF_MCP_ENDPOINT_URL

configSF_ORG_ALIAS

🔐 secretSF_REFRESH_TOKEN

🔐 secretSLACK_APP_TOKEN

🔐 secretSLACK_BOT_TOKEN

configSLACK_CLIENT_ID

🔐 secretSLACK_CLIENT_SECRET

configSLACK_DEFAULT_CHANNEL

🔐 secretSLACK_SIGNING_SECRET

configSNOWFLAKE_ACCOUNT

configSNOWFLAKE_DATABASE

🔐 secretSNOWFLAKE_PASSWORD

configSNOWFLAKE_SCHEMA

configSNOWFLAKE_USERNAME

configSNOWFLAKE_WAREHOUSE

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

5/5 tools missing one or more hints — LearnDCMCPAccountAction (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); LearnDCMCPThreadAction (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); LearnDCMCPMeetingAction (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +2 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.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Tool test coverage

Only 1/5 tools referenced in tests (20%)

Write tests that reference each tool by name so every tool has at least one test.

Shell command execution

4 calls in production code run through a shell (src/mcp/salesforceAuth.ts:78, src/mcp/salesforceAuth.ts:87, src/mcp/salesforceAuth.ts:137)

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

Secrets not logged

3 secret values sent to warn/log

Redact or omit secret values from log output.

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 6 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 Score](https://m8ven.ai/badge/mcp/sumitkrgupta05/salesforce-integration)](https://m8ven.ai/mcp/sumitkrgupta05/salesforce-integration)

Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.

commit: 899fbae52eae22f212db59a7360201ad603818a6

code hash: 7dca1bb72ddc2c22000758797b77df70d919350f7e1315cd7245f80c2ea1a20a

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