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.

DimensionSearch1API MCP ServerWeb search, news, crawling, sitemaps, and trends in one MCP server.GitHub MCP ServerGitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language
FMRS67 / 100 · C76 / 100 · B
Reliability10 / 2013 / 20
Security and permissions12 / 2014 / 20
Maintenance16 / 2018 / 20
Documentation15 / 2017 / 20
Setup experience14 / 2014 / 20
Best for
  • Developers who need reliable, high-quality search capabilities
  • AI applications requiring multiple search functions with easy integration
  • Remote MCP scenarios where OAuth simplifies authentication
  • Teams that want an AI assistant to directly operate on GitHub repos and collaboration workflows
  • Users already in the GitHub Copilot ecosystem who want a zero-deployment remote option
Not for
  • Users who need fully offline or external-API-free operation
  • Scenarios where searching private data or keeping data local is required
  • High-volume crawling due to extra credit costs per crawl
  • Scenarios where you don't want the assistant to have write access to repos (enable only read-only toolsets)
  • Environments with strict network isolation for private repos that can't reach the official remote endpoint
Required permissions
  • Requires Search1API API key (local) or OAuth authorization (remote)
  • Remote mode trusts mcp.search1api.com and localhost by default; self-hosted deployments can configure MCP_ALLOWED_HOSTS and MCP_ALLOWED_ORIGINS
  • Search and crawl actions may consume API credits
  • A personal access token (PAT) or OAuth App token; effective scope depends on the token's own permissions
  • Enabling toolsets like actions/issues/pull_requests grants write access — request tokens on a least-privilege basis
Risks and side effects
  • API key leakage: passing key via URL query parameter can expose it in logs; prefer OAuth or Authorization header
  • Network dependency: remote mode requires access to mcp.search1api.com
  • Data privacy: search queries and crawled content are sent to third-party API
  • Rate limits and costs: high-frequency requests may incur charges or be throttled
  • Write toolsets (creating/merging PRs, triggering workflows) can cause accidental changes if the token is overscoped — try a read-only toolset first
  • In hosted mode, credentials travel via the Authorization header — make sure the client-to-api.githubcopilot.com connection is trusted
Supported clientsClaude Desktop, Claude.ai, Cursor, VS Code, Claude Code, WindsurfClaude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Zed, Amp
Tools515