In-depth architectural comparison of the Ai Readiness and StreetProof Physical Brand Index MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Ai Readiness
Marketing · Local stdio
Quality: 51/100 (Good) | Auth: No auth required
StreetProof Physical Brand Index
Marketing · Remote HTTP/SSE
Quality: 41/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Ai Readiness if you need specialized Marketing tools running via a local process. Choose StreetProof Physical Brand Index if your workspace requires Marketing integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Ai Readiness when:
You need dedicated capabilities in the Marketing domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: Scores websites from 0 to 100 with a letter grade, Checks GPTBot, ClaudeBot, PerplexityBot, Google-Extended, and other crawlers, Validates JSON-LD structured data.
Check whether a website is visible to AI search (ChatGPT, Perplexity, Claude, Google AI Overviews). Scores AI-crawler access, JSON-LD structured data, title/meta, Open Graph, sitemap, and llms.txt, with a specific fix for each gap. Dependency-free, no API keys. Install: npx -y github:epistemedeus/ai-readiness mcp.
Read-only, privacy-safe evidence of physical business presence for AI agents.
Ai Readiness is categorized under Marketing and uses a local stdio subprocess. In contrast, StreetProof Physical Brand Index belongs to Marketing using remote streaming HTTP/SSE transport. Select Ai Readiness when you need capabilities focused on marketing and StreetProof Physical Brand Index when you require tools for marketing.