Launch Audit
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Use check_brand_availability, audit_email_deliverability, audit_ai_search_visibility, or full_launch_readiness_audit to run live pre-launch technical audits on domains and candidate startup names.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_brand_availabilityA | Check a single candidate startup or product name across top TLDs (.com, .io, .ai, .dev via live RDAP/DNS), public developer handles (GitHub, npm, PyPI, Bluesky), and live USPTO trademark records, returning a 0-100 Brand Readiness Score. Use this tool when evaluating candidate names before registering a domain; use |
| audit_email_deliverabilityA | Audit a sending domain's email authentication and inbox placement health: resolves MX servers, recursively counts SPF DNS lookups against the RFC 7208 10-lookup hard limit, probes 18 standard ESP DKIM selectors, validates DMARC policy enforcement, checks MTA-STS/BIMI, and tests the primary mail IP against major DNSBL blacklists. Use this tool for diagnosing why transactional or marketing emails land in spam; use |
| audit_ai_search_visibilityA | Inspect a live website URL for Generative Engine Optimization (GEO) and AI assistant citation readiness: verifies whether |
| full_launch_readiness_auditA | Run a comprehensive, parallel 3-pillar pre-launch audit on a production domain — combining brand/trademark conflict screening, SPF/DKIM/DMARC/DNSBL email deliverability verification, and AI search ( |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| pre-launch-checklist | Run a complete 3-pillar technical launch readiness audit (Brand + Email DNS + AI Search GEO) and generate a prioritized remediation plan. |
| fix-emails-going-to-spam | Diagnose SPF 10-lookup limits, missing DKIM selectors, and DMARC p=none gaps on a sending domain. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| OmniForge Pro Offline CLI & CI Remediation Toolkits | Reference matrix comparing free single-domain MCP checks with offline batch CSV, SPF flattening, and 500-page /llms.txt compilation in the Pro toolkits. |
TDQS
Scored across 4 tools
The three specialized tools target clearly distinct pillars (brand/trademark, email DNS, AI crawler readiness), and every description explicitly states when to prefer the composite `full_launch_readiness_audit` versus the single-pillar tool. The only residual ambiguity is inherent functional overlap between the composite and its three children, which is mitigated by well-written routing hints rather than eliminated.
Three tools follow a verb_noun snake_case pattern (check_brand_availability, audit_email_deliverability, audit_ai_search_visibility), which is readable and predictable. `full_launch_readiness_audit` breaks the verb-first convention by leading with an adjective, a minor deviation in an otherwise consistent set.
Four tools is tightly scoped to the pre-launch audit domain: three specialized checks plus one orchestrating composite. Each tool earns its place with no filler or redundant variants.
The surface covers brand, email deliverability, and AI search readiness with both granular and unified entry points, which is solid lifecycle coverage for a pre-launch audit. Minor gaps remain: brand checking is single-name only (no batch comparison of candidate shortlists) and there is no way to persist, diff, or re-fetch a prior audit result.