Vendor: heygen.com · entry id 08-heygen · source 08-video-prospecting.md line 147
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-24. 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.heygen.com/mcp/v1/ (docs: https://developers.heygen.com/mcp/overview; product page: https://www.heygen.com/model-context-protocol)
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.
Install, as the source shows it:
curl -fsSL https://static.heygen.ai/cli/install.sh | bashquoted from https://developers.heygen.com/cli on 2026-09-27, via shell
Login or key hint seen on the page:
heygen auth
Subcommands seen with the binary:
auth, video, video-agent
Where it was documented:
A CLI being listed means the harvest found an install command or a package on a stated date. Nobody has run it. Every command is quoted verbatim from the URL beneath it. Harvest date 2026-09-27.
api_gate, verbatim from the file:
paid, pay-as-you-go. Public REST API billed from a prepaid USD wallet per feature (e.g., roughly $0.05/sec for photo-avatar video, ~$0.000667/sec TTS, $1.00 per avatar-creation call); no free API tier found for developers, though a solo operator can start with a small prepaid balance.
No documentation URL recorded.
727 of 1252 entries are in the same position. Blank is legal and it is published as blank.
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.
No GitHub organisation could be tied to heygen.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: heygen-com, HeyGen-Official, HeyGen-Ai-App, heygen-fork, Heygent-core. A name match alone is never accepted; the account has to point at the vendor domain.
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.
6 source URLs. Raw sources field, verbatim:
https://www.heygen.com/business/sales, https://www.heygen.com/integrations/hubspot, https://www.heygen.com/blog/best-ai-video-tools-sales-prospecting, https://developers.heygen.com/mcp/overview, https://developers.heygen.com/docs/pricing, https://www.heygen.com/model-context-protocol
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.