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.

DimensionOmnisearch MCP ServerUnified access to multiple search engines, AI answers, and content extraction through one interfaceMartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS60 / 100 · C79 / 100 · B
Reliability10 / 2012 / 20
Security and permissions10 / 2018 / 20
Maintenance12 / 2016 / 20
Documentation15 / 2018 / 20
Setup experience13 / 2015 / 20
Best for
  • Developers who want multiple search and extraction providers behind a single configuration
  • MCP client users who want to choose providers per task
  • Coding assistant scenarios needing GitHub search and web content extraction
  • 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 unwilling to supply any third-party search or extraction API keys
  • Scenarios requiring official support from the upstream product owner
  • Environments that cannot run Node.js or npx
  • 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
  • Read provider API keys from environment variables (TAVILY_API_KEY, KAGI_API_KEY, BRAVE_API_KEY, GITHUB_API_KEY, EXA_API_KEY, LINKUP_API_KEY, FIRECRAWL_API_KEY)
  • Network access to provider APIs and target web pages
  • Write large-result files when file mode is used
  • 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
  • Queries and target URLs are sent to third-party services, which may raise data exposure or privacy concerns
  • API keys are stored as environment variables and may leak if misconfigured
  • Providers differ in usage, quotas, and rate limits, so calls may fail on throttling or insufficient access
  • Providers without keys are unavailable
  • The docs note caveats around large-result file mode and remote deployment
  • 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 Code, VS CodeClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools40