Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Evocrawl MCP Server

NPM · @EVOCRAWL/EVOCRAWL-MCP · SCANNED SEP 29

MCP server for Evocrawl — search, scrape, and interact with the web.

Available components

npm · @evocrawl/evocrawl-mcp 28
0 this week 28 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security80
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects @modelcontextprotocol/sdk 1.18.0, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 50 of 134 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
  • Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 156 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability0
  • Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we never saw its MCP handshake.Unverified

Unverified: 5 categories

Categories scored 0 because our sandbox has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

Install

How do I install the Evocrawl MCP Server server?

Evocrawl MCP Server runs locally as an npm package, launched with npx -y @evocrawl/evocrawl-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @evocrawl/evocrawl-mcp

# add to Claude Code
claude mcp add superaihuman-evocrawl-mcp -- npx -y @evocrawl/evocrawl-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "superaihuman-evocrawl-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@evocrawl/evocrawl-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "superaihuman-evocrawl-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@evocrawl/evocrawl-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add superaihuman-evocrawl-mcp -- npx -y @evocrawl/evocrawl-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "superaihuman-evocrawl-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@evocrawl/evocrawl-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add superaihuman-evocrawl-mcp --command npx --arg -y --arg @evocrawl/evocrawl-mcp
# ~/.hermes/config.yaml
mcp_servers:
  superaihuman-evocrawl-mcp:
    command: "npx"
    args: ["-y", "@evocrawl/evocrawl-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "superaihuman-evocrawl-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@evocrawl/evocrawl-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add superaihuman-evocrawl-mcp -t stdio -c npx -a -y @evocrawl/evocrawl-mcp
// mcp.json
{
  "mcpServers": {
    "superaihuman-evocrawl-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@evocrawl/evocrawl-mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 29 Sept 26 0
    • CVE-2026-44487 affects this package: high ▼ security
    • CVE-2026-42264 affects this package: high ▼ security
    • CVE-2026-67317 affects this package: high ▼ security
    • CVE-2026-25536 affects this package: high ▼ security
    • CVE-2026-67315 affects this package: high ▼ security
    • CVE-2026-44492 affects this package: high ▼ security
    • CVE-2026-42033 affects this package: high ▼ security
    • CVE-2026-42044 affects this package: high ▼ security
    • CVE-2026-42037 affects this package: high ▼ security
    • CVE-2026-67313 affects this package: high ▼ security
    • CVE-2026-42034 affects this package: high ▼ security
    • CVE-2026-44488 affects this package: high ▼ security
    • CVE-2026-42038 affects this package: high ▼ security
    • CVE-2025-66414 affects this package: high ▼ security
    • CVE-2026-44495 affects this package: high ▼ security
    • CVE-2026-42043 affects this package: high ▼ security
    • CVE-2026-42035 affects this package: high ▼ security
    • CVE-2026-42040 affects this package: high ▼ security
    • CVE-2026-67318 affects this package: high ▼ security
    • CVE-2026-42042 affects this package: high ▼ security
    • CVE-2026-42039 affects this package: high ▼ security
    • CVE-2026-0621 affects this package: high ▼ security
    • CVE-2026-44496 affects this package: high ▼ security
    • CVE-2026-67312 affects this package: high ▼ security
    • CVE-2026-44490 affects this package: high ▼ security
    • CVE-2026-67316 affects this package: high ▼ security
    • CVE-2026-42036 affects this package: high ▼ security
    • CVE-2026-42041 affects this package: high ▼ security
    • CVE-2026-44494 affects this package: high ▼ security
    • CVE-2026-67319 affects this package: high ▼ security
    • CVE-2026-44486 affects this package: high ▼ security
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Sept 26 0
    • CVE-2026-44487 affects this package: high ▼ security
    • CVE-2026-42264 affects this package: high ▼ security
    • CVE-2026-67317 affects this package: high ▼ security
    • CVE-2026-25536 affects this package: high ▼ security
    • CVE-2026-67315 affects this package: high ▼ security
    • CVE-2026-44492 affects this package: high ▼ security
    • CVE-2026-42033 affects this package: high ▼ security
    • CVE-2026-42044 affects this package: high ▼ security
    • CVE-2026-42037 affects this package: high ▼ security
    • CVE-2026-67313 affects this package: high ▼ security
    • CVE-2026-42034 affects this package: high ▼ security
    • CVE-2026-44488 affects this package: high ▼ security
    • CVE-2026-42038 affects this package: high ▼ security
    • CVE-2025-66414 affects this package: high ▼ security
    • CVE-2026-44495 affects this package: high ▼ security
    • CVE-2026-42043 affects this package: high ▼ security
    • CVE-2026-42035 affects this package: high ▼ security
    • CVE-2026-42040 affects this package: high ▼ security
    • CVE-2026-67318 affects this package: high ▼ security
    • CVE-2026-42042 affects this package: high ▼ security
    • CVE-2026-42039 affects this package: high ▼ security
    • CVE-2026-0621 affects this package: high ▼ security
    • CVE-2026-44496 affects this package: high ▼ security
    • CVE-2026-67312 affects this package: high ▼ security
    • CVE-2026-44490 affects this package: high ▼ security
    • CVE-2026-67316 affects this package: high ▼ security
    • CVE-2026-42036 affects this package: high ▼ security
    • CVE-2026-42041 affects this package: high ▼ security
    • CVE-2026-44494 affects this package: high ▼ security
    • CVE-2026-67319 affects this package: high ▼ security
    • CVE-2026-44486 affects this package: high ▼ security
  • 26 Sept 26 0
    • CVE-2026-44487 affects this package: high ▼ security
    • CVE-2026-42264 affects this package: high ▼ security
    • CVE-2026-67317 affects this package: high ▼ security
    • CVE-2026-25536 affects this package: high ▼ security
    • CVE-2026-67315 affects this package: high ▼ security
    • CVE-2026-44492 affects this package: high ▼ security
    • CVE-2026-42033 affects this package: high ▼ security
    • CVE-2026-42044 affects this package: high ▼ security
    • CVE-2026-42037 affects this package: high ▼ security
    • CVE-2026-67313 affects this package: high ▼ security
    • CVE-2026-42034 affects this package: high ▼ security
    • CVE-2026-44488 affects this package: high ▼ security
    • CVE-2026-42038 affects this package: high ▼ security
    • CVE-2025-66414 affects this package: high ▼ security
    • CVE-2026-44495 affects this package: high ▼ security
    • CVE-2026-42043 affects this package: high ▼ security
    • CVE-2026-42035 affects this package: high ▼ security
    • CVE-2026-42040 affects this package: high ▼ security
    • CVE-2026-67318 affects this package: high ▼ security
    • CVE-2026-42042 affects this package: high ▼ security
    • CVE-2026-42039 affects this package: high ▼ security
    • CVE-2026-0621 affects this package: high ▼ security
    • CVE-2026-44496 affects this package: high ▼ security
    • CVE-2026-67312 affects this package: high ▼ security
    • CVE-2026-44490 affects this package: high ▼ security
    • CVE-2026-67316 affects this package: high ▼ security
    • CVE-2026-42036 affects this package: high ▼ security
    • CVE-2026-42041 affects this package: high ▼ security
    • CVE-2026-44494 affects this package: high ▼ security
    • CVE-2026-67319 affects this package: high ▼ security
    • CVE-2026-44486 affects this package: high ▼ security
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 24 Sept 26 0
    • CVE-2026-44487 affects this package: high ▼ security
    • CVE-2026-42264 affects this package: high ▼ security
    • CVE-2026-67317 affects this package: high ▼ security
    • CVE-2026-25536 affects this package: high ▼ security
    • CVE-2026-67315 affects this package: high ▼ security
    • CVE-2026-44492 affects this package: high ▼ security
    • CVE-2026-42033 affects this package: high ▼ security
    • CVE-2026-42044 affects this package: high ▼ security
    • CVE-2026-42037 affects this package: high ▼ security
    • CVE-2026-67313 affects this package: high ▼ security
    • CVE-2026-42034 affects this package: high ▼ security
    • CVE-2026-44488 affects this package: high ▼ security
    • CVE-2026-42038 affects this package: high ▼ security
    • CVE-2025-66414 affects this package: high ▼ security
    • CVE-2026-44495 affects this package: high ▼ security
    • CVE-2026-42043 affects this package: high ▼ security
    • CVE-2026-42035 affects this package: high ▼ security
    • CVE-2026-42040 affects this package: high ▼ security
    • CVE-2026-67318 affects this package: high ▼ security
    • CVE-2026-42042 affects this package: high ▼ security
    • CVE-2026-42039 affects this package: high ▼ security
    • CVE-2026-0621 affects this package: high ▼ security
    • CVE-2026-44496 affects this package: high ▼ security
    • CVE-2026-67312 affects this package: high ▼ security
    • CVE-2026-44490 affects this package: high ▼ security
    • CVE-2026-67316 affects this package: high ▼ security
    • CVE-2026-42036 affects this package: high ▼ security
    • CVE-2026-42041 affects this package: high ▼ security
    • CVE-2026-44494 affects this package: high ▼ security
    • CVE-2026-67319 affects this package: high ▼ security
    • CVE-2026-44486 affects this package: high ▼ security
  • 23 Sept 26 0
    • CVE-2026-44487 affects this package: high ▼ security
    • CVE-2026-42264 affects this package: high ▼ security
    • CVE-2026-67317 affects this package: high ▼ security
    • CVE-2026-25536 affects this package: high ▼ security
    • CVE-2026-67315 affects this package: high ▼ security
    • CVE-2026-44492 affects this package: high ▼ security
    • CVE-2026-42033 affects this package: high ▼ security
    • CVE-2026-42044 affects this package: high ▼ security
    • CVE-2026-42037 affects this package: high ▼ security
    • CVE-2026-67313 affects this package: high ▼ security
    • CVE-2026-42034 affects this package: high ▼ security
    • CVE-2026-44488 affects this package: high ▼ security
    • CVE-2026-42038 affects this package: high ▼ security
    • CVE-2025-66414 affects this package: high ▼ security
    • CVE-2026-44495 affects this package: high ▼ security
    • CVE-2026-42043 affects this package: high ▼ security
    • CVE-2026-42035 affects this package: high ▼ security
    • CVE-2026-42040 affects this package: high ▼ security
    • CVE-2026-67318 affects this package: high ▼ security
    • CVE-2026-42042 affects this package: high ▼ security
    • CVE-2026-42039 affects this package: high ▼ security
    • CVE-2026-0621 affects this package: high ▼ security
    • CVE-2026-44496 affects this package: high ▼ security
    • CVE-2026-67312 affects this package: high ▼ security
    • CVE-2026-44490 affects this package: high ▼ security
    • CVE-2026-67316 affects this package: high ▼ security
    • CVE-2026-42036 affects this package: high ▼ security
    • CVE-2026-42041 affects this package: high ▼ security
    • CVE-2026-44494 affects this package: high ▼ security
    • CVE-2026-67319 affects this package: high ▼ security
    • CVE-2026-44486 affects this package: high ▼ security
  • 22 Sept 26 0
    • CVE-2026-44487 affects this package: high ▼ security
    • CVE-2026-42264 affects this package: high ▼ security
    • CVE-2026-67317 affects this package: high ▼ security
    • CVE-2026-25536 affects this package: high ▼ security
    • CVE-2026-67315 affects this package: high ▼ security
    • CVE-2026-44492 affects this package: high ▼ security
    • CVE-2026-42033 affects this package: high ▼ security
    • CVE-2026-42044 affects this package: high ▼ security
    • CVE-2026-42037 affects this package: high ▼ security
    • CVE-2026-67313 affects this package: high ▼ security
    • CVE-2026-42034 affects this package: high ▼ security
    • CVE-2026-44488 affects this package: high ▼ security
    • CVE-2026-42038 affects this package: high ▼ security
    • CVE-2025-66414 affects this package: high ▼ security
    • CVE-2026-44495 affects this package: high ▼ security
    • CVE-2026-42043 affects this package: high ▼ security
    • CVE-2026-42035 affects this package: high ▼ security
    • CVE-2026-42040 affects this package: high ▼ security
    • CVE-2026-67318 affects this package: high ▼ security
    • CVE-2026-42042 affects this package: high ▼ security
    • CVE-2026-42039 affects this package: high ▼ security
    • CVE-2026-0621 affects this package: high ▼ security
    • CVE-2026-44496 affects this package: high ▼ security
    • CVE-2026-67312 affects this package: high ▼ security
    • CVE-2026-44490 affects this package: high ▼ security
    • CVE-2026-67316 affects this package: high ▼ security
    • CVE-2026-42036 affects this package: high ▼ security
    • CVE-2026-42041 affects this package: high ▼ security
    • CVE-2026-44494 affects this package: high ▼ security
    • CVE-2026-67319 affects this package: high ▼ security
    • CVE-2026-44486 affects this package: high ▼ security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 29 Sept 2026 · Analysed npm/@evocrawl/evocrawl-mcp@4.0.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 31 findings
ID CVE Severity Vector Fix available
GHSA-345p-7cg4-v4c7 CVE-2026-25536 high CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N yes
GHSA-8r9q-7v3j-jr4g CVE-2026-0621 high yes
GHSA-w48q-cv73-mx4w CVE-2025-66414 high yes
GHSA-35jp-ww65-95wh CVE-2026-44494 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N yes
GHSA-3g43-6gmg-66jw CVE-2026-44495 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:L yes
GHSA-3w6x-2g7m-8v23 CVE-2026-42044 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:N yes
GHSA-42h9-826w-cgv3 CVE-2026-67313 medium yes
GHSA-445q-vr5w-6q77 CVE-2026-42037 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N yes
GHSA-5c9x-8gcm-mpgx CVE-2026-42034 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L yes
GHSA-62hf-57xw-28j9 CVE-2026-42039 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-6chq-wfr3-2hj9 CVE-2026-42035 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N yes
GHSA-777c-7fjr-54vf CVE-2026-44488 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-7q8q-rj6j-mhjq CVE-2026-67319 medium yes
GHSA-898c-q2cr-xwhg CVE-2026-44490 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L yes
GHSA-f4gw-2p7v-4548 CVE-2026-67315 medium yes
GHSA-hfxv-24rg-xrqf CVE-2026-44496 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-j5f8-grm9-p9fc CVE-2026-44486 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N yes
GHSA-jqh4-m9w3-8hp9 CVE-2026-67317 medium yes
GHSA-m7pr-hjqh-92cm CVE-2026-42038 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N yes
GHSA-mmx7-hfxf-jppx CVE-2026-67316 medium yes
GHSA-mwf2-3pr3-8698 CVE-2026-67318 medium yes
GHSA-p92q-9vqr-4j8v CVE-2026-44487 high yes
GHSA-pf86-5x62-jrwf CVE-2026-42033 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N yes
GHSA-pjwm-pj3p-43mv CVE-2026-44492 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N yes
GHSA-pmv8-rq9r-6j72 CVE-2026-67312 medium yes
GHSA-pmwg-cvhr-8vh7 CVE-2026-42043 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N yes
GHSA-q8qp-cvcw-x6jj CVE-2026-42264 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N yes
GHSA-vf2m-468p-8v99 CVE-2026-42036 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L yes
GHSA-w9j2-pvgh-6h63 CVE-2026-42041 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N yes
GHSA-xhjh-pmcv-23jw CVE-2026-42040 low CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N yes
GHSA-xx6v-rp6x-q39c CVE-2026-42042 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 134 packages
Packages resolved 134
Stale 50
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

Common questions

What is the Evocrawl MCP Server server?

Evocrawl MCP Server is listed in the public MCP registry as io.github.superaihuman/evocrawl-mcp. MCP server for Evocrawl, search, scrape, and interact with the web. This page covers its npm package (@evocrawl/evocrawl-mcp).

Is the Evocrawl MCP Server server safe to use?

Evocrawl MCP Server scores 28 out of 100 on VerifyMCP. We recorded 31 known advisories against it as of 29 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

Is the Evocrawl MCP Server server still maintained?

Evocrawl MCP Server is still listed as active in the MCP registry. We last reached this channel on 29 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Evocrawl MCP Server server under?

Evocrawl MCP Server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.