# Salesforce (oci · ghcr.io/wyre-ai/salesforce-mcp:v1.0.4)

MCP server for Salesforce CRM — Accounts, Contacts, Opportunities, Leads, Cases.

- Trust score: 49/100 (low)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- oci · `ghcr.io/wyre-ai/salesforce-mcp:v1.0.4`: 49/100 (this document), [markdown](https://verifymcp.io/servers/wyre-ai-salesforce-mcp/ghcr-io-wyre-ai-salesforce-mcp-v1-0-4.md), [page](https://verifymcp.io/servers/wyre-ai-salesforce-mcp/ghcr-io-wyre-ai-salesforce-mcp-v1-0-4)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/wyre-ai/salesforce-mcp:v1.0.4`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Supply Chain Security**: 0/100
  - Malware scan not yet available for this package.
  - Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.
- **Provenance & Transparency**: 32/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: the license (NOASSERTION) isn't a recognized OSI-approved license.
  - Actively maintained (last published 26 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 80/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 541 tokens (~90/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 87/100
  - Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "salesforce_query_records" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the Salesforce MCP server?

Salesforce runs locally as a container image, launched with docker run --rm -i ghcr.io/wyre-ai/salesforce-mcp:v1.0.4. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add wyre-ai-salesforce-mcp -- docker run --rm -i ghcr.io/wyre-ai/salesforce-mcp:v1.0.4
```

### Cursor

```json
{
  "mcpServers": {
    "wyre-ai-salesforce-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-ai/salesforce-mcp:v1.0.4"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "wyre-ai-salesforce-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-ai/salesforce-mcp:v1.0.4"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add wyre-ai-salesforce-mcp -- docker run --rm -i ghcr.io/wyre-ai/salesforce-mcp:v1.0.4
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "wyre-ai-salesforce-mcp": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-ai/salesforce-mcp:v1.0.4"
      ],
      "enabled": true
    }
  }
}
```

### Hermes

```yaml
mcp_servers:
  wyre-ai-salesforce-mcp:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/wyre-ai/salesforce-mcp:v1.0.4"]
```

### Netclaw

```json
{
  "McpServers": {
    "wyre-ai-salesforce-mcp": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-ai/salesforce-mcp:v1.0.4"
      ]
    }
  }
}
```

### Other

```json
{
  "mcpServers": {
    "wyre-ai-salesforce-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-ai/salesforce-mcp:v1.0.4"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 49, +1)

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

### 2026-09-17 (score 48, +1)

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

### 2026-09-15 (score 47, +1)

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

### 2026-09-13 (score 46, +1)

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

### 2026-09-11 (score 45, +1)

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

### 2026-09-09 (score 44, +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.

### 2026-09-07 (score 43, +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.

### 2026-09-04 (score 42, +1)

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

## MCP tools (6)

### `salesforce_search_objects` (~72 tokens)

Search Salesforce objects by partial name. Returns matching standard and custom objects. Use this to discover which objects to query before describing or querying them. Example: "Account" returns Account, AccountHistory, AccountContactRelation, etc.

Input parameters:

- `pattern` (string, required): Partial object name to search for. Case-insensitive.

### `salesforce_describe_object` (~73 tokens)

Get the full schema for a Salesforce object — all fields with types, labels, picklist values, and relationships. Use before constructing queries to know exact field names.

Input parameters:

- `objectName` (string, required): API name of the Salesforce object (e.g. "Account", "Opportunity", "Custom_Object__c").

### `salesforce_query_records` (~82 tokens)

Execute a SOQL query against Salesforce. Supports parent-to-child and child-to-parent relationship queries. For aggregate queries (GROUP BY, COUNT, SUM), use salesforce_aggregate_query instead.

Input parameters:

- `soql` (string, required): A SOQL SELECT statement. Example: "SELECT Id, Name, Industry FROM Account WHERE Industry = 'Technology' LIMIT 100"

### `salesforce_aggregate_query` (~77 tokens)

Execute a SOQL aggregate query (GROUP BY, COUNT, SUM, AVG, MIN, MAX, COUNT_DISTINCT). Use for reporting / rollups. HAVING clauses supported.

Input parameters:

- `soql` (string, required): A SOQL aggregate query. Example: "SELECT StageName, COUNT(Id) FROM Opportunity GROUP BY StageName"

### `salesforce_dml_records` (~150 tokens)

Perform record-level data operations: insert, update, delete, or upsert. Operates on one object type per call; pass an array of records.

Input parameters:

- `externalIdField` (string): Required for upsert: the API name of the custom external-id field used to match existing records.
- `objectName` (string, required): API name of the Salesforce object to operate on (e.g. "Account", "Contact").
- `operation` (string, required): The DML operation to perform.
- `records` (array, required): Array of record objects. For update/delete: each record must include "Id". For upsert: each record must include the external-id field referenced in `externalIdField`.

### `salesforce_search_all` (~87 tokens)

Cross-object search using SOSL. Searches multiple objects at once for text matches. Use when the customer wants to find a name/email/keyword without knowing which object it lives on.

Input parameters:

- `sosl` (string, required): A SOSL FIND statement. Example: "FIND {acme corp} IN ALL FIELDS RETURNING Account(Id,Name), Contact(Id,Name,Email)"

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/wyre-ai-salesforce-mcp/ghcr-io-wyre-ai-salesforce-mcp-v1-0-4#diagnostics

## Score history

- 2026-09-21: 49
- 2026-09-20: 49
- 2026-09-19: 49
- 2026-09-18: 48
- 2026-09-17: 48
- 2026-09-16: 47
- 2026-09-15: 47
- 2026-09-14: 46
- 2026-09-13: 46
- 2026-09-12: 45
- 2026-09-11: 45
- 2026-09-10: 44
- 2026-09-09: 44
- 2026-09-08: 43
- 2026-09-07: 43
- 2026-09-06: 42
- 2026-09-05: 42
- 2026-09-04: 42
- 2026-09-03: 41
- 2026-09-02: 37
- 2026-09-01: 37
- 2026-08-31: 37
- 2026-08-30: 37
- 2026-08-29: 37
- 2026-08-28: 37
- 2026-08-27: 37
- 2026-08-26: 37

## Common questions

### What is the Salesforce MCP server?

Salesforce is an MCP server listed in the public MCP registry as io.github.WYRE-AI/salesforce-mcp. MCP server for Salesforce CRM, Accounts, Contacts, Opportunities, Leads, Cases. This page covers its container image (ghcr.io/wyre-ai/salesforce-mcp:v1.0.4).

### Is the Salesforce MCP server safe to use?

Salesforce scores 49 out of 100 on VerifyMCP. 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 Salesforce MCP server expose?

Salesforce exposes 6 tools: salesforce_search_objects, salesforce_describe_object, salesforce_query_records, salesforce_aggregate_query, salesforce_dml_records, salesforce_search_all. Their descriptions and schemas cost roughly 541 tokens of context every time the server is loaded.

### Is the Salesforce MCP server still maintained?

Salesforce is still listed as active in the MCP registry. We last reached this channel on 21 September 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 Salesforce MCP server under?

Salesforce declares the NOASSERTION licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.

## Links

- Repository: https://github.com/WYRE-AI/salesforce-mcp
- Changelog RSS feed: https://verifymcp.io/servers/wyre-ai-salesforce-mcp/ghcr-io-wyre-ai-salesforce-mcp-v1-0-4.xml
- Changelog JSON feed: https://verifymcp.io/servers/wyre-ai-salesforce-mcp/ghcr-io-wyre-ai-salesforce-mcp-v1-0-4.json
- HTML version of this page: https://verifymcp.io/servers/wyre-ai-salesforce-mcp/ghcr-io-wyre-ai-salesforce-mcp-v1-0-4
