Vendor: dealhub.io · entry id 13-dealhub · source 13-proposals-deals.md line 71
The check could not settle it either way. Unknown is a legal answer and it is published rather than guessed. The status was established on 2026-08-24 and has not been re-fetched since.
mcp_status, verbatim from the file:
unknown
mcp_url, verbatim from the file:
a third-party directory (salestools.club/apis/dealhub) lists "DealHub API Documentation & MCP Config," implying some MCP configuration exists, but no official DealHub-branded MCP docs page or GitHub repo could be independently located to confirm - logged as unknown rather than community/official pending direct verification.
api_gate, verbatim from the file:
enterprise-only in practice. DealHub operates on a custom-quote-only pricing model with no published prices across all three tiers (CPQ+, CPQ+CLM, Quote-to-Revenue); the Pricing API and Callouts API for real-time pricing sync exist but are documented as integration features of a purchased platform, not a standalone self-serve developer product.
No documentation URL recorded.
263 of 293 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 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 55 job vocabulary. 271 of 293 entries carry at least one tag; 827 tags are assigned in total.
4 source URLs. Raw sources field, verbatim:
https://dealhub.io/pricing/, https://developers.dealhub.io/docs/introduction-to-dealhub-apis, https://dealhub.io/blog/cpq/what-you-can-do-with-dealhub-api/, https://salestools.club/apis/dealhub
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.