# Rox: MCP server status, API access gate and what it does > An AI-powered revenue automation platform for enterprise sales teams, positioned as an autonomous SDR-style... No MCP found, Gate unknown. 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) / [AI SDRs](../categories/ai-sdr-agents.md) / Rox # Rox [No MCP found](../mcp/none-found.md) [Gate unknown](../gates/unknown.md) [AI SDRs](../categories/ai-sdr-agents.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: [https://www.rox.com](https://www.rox.com) · entry id 04-rox · source 04-ai-sdr-agents.md line 315 **What it does** An AI-powered revenue automation platform for enterprise sales teams, positioned as an autonomous SDR-style agent handling pipeline generation, lead qualification, meeting booking, deal management, and account expansion "on autopilot." **AI features, separated from automation with an AI label on it** Site copy explicitly caveats that "autopilot"/"autonomous" features operate within user-defined parameters and require initial configuration and ongoing oversight - a rare instance of a vendor undercutting its own hype in the fine print; treat the headline autonomy claims as partially self-qualified. **RevOps role** Full-cycle revenue automation for large enterprise sales orgs - not sized or priced for a solo operator based on available signals. **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 The mcp_url field is empty on this entry. 417 of 1252 entries are. **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**: Gate unknown - **Can a solo operator reach it**: Not established api_gate, verbatim from the file: unknown - built for "the Global 2000," no self-serve signup found; strongly enterprise-oriented positioning 949 of 1252 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. 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** [github.com/Rox-AI](https://github.com/Rox-AI) tied to the vendor by rule 3, account website rox.com has the vendor's domain, confidence strong - **Public repositories**: 2, forks excluded, as read on 2026-09-08 - **Mention MCP**: 0 of them - **Look like CLIs**: 0 of them - **Latest push**: 2026-08-21 The five most recently pushed, on 2026-09-08: | Repository | Kind | Description | Stars | Pushed | Latest release | |---|---|---|---|---|---| | [rox-electron-updates](https://github.com/Rox-AI/rox-electron-updates) | other | Rox Desktop Electron App Updates | 0 | 2026-08-21 | v1.0.37 | | [rox-mac-app-updates](https://github.com/Rox-AI/rox-mac-app-updates) | app | Rox Mac App updates | 0 | 2026-02-17 | mac-0.4.6 | 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. **Jobs it can do** - [Run an autonomous SDR agent](../jobs/run-autonomous-sdr-agent.md) - [Book a meeting](../jobs/book-a-meeting.md) - [Score and prioritize leads](../jobs/score-and-prioritize-leads.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.rox.com](https://www.rox.com) - [https://www.rox.com/pricing](https://www.rox.com/pricing) 2 source URLs. Raw sources field, verbatim: https://www.rox.com, https://www.rox.com/pricing **Notes, verbatim from the file** Rox has built something called "Rox Tether," described on their site (dated July 29, 2026) as an "Agentic UI alternative to MCP Apps, A2UI or ChatGPT Apps" - i.e., Rox is positioning against MCP-style integration patterns rather than shipping an MCP server. Worth a dedicated look for category 7 (mcp-infrastructure) as a competitor/alternative protocol, not as an MCP itself. [api_gate 2026-08-25] Re-checked and left unknown, honestly: self-serve tiers are published at $100/mo Individual and $255/mo Teams plus a quote-only Enterprise, but neither the pricing page nor docs.rox.com (release notes only) states anything about API access. Checked against https://www.rox.com/pricing. 2026-09-02: re-checked https://www.rox.com/llms.txt (no MCP mention; it describes a Microsoft Copilot integration), the official MCP registry (no Rox entry) and a web search; no MCP server found. The Rox Tether positioning against MCP Apps is unchanged. **Provenance** - **Entry id**: 04-rox - **Source file**: 04-ai-sdr-agents.md - **Source line**: 315 - **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).