Vendor: pandadoc.com · entry id 13-pandadoc · source 13-proposals-deals.md line 14
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-09-07. 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:
official
mcp_url, verbatim from the file:
https://mcp.pandadoc.com/v1/mcp ; https://developers.pandadoc.com/docs/how-to-use-the-pandadoc-mcp-server ; hosted remote server at https://mcp.pandadoc.com/v1/mcp ; repo https://github.com/PandaDoc/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.
This is a third party's CLI. It was published by somebody other than the vendor, so it is that author's surface for the vendor's API and not the vendor's published surface. The two must not be read as the same thing.
Install, as the source shows it:
pip install pandadocquoted from https://pypi.org/project/pandadoc/ on 2026-09-27, via pypi, a third party source
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:
free (limited). PandaDoc's Free plan now includes API access with both a sandbox and production API key at signup (60 documents/year, 5 templates, sandbox docs watermarked and limited to your own domain) - sources conflict on whether production API access requires a paid/Enterprise plan, so treat the free-tier claim as probable-but-recently-changed rather than fully certain; verify current terms before publishing.
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.
A github.com URL already appears somewhere in this entry, which is a seed for that rail and not a measurement of repo health:
github.com/PandaDoc tied to the vendor by rule 2, account website https://pandadoc.com has the vendor's domain, confidence strong
The five most recently pushed, on 2026-09-08:
| Repository | Kind | Description | Stars | Pushed | Latest release |
|---|---|---|---|---|---|
| pandadoc-openapi-specification | API client | 6 | 2026-09-08 | v7.27.1 | |
| design-engineer-interview-200826-dry-run | other | 0 | 2026-08-20 | ||
| mcp-server-guide | MCP server | Where to start to use PandaDoc MCP server | 2 | 2026-08-20 | v1.0.0 |
| design-engineer-interview-170826 | other | 0 | 2026-08-17 | ||
| property-agreement-templates | docs or examples | Free property and real estate agreement templates - residential and commercial leases, rental agreements,... | 0 | 2026-07-22 | v1.0.0 |
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.
7 source URLs. Raw sources field, verbatim:
https://developers.pandadoc.com/docs/how-to-use-the-pandadoc-mcp-server, https://www.usecarly.com/blog/pandadoc-mcp/, https://www.pandadoc.com/blog/pandadoc-free-plan-api/, https://www.pandadoc.com/api/pricing/, https://www.pulsemcp.com/servers/dazanza-pandadoc, https://github.com/PandaDoc/mcp-server-guide, https://mcp.pandadoc.com/v1/mcp
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.