# Revenue.io: MCP server status, API access gate and what it does > Salesforce-native AI-guided-selling platform whose forecasting product reads live Salesforce opportunity data... No MCP found, Enterprise only. Checked 2026-09-02. *Markdown twin of the HTML page at the same path. Same content, no navigation, no styling, no scripts. Links below point at other twins. Site map for machines: [llms.txt](../llms.txt). The whole dataset: [directory.json](../data/directory.json).* *Maintained by Andrew McGuire (https://andrewcmcguire.com), who also publishes https://gtmsignals.co and https://justsaid.ai.* --- [Directory](../index.md) / [Forecasting & Revenue](../categories/forecasting-revenue.md) / Revenue.io # Revenue.io [No MCP found](../mcp/none-found.md) [Enterprise only](../gates/enterprise-only.md) [Forecasting & Revenue](../categories/forecasting-revenue.md) RESEARCHED Checked 2026-09-02 > **RESEARCHED** Facts from public sources with URLs. No usage claims. Nobody has run this tool. The other tier is BENCH-TESTED, which means Andrew personally ran the tool on a stated date and cannot be bought at any price. Across the whole directory that count is 1. Vendor: [revenue.io](https://revenue.io) · entry id 12-revenue-io · source 12-forecasting-revenue.md line 264 **What it does** Salesforce-native AI-guided-selling platform whose forecasting product reads live Salesforce opportunity data to produce automatic rep/manager/VP forecast roll-ups without CSV exports or manual sync. **AI features, separated from automation with an AI label on it** Conversation intelligence (auto-transcribes/scores Salesforce-dialer calls, surfaces deal risk in real time); deal-health scoring that flags forecast risk and sits "as a peer voice" alongside reps/managers rather than replacing their number with a single AI figure; sentiment analysis mapping rep sentiment trends to pipeline-stage movement. Genuinely call-derived signals, not just CRM-field math. **RevOps role** Salesforce-embedded forecasting-plus-conversation-intelligence layer, positioned as an always-current forecast (no separate report to maintain) rather than a standalone forecasting platform. **MCP server** - **Status bucket**: No MCP found - **Auth**: n/a - **Parsed URLs**: 0 found in the mcp_url field No server was found at the time of the check. That is a statement about the search, not a promise that none exists. The status was established on 2026-09-02. mcp_status, verbatim from the file: none-found mcp_url, verbatim from the file: none **Command line** No CLI found by the 2026-09-27 harvest across vendor docs, npm, PyPI, Homebrew and GitHub. That is a probe result, not proof of absence. **Access gate** - **Gate bucket**: Enterprise only - **Can a solo operator reach it**: Not without a contract api_gate, verbatim from the file: enterprise-only (the pricing page states a custom quote is built on the demo call rather than published as a list price; an API exists and the support site documents APIs and Programmatic Operations for Guided Selling, but no plan condition is published) **API documentation** No documentation URL recorded. 727 of 1252 entries are in the same position. Blank is legal and it is published as blank. **GitHub health** Not measured. github_url, github_stars, github_last_commit and github_archived are null on every entry in this build. The refresh rail specced in SPEC section 7.2 has not been run. An unstamped star count is a lie, so nothing is shown rather than something stale. **On GitHub** No GitHub organisation could be tied to revenue.io with evidence on 2026-09-08. Recorded by the harvest: github candidates were seen but none passed the evidence rules. 5 candidate accounts seen and rejected by the evidence rules: RevenueCat, hmrc, Revenue-Academy, IRS-Public, PrimeRevenue. A name match alone is never accepted; the account has to point at the vendor domain. **Jobs it can do** - [Place an outbound call](../jobs/place-outbound-call.md) - [Fetch a call transcript](../jobs/fetch-call-transcript.md) - [Extract deal signals from calls](../jobs/extract-deal-signals-from-calls.md) - [Read the pipeline forecast](../jobs/read-pipeline-forecast.md) 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. Tagged by machine-pass on 2026-08-25 against the closed 56 job vocabulary. 271 of 1,252 entries carry at least one tag; 849 tags are assigned in total. **Sources** - [https://www.revenue.io/forecasting](https://www.revenue.io/forecasting) - [https://www.revenue.io/faqs](https://www.revenue.io/faqs) - [https://www.vendr.com/marketplace/revenue-io](https://www.vendr.com/marketplace/revenue-io) - [https://www.pulsemcp.com/servers?q=revenue.io](https://www.pulsemcp.com/servers?q=revenue.io) - [https://www.revenue.io/pricing](https://www.revenue.io/pricing) 5 source URLs. Raw sources field, verbatim: https://www.revenue.io/forecasting, https://www.revenue.io/faqs, https://www.vendr.com/marketplace/revenue-io, https://www.pulsemcp.com/servers?q=revenue.io, https://www.revenue.io/pricing **Notes, verbatim from the file** None. [api_gate 2026-08-25] Reclassified unknown -> enterprise-only from the vendor's own page (https://www.revenue.io/pricing): the pricing page states a custom quote is built on the demo call rather than published as a list price; an API exists and the support site documents APIs and Programmatic Operations for Guided Selling, but no plan condition is published. 2026-09-02: re-checked https://www.revenue.io/llms.txt (no MCP mention), the official MCP registry (no entry) and a web search (hits were Revenue Grid and RevenueCat, different companies); no MCP server found. **Provenance** - **Entry id**: 12-revenue-io - **Source file**: 12-forecasting-revenue.md - **Source line**: 264 - **Tier**: RESEARCHED - **last_checked**: 2026-09-02 - **Data baked**: 2026-09-27 Every field above is rendered from directory.json exactly as the build produced it. Nothing is summarised and nothing is dropped. The one change made at render time is typographic and it is disclosed on the [methodology page](../methodology.md).