Shipwork SEO Checks vs Screaming Frog MCP | AllMCPs
Side-by-Side Model Context Protocol Comparison
Shipwork SEO Checks vs Screaming Frog MCP
In-depth architectural comparison of the Shipwork SEO Checks and Screaming Frog 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
Screaming Frog MCP
Marketing · Local stdio
Quality: 47/100 (Fair) | Auth: other
Verdict Summary: Choose Shipwork SEO Checks if you need specialized Marketing tools running via a local process. Choose Screaming Frog 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).
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.
Screaming Frog SEO Spider headless crawls, data export, and technical SEO audit skill for Claude. 8 tools, cross-platform (Mac + Windows), includes a ready-to-use technical SEO scan skill.
Shipwork SEO Checks is categorized under Marketing and uses a local stdio subprocess. In contrast, Screaming Frog MCP belongs to Marketing using local stdio subprocess. Select Shipwork SEO Checks when you need capabilities focused on marketing and Screaming Frog MCP when you require tools for marketing.