# 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, 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) / Aviso # Aviso [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: [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-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 (quote-only - the pricing page asks you to fill out a form for a tailored proposal - and no API or developer docs link exists in nav or footer) **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 aviso.com 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: avisota, AvisoNovate, Avison-Technologies, cc-tcc-udf, avisops. A name match alone is never accepted; the account has to point at the vendor domain. **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 56 job vocabulary. 271 of 1,252 entries carry at least one tag; 849 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. [api_gate 2026-08-25] Reclassified unknown -> enterprise-only from the vendor's own page (https://www.aviso.com/pricing/): quote-only - the pricing page asks you to fill out a form for a tailored proposal - and no API or developer docs link exists in nav or footer. 2026-09-02: re-checked aviso.com (no llms.txt; the path serves the homepage), the official MCP registry (no entry) and a web search. Aviso's own Agent Studio blog describes each agent having "its own set of MCP tool servers", which makes Aviso an MCP client, not a server; no Aviso-published MCP server found. **Provenance** - **Entry id**: 12-aviso - **Source file**: 12-forecasting-revenue.md - **Source line**: 36 - **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).