# Default: MCP server status, API access gate and what it does > An inbound go-to-market platform unifying revenue-stack data (a "Tables" data layer) with AI-agent-built... Official MCP, Gate unknown. Checked 2026-08-24. *Markdown twin of the HTML page at the same path. Same content, no navigation, no styling, no scripts. Links below point at other twins. Site map for machines: [llms.txt](../llms.txt). The whole dataset: [directory.json](../data/directory.json).* --- [Directory](../index.md) / [RevOps Infra](../categories/revops-infra.md) / Default # Default [Official MCP](../mcp/official.md) [Gate unknown](../gates/unknown.md) [RevOps Infra](../categories/revops-infra.md) RESEARCHED Checked 2026-08-24 > **RESEARCHED** Facts from public sources with URLs. No usage claims. Nobody has run this tool. The other tier is BENCH-TESTED, which means Andrew personally ran the tool on a stated date and cannot be bought at any price. Across the whole directory that count is 0. Vendor: [default.com](https://default.com) · entry id 06-default · source 06-revops-infra.md line 210 **What it does** An inbound go-to-market platform unifying revenue-stack data (a "Tables" data layer) with AI-agent-built workflows for lead routing, qualification, and meeting scheduling. **AI features, separated from automation with an AI label on it** "Dot" is an AI assistant/agent that turns plain-language requests into working GTM systems, with agent-built workflows reviewed/approved by humans before deployment, and agents that can schedule meetings. The workflow builder also has discrete "AI Routing" and "AI Prompt" nodes for AI-driven decisions inside otherwise deterministic workflows - a hybrid pattern similar to Make's. **RevOps role** Sits at inbound lead routing/qualification - where marketing-generated leads get scored, matched to reps/territories, and booked; pitched as an agentic replacement for legacy lead-routing tools. **MCP server** - **Status bucket**: Official MCP - **Auth**: unknown - not documented anywhere found (checked default.com, default.com/product, docs.default.com). - **Parsed URLs**: 1 found in the mcp_url field 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 on 2026-08-24 and has not been re-fetched since. mcp_status, verbatim from the file: official mcp_url, verbatim from the file: https://www.default.com (homepage feature line only - "MCP access to data and tools for every agent, whether built inside Default or on top of it," explicitly marked "In beta"; no separate docs/repo page was located) - [https://www.default.com](https://www.default.com) **Access gate** - **Gate bucket**: Gate unknown - **Can a solo operator reach it**: Not established api_gate, verbatim from the file: unknown - no visible self-serve signup, free trial, or pricing page; access is exclusively via "Request a Demo" or existing-customer login (default.com/pricing 404s). Strongly suggestive of an enterprise-sales gate, but unconfirmed. 83 of 293 entries carry an unknown gate. Unknown is a legal answer and it ships as unknown rather than as a guess. **API documentation** No documentation URL recorded. 263 of 293 entries are in the same position. Blank is legal and it is published as blank. **GitHub health** 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. **Jobs it can do** - [Enrich a company from a domain](../jobs/enrich-company-from-domain.md) - [Book a meeting](../jobs/book-a-meeting.md) - [Run an automation workflow](../jobs/run-automation-workflow.md) - [Route an inbound lead](../jobs/route-inbound-lead.md) - [Score and prioritize leads](../jobs/score-and-prioritize-leads.md) 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. **Also listed in another category** This page is the canonical home. The listing below is the same product, counted separately in the source markdown. - **Listed as**: Default - **Category**: [Scheduling & Routing](../categories/scheduling-routing.md) - **MCP status there**: Official MCP - **Gate there**: Gate unknown - **Source**: 10-scheduling-routing.md line 65 - **Canonical page**: [Default](../tools/default.md) 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 293 entries are cross listed like this. They are why the entry count is 293 and the unique product count is 277. The canonical home is declared in INDEX.md, not chosen by the parser. **Sources** - [https://www.default.com](https://www.default.com) - [https://www.default.com/product](https://www.default.com/product) - [https://docs.default.com](https://docs.default.com) 3 source URLs. Raw sources field, verbatim: https://www.default.com, https://www.default.com/product, https://docs.default.com **Notes, verbatim from the file** Confirmed this is default.com the lead-routing SaaS, not a generic dev-tooling reference. The MCP claim is real but labeled "In beta" on the homepage with no dedicated docs/repo page found - treat as early/unstable. Marked official rather than none-found because the vendor's own page explicitly names MCP with a linkable URL, satisfying the schema's "URL required" law, even though it isn't a full docs page. **Provenance** - **Entry id**: 06-default - **Source file**: 06-revops-infra.md - **Source line**: 210 - **Tier**: RESEARCHED - **last_checked**: 2026-08-24 - **Data baked**: 2026-08-25 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](../methodology.md).