# Champify: MCP server status, API access gate and what it does > Tracks job changes of a company's past customers and champions as they move to new roles/companies, and flags... 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) / [Signals & Intent](../categories/signals-intent-abm.md) / Champify # Champify [No MCP found](../mcp/none-found.md) [Enterprise only](../gates/enterprise-only.md) [Signals & Intent](../categories/signals-intent-abm.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.champify.io](https://www.champify.io) · entry id 05-champify · source 05-signals-intent-abm.md line 111 **What it does** Tracks job changes of a company's past customers and champions as they move to new roles/companies, and flags closed-lost opportunities for re-engagement, integrated directly into Salesforce. **AI features, separated from automation with an AI label on it** "Insider AI" is marketed as synthesizing call transcripts, emails, and CRM data to recommend who/when/how to re-engage - plausible LLM synthesis, but no methodology is disclosed publicly, so treat as an unverified vendor claim. The core job-change detection itself is plain matching, not ML. **RevOps role** Champion-tracking / warm-outbound trigger tool, a near-direct competitor to UserGems with the same product shape. **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 **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/champifyio](https://github.com/champifyio) tied to the vendor by rule 3, account website https://champify.io has the vendor's domain, confidence strong - **Public repositories**: 1, forks excluded, as read on 2026-09-08 - **Mention MCP**: 0 of them - **Look like CLIs**: 0 of them - **Latest push**: 2024-11-22 The five most recently pushed, on 2026-09-08: | Repository | Kind | Description | Stars | Pushed | Latest release | |---|---|---|---|---|---| | [env](https://github.com/champifyio/env) | other | | 1 | 2024-11-22 | | 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** - [Track job changes](../jobs/track-job-changes.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.champify.io/pricing](https://www.champify.io/pricing) - [https://www.champify.io/](https://www.champify.io/) - [https://www.trustradius.com/products/champify/pricing](https://www.trustradius.com/products/champify/pricing) - [https://prospectingmanual.com/ai-automation/compare/usergems-vs-champify/](https://prospectingmanual.com/ai-automation/compare/usergems-vs-champify/) - [https://www.vendr.com/buyer-guides/champify](https://www.vendr.com/buyer-guides/champify) 5 source URLs. Raw sources field, verbatim: https://www.champify.io/pricing, https://www.champify.io/, https://www.trustradius.com/products/champify/pricing, https://prospectingmanual.com/ai-automation/compare/usergems-vs-champify/, https://www.vendr.com/buyer-guides/champify **Notes, verbatim from the file** Searched GitHub, mcp.so, glama.ai, pulsemcp.com - no MCP found. Published tiers $2,000-$6,000/mo (annual contracts standard); no self-serve signup, pricing page only offers "Get Demo"/"Request Data Test." Vendr reports median actual spend of $15,750/yr (n=11), below list price. 2026-09-02: re-checked champify.io/llms.txt (404) and web search; no MCP server found. **Provenance** - **Entry id**: 05-champify - **Source file**: 05-signals-intent-abm.md - **Source line**: 111 - **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).