# Champion: MCP server status, API access gate and what it does > Identifies and scores which existing customers are most engaged or most at risk, builds rich profiles of... 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) / [Community & Dark Social](../categories/community-dark-social.md) / Champion # Champion [No MCP found](../mcp/none-found.md) [Gate unknown](../gates/unknown.md) [Community & Dark Social](../categories/community-dark-social.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://championhq.com](https://championhq.com) · entry id 15-champion · source 15-community-dark-social.md line 26 **What it does** Identifies and scores which existing customers are most engaged or most at risk, builds rich profiles of their expertise/preferences, and matches them to sales/CS deal contexts for reference requests, case studies, and expansion motions. **AI features, separated from automation with an AI label on it** Markets "Revenue AI" for contact scoring (engaged vs. at-risk) and deal-context matching/ranking of champions - vendor-described on the homepage, no methodology disclosed, not independently verified. **RevOps role** Champion/advocate-identification and revenue-attribution layer spanning CRM, product-usage, support, and community-engagement signals - the customer-marketing sibling to job-change trackers like UserGems/Champify, but scoring champions inside existing accounts rather than tracking them to new employers. **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**: Gate unknown - **Can a solo operator reach it**: Not established api_gate, verbatim from the file: unknown - no self-serve pricing, signup, or API docs were found anywhere on the site; /pricing 404'd during this research and the homepage is demo-gated only ("Book a Demo," no visible signup or dollar figures). 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/championhq](https://github.com/championhq) tied to the vendor by rule 3, account website championhq.com has the vendor's domain, confidence strong - **Public repositories**: 0, forks excluded, as read on 2026-09-08 - **Mention MCP**: 0 of them - **Look like CLIs**: 0 of them - **Latest push**: not recorded 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** - [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://championhq.com](https://championhq.com) - [https://championhq.com/product](https://championhq.com/product) - [https://championhq.com/pricing](https://championhq.com/pricing) 3 source URLs. Raw sources field, verbatim: https://championhq.com, https://championhq.com/product, https://championhq.com/pricing **Notes, verbatim from the file** DISAMBIGUATION FLAG - do not confuse with Champify (champify.io), a different company covered in 05-signals-intent-abm.md that tracks job changes of past customers/champions moving to NEW companies. Champion (championhq.com) instead scores and activates champions WITHIN existing customer accounts for references, case studies, and expansion - a distinct product shape despite the near-identical name and adjacent positioning. Several plausible domains for a "Champion" tool were checked and ruled out during this research: champion.io (redirects to an unrelated personal site), trychampion.com (parked/domain-marketplace listing), and champion.app (parked for sale on GoDaddy) - championhq.com is the verified, live, correct domain. [api_gate 2026-08-25] Re-checked and left unknown, honestly: the Pricing nav item is a dead hash link with no destination, championhq.com/pricing returns 404, and no API or developer docs are referenced anywhere on the site. Checked against https://championhq.com/pricing. 2026-09-02: re-checked championhq.com (no llms.txt; /pricing still 404), the official MCP registry (no entry) and a web search; no MCP server found. **Provenance** - **Entry id**: 15-champion - **Source file**: 15-community-dark-social.md - **Source line**: 26 - **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).