Matrix / Status / Salesforce

Is the Salesforce MCP server down?

No. On 2026-11-02 14:02 PT, api.salesforce.com answered StackMCP's check with an auth challenge (HTTP 401) in 196 ms. That is the normal healthy response. 19 checks since Oct 16 were up.

Status

Up · auth

HTTP

401

Latency

196 ms

Last check

2026-11-02 14:02 PT

Uptime

100% (19 of 19)

Transport

Remote HTTP (hosted by Salesforce; mcp-remote stdio bridge not supported)

Auth

OAuth 2.0 authorization code flow with PKCE via an admin-created External Client App (scopes mcp_api + refresh_token); no DCR, no client-credentials

Endpoint

https://api.salesforce.com/platform/mcp/v1/platform/sobject-all Copy

What we checked

The scheduled check runs once a day, with no credentials and no API key. This log has 23 runs on 19 days, and 4 of those days have more than one run. Each run sends one MCP initialize request. HTTP 401 with an auth challenge means the server is up and wants a sign-in. That result is labeled Up · auth. HTTP 200 means the server answered without asking for a sign-in. A timeout, a 5xx response, or a 404 is a problem. Another code is labeled Unknown, because the check could not tell. The check only shows that the MCP endpoint answered. It does not show that Salesforce's app is working.

Resource metadata: https://api.salesforce.com/.well-known/oauth-protected-resource

Last 19 checks

19 stored checks, newest first. Times are Pacific Time.

Last change

Up · auth since Oct 16. No later status change is stored.

Newest changelog entry for Salesforce, 2026-11-02: Salesforce standard servers do not let you turn tools off.

Is Salesforce itself down?

Salesforce publishes its own status page: Trust Status. Checked 2026-11-02.

Our check only shows that the MCP endpoint answers. If Salesforce's app is down, your connector can fail even when this page says up.

Up here but your Salesforce connector still fails?

• Salesforce's authentication troubleshooting page says to make the callback URL match exactly, and that the client must support an OAuth flow compatible with Salesforce Hosted MCP Servers. It does not name a specific error code. The setup pages do name the settings that have to be on. See the Salesforce page.
• Sign-in looks finished and calls still fail. On the External Client App, select Issue JSON Web Token (JWT)-based access tokens for named users, then disconnect and connect again. See the Salesforce page.
• The callback does not match. The URL in the client and the URL on the External Client App have to be the same. For Cursor, add http://localhost:8787/callback. If your Cursor version also uses cursor://anysphere.cursor-mcp/oauth/callback, add that too. See the Salesforce page.
• Nothing is available yet. The External Client App can take up to 30 minutes to become usable. The server also stays off until an administrator activates it. See the Salesforce page.
• A Connected App was used. Salesforce says Connected Apps are not supported. Create an External Client App. See the Salesforce page.

MCP status for other tools

• Is the HubSpot MCP server down?
• Is the Pipedrive MCP server down?
• Is the Gong MCP server down?
• Is the Stripe MCP server down?
• Is the Perplexity MCP server down?
• Is the Zapier MCP server down?
• All endpoint status

FAQ

Is the Salesforce MCP server down?

No. On 2026-11-02 14:02 PT, api.salesforce.com answered StackMCP's check with an auth challenge (HTTP 401) in 196 ms. That is the normal healthy response. 19 checks since Oct 16 were up.

What does "Up · auth" or HTTP 401 mean on an MCP status check?

It means the server is up. MCP servers that use OAuth answer an unauthenticated request with 401 and a pointer to their sign-in metadata, so a 401 with an auth challenge is the expected healthy response. It is not an error. A timeout, a 5xx error, or a 404 is what signals a problem. The check only proves the Salesforce MCP endpoint answers. It does not prove Salesforce's app is working, so also check the vendor status page when one is linked here. The check method is on the About page.

The Salesforce MCP server is up, but my connector won't work. What should I check?

Salesforce's authentication troubleshooting page says to make the callback URL match exactly, and that the client must support an OAuth flow compatible with Salesforce Hosted MCP Servers. It does not name a specific error code. The setup pages do name the settings that have to be on. Sign-in looks finished and calls still fail. On the External Client App, select Issue JSON Web Token (JWT)-based access tokens for named users, then disconnect and connect again. The callback does not match. The URL in the client and the URL on the External Client App have to be the same. For Cursor, add http://localhost:8787/callback. If your Cursor version also uses cursor://anysphere.cursor-mcp/oauth/callback, add that too. Nothing is available yet. The External Client App can take up to 30 minutes to become usable. The server also stays off until an administrator activates it. A Connected App was used. Salesforce says Connected Apps are not supported. Create an External Client App.

The scheduled check runs once a day. The count above is every stored check, not one check per day. No credentials are sent. The runner region is not published. The method is on the About page. Setup: Salesforce.