In-depth architectural comparison of the Ovecc and Web Hygiene 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
Ovecc
Developer Tools · Local stdio
Quality: 48/100 (Fair) | Auth: No auth required
Web Hygiene MCP
Developer Tools · Remote HTTP/SSE
Quality: 56/100 (Good) | Auth: API Key required
Verdict Summary: Choose Ovecc if you need specialized Developer Tools tools running via a local process. Choose Web Hygiene MCP if your workspace requires Developer Tools integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Ovecc when:
You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: Persistent repository index of files, imports, symbols, and calls, MCP access to the CLI command surface over stdio, Architecture contracts with dependency and complexity rules.
Architecture guardrails for AI-written code: dependency graph, impact, dead code, CI gate
Live web checks for AI agents, from real HTTP requests at call time: site_overview (robots.txt, llms.txt, sitemaps, feeds), list_site_urls, check_url, check_links (404s, redirects, SSL, slow pages), discover_feeds, read_feed (RSS/Atom/JSON Feed), and verify_citations (does the cited page exist and really carry the quote, title, date? Internet Archive copy for dead links). Remote Streamable HTTP server hosted on Apify; pay per event via your own Apify account, nothing runs locally. Claude Code plugin with verify-sources and site-preflight skills available.
Category & Scope
Tools & Capabilities Breakdown
Ovecc Tools (6)
Persistent repository index of files, imports, symbols, and calls
MCP access to the CLI command surface over stdio
Architecture contracts with dependency and complexity rules
Impact, cycle, coupling, and hotspot analysis
Security, audit, dead-code, duplicate-code, and health checks
Text, JSON, NDJSON, Markdown, SARIF, and Code Climate output
Web Hygiene MCP Tools (0)
No explicit tool names declared in metadata yet. Check project README on main listing page.
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).
Ovecc is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Web Hygiene MCP belongs to Developer Tools using remote streaming HTTP/SSE transport. Select Ovecc when you need capabilities focused on developer tools and Web Hygiene MCP when you require tools for developer tools.