| FMRS | 52 / 100 · D | 75 / 100 · B | 73 / 100 · B |
|---|
| Reliability | 9 / 20 | 13 / 20 | 12 / 20 |
|---|
| Security and permissions | 8 / 20 | 12 / 20 | 13 / 20 |
|---|
| Maintenance | 11 / 20 | 16 / 20 | 16 / 20 |
|---|
| Documentation | 12 / 20 | 17 / 20 | 16 / 20 |
|---|
| Setup experience | 12 / 20 | 17 / 20 | 16 / 20 |
|---|
| Best for | - SRE, DevOps, and network engineering teams using Kubernetes.
- Incident response and root-cause analysis requiring cluster-wide network, API, and Kubernetes context.
- Teams that want MCP-compatible AI agents to query live or retained network data.
| - 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
| - Q&A and research scenarios that need real-time, clean web content
- Users with an existing Exa account who want a zero-deployment remote option
|
|---|
| Not for | - Users who do not run Kubernetes or do not need network traffic observability.
- Client scenarios requiring only generic file, database, or collaboration features.
- Environments where handling sensitive traffic or decrypting TLS/mTLS is unacceptable.
| - 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)
| - Scenarios requiring a strict allowlist of search sources that can't use a third-party search service
- Budget-sensitive, high-volume search scenarios (remote/API calls may incur cost)
|
|---|
| Required permissions | - Proxy mode requires a kubeconfig with access to the Kubernetes cluster.
- Direct URL mode requires access to an existing Kubeshark Hub URL.
- Start and stop operations require explicitly enabling --allow-destructive.
- The source does not specify exact Kubernetes RBAC permissions or authentication mechanisms.
| - 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
| - Requires an Exa API key for full functionality; OAuth login is optional in remote mode
- web_fetch_exa retrieves content from a specified URL; agent_run performs multi-step autonomous actions and needs the user to have clear expectations of Agent behavior
|
|---|
| Risks and side effects | - The server can deploy or remove Kubeshark; start_kubeshark and stop_kubeshark are marked destructive.
- Observed data may include complete API requests, headers, bodies, and PCAPs.
- TLS/mTLS traffic can be decrypted into plaintext, potentially exposing sensitive information.
- The source does not specify access-control, authentication, or data-retention policies.
| - 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
| - The API key should be stored carefully — avoid leaving it in plaintext in client config files on untrusted machines
- agent_run is a multi-step autonomous tool with a longer action chain — try it on low-risk tasks first
|
|---|
| Supported clients | Claude Code, Cursor | Claude Desktop, VS Code, Cursor, Windsurf, Zed, Amp | Claude Desktop, Claude Code, VS Code, Cursor, Windsurf, Zed, Amp, Kiro, LM Studio, Antigravity |
|---|
| Tools | 14 | 11 | 4 |
|---|