Vendor: default.com · entry id 06-default · source 06-revops-infra.md line 220
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-09-02.
mcp_status, verbatim from the file:
unknown
mcp_url, verbatim from the file:
n/a (marketing pages only: https://www.default.com/solutions/default-mcp names a Default MCP but publishes no endpoint, auth, or setup docs, and docs.default.com has no MCP article)
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:
enterprise-only (no pricing is published and the only CTA is book-a-demo; the site describes Native Access in beta as MCP access to data and tools for every agent, so programmatic access exists but is reachable only through sales)
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 default.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: chainguard-dev, SovereignCloudStack, Kicksecure, nordicsemi, AkerBP. 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.
This page is the canonical home. The listing below is the same product, counted separately in the source markdown.
What that listing says it does: "Agentic GTM infrastructure" platform unifying CRM, website-form, and enrichment data into one identity-resolved model, with lead routing, scheduling, enrichment, and workflow automation built on top.
16 of the 1252 entries are cross listed like this. They are why the entry count is 1252 and the unique product count is 1236. The canonical home is declared in INDEX.md, not chosen by the parser.
4 source URLs. Raw sources field, verbatim:
https://www.default.com, https://www.default.com/product, https://docs.default.com, https://www.default.com/solutions/default-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.