Shipwork SEO Checks vs AI Visibility MCP | AllMCPs
Side-by-Side Model Context Protocol Comparison
Shipwork SEO Checks vs AI Visibility MCP
In-depth architectural comparison of the Shipwork SEO Checks and AI Visibility MCP 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
Shipwork SEO Checks
Marketing · Local stdio
Quality: 45/100 (Fair) | Auth: API Key required
AI Visibility MCP
Marketing · Local stdio
Quality: 44/100 (Fair) | Auth: API Key required
Verdict Summary: Choose Shipwork SEO Checks if you need specialized Marketing tools running via a local process. Choose AI Visibility MCP if your workspace requires Marketing integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
S
Choose Shipwork SEO Checks when:
You need dedicated capabilities in the Marketing domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Freemium).
You need dedicated capabilities in the Marketing domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
You have access to required keys: PERPLEXITY_API_KEY, OPENROUTER_API_KEY, MAX_COST_PER_CALL, MAX_DAILY_USD, LLM_MAX_OUTPUT_TOKENS, AI_VISIBILITY_SPEND_FILE.
Primary tools included: Audits 22 AI user-agents, Scores robots, schema, sitemap, llms.txt, and SPA visibility, Generates robots.txt patches and structured data.
Hosted MCP tools for technical SEO audits, URL status and indexability, sitemaps, and site scores. Sign in at shipwork.io/account to create a personal MCP URL; tool calls use that account allowance.
Audit how AI sees your website. Per-bot robots.txt verdicts for 22 known AI user-agents (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, Bytespider, etc), Cloudflare AI-default flags, on-page schema, sitemap, llms.txt, SPA-shell detection, and cross-model brand mentions via Perplexity + OpenRouter. 0-100 score with explainable deductions; parallel competitor compare. SSRF-guarded, per-call and daily LLM spend caps. MIT, 24 tests, stdio + HTTP.
Category & Scope
Tools & Capabilities Breakdown
Shipwork SEO Checks Tools (0)
No explicit tool names declared in metadata yet. Check project README on main listing page.
AI Visibility MCP Tools (6)
Audits 22 AI user-agents
Scores robots, schema, sitemap, llms.txt, and SPA visibility
Generates robots.txt patches and structured data
Checks cross-model brand mentions
Compares up to 10 domains in parallel
Enforces SSRF and LLM spending safeguards
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Shipwork SEO Checks is categorized under Marketing and uses a local stdio subprocess. In contrast, AI Visibility MCP belongs to Marketing using local stdio subprocess. Select Shipwork SEO Checks when you need capabilities focused on marketing and AI Visibility MCP when you require tools for marketing.