Launch Audit
# mcp-launch-audit
[](./LICENSE)
[](https://nodejs.org)
[](./package.json)
[](https://modelcontextprotocol.io)
[](https://brand-checker.appwrite.network/report/BrandShield)
[](https://inbox-checker.appwrite.network/?domain=stripe.com)
[](https://citeready-checker.appwrite.network/?url=https://stripe.com)
**Zero-dependency Model Context Protocol (MCP) server for pre-launch startup & domain audits** — combining live RDAP domain + developer handle + USPTO trademark conflict checks, recursive SPF/DKIM/DMARC/DNSBL email deliverability verification, and AI search (`robots.txt`, `/llms.txt`, Schema.org JSON-LD) readiness in one lightweight package.
Works out of the box with **zero API keys**, **zero `npm` sub-dependencies**, and **zero configuration** in Claude Desktop, Claude Code, Cursor, Windsurf, Cline, and VS Code.
---
## Quick Start
### Option A: Local `stdio` via `npx` (Recommended)
Add to your `claude_desktop_config.json`, `.cursor/mcp.json`, or `.vscode/mcp.json`:
```json
{
"mcpServers": {
"launch-audit": {
"command": "npx",
"args": ["-y", "github:zColdWater/mcp-launch-audit"]
}
}
}
```
Or add in one command with **Claude Code**:
```bash
claude mcp add launch-audit -- npx -y github:zColdWater/mcp-launch-audit
```
### Option B: Zero-Install Remote Streamable-HTTP Endpoint
Prefer a hosted MCP connector with no local runtime? Point any Streamable-HTTP MCP client directly at:
```text
https://brand-checker.appwrite.network/mcp
```
```bash
claude mcp add --transport http launch-audit https://brand-checker.appwrite.network/mcp
```
### Option C: Docker
```bash
docker build -t mcp-launch-audit .
docker run -i --rm mcp-launch-audit
```
---
## Included MCP Tools (4)
| Tool | What It Audits | Output |
| :--- | :--- | :--- |
| `check_brand_availability` | Live RDAP/DNS across `.com/.io/.ai/.dev`, public developer handles (`GitHub`, `npm`, `PyPI`, `Bluesky`), and live USPTO trademark filings | `0-100` Brand Readiness Score + per-TLD & trademark breakdown |
| `audit_email_deliverability` | MX servers, ESP auto-detection, recursive SPF lookup count against RFC 7208's 10-lookup hard cap, 18 standard DKIM selectors, DMARC policy, MTA-STS, BIMI, and DNSBL blacklists | `0-100` Deliverability Score + actionable DNS fixes |
| `audit_ai_search_visibility` | `/robots.txt` rules across 8 AI search crawlers (`OAI-SearchBot`, `GPTBot`, `PerplexityBot`, `ClaudeBot`, `Google-Extended`, etc.), `/llms.txt` & `/llms-full.txt` validation, and Schema.org `application/ld+json` extraction | `0-100` AI Search (GEO) Score + visibility gaps |
| `full_launch_readiness_audit` | Runs all 3 pillars in parallel on a production domain | Weighted `0-100` Launch Scorecard + prioritized pre-launch checklist |
All tools are strictly **read-only** (`readOnlyHint: true`, `destructiveHint: false`) — they never register domains, modify DNS records, or store queried brand names.
---
## Interactive Web Diagnostics & Pro Offline Toolkits
Need batch CSV screening across 500 names/domains, automatic SPF flattening, 500-page `/llms.txt` compilation, or CI/CD gates?
| Pillar | Free Interactive Web App | Open-Source CLI & GitHub Action | Pro Offline Suite & Agency License |
| :--- | :--- | :--- | :--- |
| **Brand & Trademarks** | [brand-checker.appwrite.network](https://brand-checker.appwrite.network) | [zColdWater/brandshield-cli](https://github.com/zColdWater/brandshield-cli) | [BrandShield Pro ($19)](https://agentarenastudi.gumroad.com/l/omniforge-brandshield) · [Direct Checkout](https://omnipulse-x402.appwrite.network/checkout/brandshield) |
| **Email Deliverability** | [inbox-checker.appwrite.network](https://inbox-checker.appwrite.network) | [zColdWater/inboxshield-cli](https://github.com/zColdWater/inboxshield-cli) | [InboxShield Pro ($29)](https://agentarenastudi.gumroad.com/l/omniforge-inboxshield) · [Direct Checkout](https://omnipulse-x402.appwrite.network/checkout/inboxshield) |
| **AI Search & `llms.txt`** | [citeready-checker.appwrite.network](https://citeready-checker.appwrite.network) | [zColdWater/citeready-cli](https://github.com/zColdWater/citeready-cli) | [CiteReady Pro ($19)](https://agentarenastudi.gumroad.com/l/omniforge-citeready) · [Direct Checkout](https://omnipulse-x402.appwrite.network/checkout/citeready) |
| **3-in-1 Launch Bundle** | All 3 Web Checkers | All 3 GitHub Actions | [Founder Launch Stack ($49 — Save $38)](https://agentarenastudi.gumroad.com/l/omniforge-launch-stack) · [Direct Checkout](https://omnipulse-x402.appwrite.network/checkout/launch-stack) |
---
## Development & Verification
```bash
npm test
```
## License
[MIT](./LICENSE) © OmniForge Studio
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.