# Aviso: MCP server status, API access gate and what it does > AI revenue operations platform combining pipeline forecasting, conversation/deal intelligence, and agentic... No MCP found, Gate unknown. Checked 2026-08-24. *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).* --- [Directory](../index.md) / [Forecasting & Revenue](../categories/forecasting-revenue.md) / Aviso # Aviso [No MCP found](../mcp/none-found.md) [Gate unknown](../gates/unknown.md) [Forecasting & Revenue](../categories/forecasting-revenue.md) RESEARCHED Checked 2026-08-24 > **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 0. Vendor: [aviso.com (aviso.ai 302-redirects to a domain-marketplace listing, not the company)](https://aviso.com (aviso.ai 302-redirects to a domain-marketplace listing, not the company)) · entry id 12-aviso · source 12-forecasting-revenue.md line 36 **What it does** AI revenue operations platform combining pipeline forecasting, conversation/deal intelligence, and agentic workflow automation for sales, RevOps, and customer success teams. **AI features, separated from automation with an AI label on it** Vendor claims "advanced forecasting models" using a "time-series database" and deal win-probability scoring derived from call/email signals - plausible ML claims but no disclosed methodology or benchmark, and includes an unverified marketing claim of "nearly 100% accurate" forecasting. Separately markets "Real-Time AI Avatars" and 30+ agentic workflows via a no-code "GTM Agent Studio" - LLM-driven workflow orchestration, not predictive ML, though vendor copy blends the two under "agentic AI." **RevOps role** Positions itself as a full "revenue operating system" - forecasting plus conversation intelligence plus CS renewal signals plus an AI SDR/agent layer - broader in scope than a pure forecasting point tool. **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-08-24 and has not been re-fetched since. mcp_status, verbatim from the file: none-found mcp_url, verbatim from the file: none **Access gate** - **Gate bucket**: Gate unknown - **Can a solo operator reach it**: Not established api_gate, verbatim from the file: unknown. No developer/API documentation was found in site navigation, and third-party sources disagree on whether a public API exists at all. Pricing is entirely quote/demo-gated - no self-serve tier or published prices. 83 of 293 entries carry an unknown gate. Unknown is a legal answer and it ships as unknown rather than as a guess. **API documentation** No documentation URL recorded. 263 of 293 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. **Jobs it can do** - [Extract deal signals from calls](../jobs/extract-deal-signals-from-calls.md) - [Run an automation workflow](../jobs/run-automation-workflow.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 55 job vocabulary. 271 of 293 entries carry at least one tag; 827 tags are assigned in total. **Sources** - [https://aviso.ai](https://aviso.ai) - [https://www.atom.com/name/Aviso.ai](https://www.atom.com/name/Aviso.ai) - [https://www.aviso.com](https://www.aviso.com) - [https://www.aviso.com/pricing](https://www.aviso.com/pricing) 4 source URLs. Raw sources field, verbatim: https://aviso.ai, https://www.atom.com/name/Aviso.ai, https://www.aviso.com, https://www.aviso.com/pricing **Notes, verbatim from the file** DOMAIN FLAG - aviso.ai does not belong to the company; it 302-redirects to a domain marketplace/broker listing page. The live product is at aviso.com. Same "wrong domain in circulation" pattern flagged for Clearbit/Leadfeeder elsewhere in this directory. **Provenance** - **Entry id**: 12-aviso - **Source file**: 12-forecasting-revenue.md - **Source line**: 36 - **Tier**: RESEARCHED - **last_checked**: 2026-08-24 - **Data baked**: 2026-08-25 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).