Salesforce

A live handshake means the URL answered an MCP initialize as a server on the probe date. It is liveness and nothing more: nobody has run its tools. A tool being catalogued means a server names it, by answering tools/list, in its own source, or in the vendor's documentation. None of them has been called. A tool count of 0 means not measured, never zero tools.

Salesforce (core CRM/platform) + Agentforce

A cloud CRM/platform for managing sales, service, and marketing records via a database, APIs, and a low-code app layer, with Agentforce as a layer on top for configuring autonomous AI agents that read Salesforce data, decide on an action, and execute it or...

Salesforce Einstein Forecasting

Sales Cloud's AI forecasting feature, analyzing past opportunities, account history, and activities plus rep win-rates to generate revenue predictions with confidence ranges. See 06-revops-infra.md for Salesforce's full platform entry (Agentforce, Hosted MCP...

2 of 2 enterprise only, API access needs a contract.

The gate is the api_gate field on each product entry, established by hand on the last_checked date shown above. It records whether a solo operator can get API access without a contract. Money is not tracked.

• Run an autonomous SDR agent
• Answer an inbound chat or call
• Read CRM records
• Write CRM records
• Run an automation workflow
• Read the pipeline forecast

6 distinct job labels, the union across 2 products, tagged 2026-08-25. A job tag means the vendor says the tool does this. It is not a test result, not proof the capability is reachable through the tool's MCP server, and not proof it is available on the gate this entry records.

• https://github.com/salesforcecli/mcp (Salesforce (core CRM/platform) + Agentforce, docs page, probed 2026-09-04)

An endpoint is where an agent connects. A docs page is where a person reads about connecting. Both are published because both are what the probe found; an agent needs the first.

Salesforce (core CRM/platform) + Agentforce sf official CLI

npm install -g @salesforce/cli

quoted from https://www.npmjs.com/package/@salesforce/cli on 2026-09-27, via npm

harvested 2026-09-27, all on the tool page.

A CLI being listed means the harvest found an install command or a package on a stated date. Nobody has run it. Every command is quoted verbatim from the URL beneath it.

github.com/salesforcecli

github.com/salesforcecli tied to the vendor by rule 1, account website https://developer.salesforce.com/tools/salesforcecli has the vendor's domain, confidence strong

The five most recently pushed, on 2026-09-08:

Kind is a heuristic guessed from the repository name, topics and description, not a fact the vendor stated. A repository count is activity, not a verdict. Read 2026-09-08.

github.com/salesforce

github.com/salesforce tied to the vendor by rule 3, account website https://opensource.salesforce.com has the vendor's domain, confidence strong

The five most recently pushed, on 2026-09-08:

Kind is a heuristic guessed from the repository name, topics and description, not a fact the vendor stated. A repository count is activity, not a verdict. Read 2026-09-08.

A job tag is a vendor claim: it means the vendor says the product does this, and it is not a test result. A listed tool has not been run: the catalogue says what an agent could try, not what works. 1 of 1,252 directory entries are bench tested, meaning somebody personally ran the tool on a stated date, and 0 of this vendor's 2 products are among them. There is no verdict here on whether this vendor is better than another.

Vendor pages group the directory's canonical product entries by vendor_domain. The vendor name is the product display name that matches the domain when several products share it; nothing on this page is typed by hand. Data baked 2026-09-27 by build_directory.py (phase 1).