Vendor: mixmax.com · entry id 02-mixmax · source 02-engagement-outbound.md line 483
The vendor ships and maintains the server itself. A wrapper built by Zapier, Composio or a similar third party does not count as official. The status was established by hand on 2026-08-25. On 2026-09-04 the recorded URL answered an MCP initialize as a server, which is liveness and nothing more: nobody has run its tools.
mcp_status, verbatim from the file:
official
mcp_url, verbatim from the file:
https://mcp.mixmax.com/mcp (docs: https://success.mixmax.com/en/articles/14298142-mixmax-mcp-server; vendor guide: https://www.mixmax.com/mcp-server-guide)
Not harvested yet. Unmeasured, not empty: nobody has read this server's tool list, so this page says nothing about what it exposes.
141 of the 741 entries that record an official or community MCP server carry a harvested tool list. The other 600 are unmeasured, which is not the same as empty. Harvest last run 2026-09-27. The full roll up is on the tools index.
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.
api_gate, verbatim from the file:
paid. Two separate gates, and the split is the useful fact. The MCP server is free to every Mixmax customer including the $0 Free plan per the vendor help doc, but meeting data requires the Meeting Copilot product ($29/user/mo annual, $34 monthly). The REST API is a higher gate: Mixmax's own pricing page includes "Mixmax API" only on Engagement Copilot ($49/mo annual), Mixmax Suite ($89/mo annual) and Mixmax for Teams. A third-party review states API is restricted to annual Growth+/Enterprise plans, which does not match the current published plan names, so trust the pricing page.
https://developer.mixmax.com/reference/getting-started-with-the-api
No documentation text is reproduced anywhere on this site. Read the vendor page for the prose. The structured docs digest specced in SPEC section 3 has not been built or crawled: docs_digest is null on every entry in this build.
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.
github.com/mixmaxhq tied to the vendor by rule 3, account website https://www.mixmax.com/engineering has the vendor's domain, confidence strong
The five most recently pushed, on 2026-09-08:
| Repository | Kind | Description | Stars | Pushed | Latest release |
|---|---|---|---|---|---|
| email-setup | other | Collection of utilities for checking email configuration settings. | 2 | 2026-09-01 | v1.1.2 |
| eslint-config-mixmax | other | Mixmax's JS linter configuration. | 1 | 2026-08-19 | v6.0.1 |
| custody-probe | other | Report the state of child processes to custody. | 0 | 2026-07-10 | |
| aws-instance-metadata | other | 2 | 2026-07-10 | v2.1.3 | |
| check-dependencies-except-peer | other | Ensure that your package-lock matches your package and is self-consistent, and ignore missing peerDependencies | 1 | 2026-07-10 |
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.
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.
5 source URLs. Raw sources field, verbatim:
https://success.mixmax.com/en/articles/14298142-mixmax-mcp-server, https://www.mixmax.com/mcp-server-guide, https://www.mixmax.com/pricing, https://developer.mixmax.com/, https://success.mixmax.com/en/articles/11643056-mixmax-rest-api
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.