M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionCrawlSEO MCP ServerOpen-source SEO monitoring: Google Search Console + Site Crawler + Core Web Vitals + MCP Server in one self-hosted dashboard.MartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS57 / 100 · C79 / 100 · B
Reliability8 / 2012 / 20
Security and permissions12 / 2018 / 20
Maintenance15 / 2016 / 20
Documentation12 / 2018 / 20
Setup experience10 / 2015 / 20
Best for
  • Founders, indie developers, and small teams
  • Users who want self-hosted SEO tools with data privacy
  • Users who want to leverage AI assistants for quick SEO insights
  • Engineering teams scaling AI coding agents while controlling spend
  • Platform teams that need auditable, rollback-aware agent execution records
  • Organizations using multiple agents (Claude, Codex, Gemini) under one governed flow
Not for
  • Users needing advanced enterprise-grade SEO features (e.g., large-scale keyword research, paid data)
  • Non-technical users, as self-hosting and configuration require technical skills
  • Users requiring official support (this is an open-source community project)
  • Developers who just want a simple code-completion helper without run governance
  • Teams unwilling to accept local JSONL run records with HMAC signing
  • Environments without a supported adapter (Claude/Codex/Gemini CLIs, direct provider, or verifier-only)
Required permissions
  • Requires access to the local server's database (PostgreSQL)
  • Requires Google OAuth credentials to access Google Search Console data
  • Requires network access to run crawls and fetch Core Web Vitals (e.g., via PageSpeed Insights)
  • Read/write access to the configured repo root (writable scope restrictable via --allow-path/--deny-path)
  • Ability to invoke the chosen agent CLI (Claude/Codex/Gemini, etc.) and its underlying model account
  • Local disk writes for run records, receipts, and share outputs (share/run-receipt., etc.)
  • Execution of user-configured verifier commands (e.g. npm test)
Risks and side effects
  • Data security risk: if the self-hosted instance is exposed to the internet without proper protection, data leakage may occur.
  • Dependence on third-party services (Google, PageSpeed Insights, DataForSEO) for availability and quota limits.
  • Open-source software may have unknown vulnerabilities; you must maintain and update it yourself.
  • Misconfiguration can prevent it from working, such as missing environment variables or a down database.
  • Verifier commands are executed; poorly chosen verifier commands carry security risk despite preflight policy checks
  • Cost and token figures may be estimates (labeled with provenance) and should not be treated as settled accounting
  • Receipt integrity must be verified before use as trustworthy evidence; missing rollback evidence is flagged as EVIDENCE_BOUNDARY
  • Policy defaults come from martin.config.yaml and can be overridden by CLI flags; misconfiguration can loosen safety boundaries
Supported clientsClaude DesktopClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools100