Vendor: vidyard.com · entry id 08-vidyard · source 08-video-prospecting.md line 14
A working server exists but somebody other than the vendor built it. It can be abandoned without the vendor noticing. The status was established by hand on 2026-08-24. On 2026-09-04 the recorded URL served a documentation page, not an MCP endpoint. That is where to read about the server, not where to connect to it. An agent needs the second.
mcp_status, verbatim from the file:
community
mcp_url, verbatim from the file:
https://viasocket.com/mcp/vidyard (third-party viaSocket connector; no vendor-published or GitHub/registry-listed dedicated server found on mcp.so, glama.ai, or pulsemcp.com)
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:
npm install -g @vidyard/vy-cliquoted from https://www.npmjs.com/package/@vidyard/vy-cli on 2026-09-27, via npm
Packages seen, with the version on 2026-09-27:
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, with conflicting detail. Vidyard's own docs say the Video Agent API is available on Free/Starter/Teams/Enterprise but caps non-add-on accounts at 15 AI videos total; a secondary source (Claap) states general API access is Enterprise-only on Starter/Teams. Treat as paid at minimum, likely more for full access.
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.
github.com/Vidyard tied to the vendor by rule 3, account website www.vidyard.com has the vendor's domain, confidence strong
The five most recently pushed, on 2026-09-08:
| Repository | Kind | Description | Stars | Pushed | Latest release |
|---|---|---|---|---|---|
| DesktopAppReleases | app | To house official releases of the Vidyard Desktop App | 0 | 2026-05-11 | 2.3.5 |
| .github | other | Public org repo | 0 | 2026-02-03 | |
| wordpress-plugin | plugin or integration | 2 | 2019-09-30 | ||
| dsm | other | Online MySQL data migrations gem | 2 | 2017-04-18 |
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.
6 source URLs. Raw sources field, verbatim:
https://www.vidyard.com/, https://www.vidyard.com/blog/ai-avatars-in-sales-and-marketing/, https://developer.vidyard.com/, https://knowledge.vidyard.com/hc/en-us/articles/42909331296411-Using-the-Vidyard-Video-Agent-API, https://viasocket.com/mcp/vidyard, https://www.claap.io/blog/vidyard-pricing
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.