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.

DimensionHermes Atlas MCP ServerBring the Hermes Atlas ecosystem catalog to any MCP client.Firecrawl MCP ServerFirecrawl's official MCP server for web search, scraping, and structured extraction for AI agents
FMRS43 / 100 · D75 / 100 · B
Reliability6 / 2013 / 20
Security and permissions10 / 2012 / 20
Maintenance8 / 2016 / 20
Documentation7 / 2017 / 20
Setup experience12 / 2017 / 20
Best for
  • Developers and teams using Hermes Agent who want to discover community tools and integrations.
  • Users who want to access live catalog information through MCP clients like Claude Desktop, Cursor, etc.
  • Users who need up-to-date ecosystem data, as data is fetched live and cached briefly.
  • Scenarios needing clean, structured web context fed to an AI assistant
  • Users already on the Firecrawl platform who want to call its scraping capability directly via MCP
Not for
  • Users needing offline catalog access independent of the internet (data is fetched live from hermesatlas.com).
  • Users who want long-term caching or to avoid external API dependencies (optional Redis provides longer caching, but default is in-memory only).
  • Users needing official oversight or support, as this server is maintained by a contributor, not the official Hermes project.
  • Simple static-page scraping where you don't want to depend on a third-party API and incur call costs
  • Sites that explicitly disallow automated access (robots.txt)
Required permissions
  • Network access: fetch live catalog data and API requests from hermesatlas.com.
  • File system access: for the installer, read and write client config files (e.g., claude_desktop_config.json).
  • Optional: access to Redis if REDIS_URL is set.
  • Requires a Firecrawl API key to call; cost and quota are governed by the Firecrawl account
  • firecrawl_agent/firecrawl_interact perform automated browser interaction, which may trigger login or form-submission flows on the target site
Risks and side effects
  • Data is sourced from a third-party API (hermesatlas.com), which could affect reliability if the site or API changes.
  • The installer modifies client config files, which could break existing MCP setups if done incorrectly; use --print for a dry run.
  • Since the server is experimental (0.x), breaking changes may occur.
  • Bulk crawl/map tools can generate significant request volume against a target site — respect the site's rate limits and terms of service
  • firecrawl_agent's interactive action chain is longer — define task boundaries clearly before running it to avoid accidentally triggering actions on a sensitive site
Supported clientsClaude Desktop, Cursor, Continue, WindsurfClaude Desktop, VS Code, Cursor, Windsurf, Zed, Amp
Tools611