Evocrawl MCP Server
NPM · @EVOCRAWL/EVOCRAWL-MCP · SCANNED AUG 3
MCP server for Evocrawl — search, scrape, and interact with the web.
Available components
+6 this week
25 25 Trust /100
Trust breakdown (6 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 →
Supply Chain Security70
- 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
- Only part of the dependency tree could be resolved (136 of 137), so this covers what we could see, not the whole tree. 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 99 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: our sandbox run of this package did not complete, so we have no schema to assess.Unverified
Stability & Change Management0
- Stability not yet verified: our sandbox run of this package did not complete, so we have no schema to compare.Unverified
Tool Coverage0
- Tool coverage not yet verified: our sandbox run of this package did not complete, so we have no tool definitions to assess.Unverified
Capabilities0
- Protocol version not yet verified: our sandbox run of this package did not complete, so we never saw its MCP handshake.Unverified
Unverified: 4 categories
Categories scored 0 because our sandbox run of this package 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
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @evocrawl/evocrawl-mcp
# add to Claude Code
claude mcp add superaihuman-evocrawl-mcp -- npx -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"] // 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.
- 3 Aug 26 0
- CVE-2026-44487 affects this package: high ▼ security
- CVE-2026-44486 affects this package: high ▼ security
- CVE-2026-67319 affects this package: high ▼ security
- CVE-2026-44494 affects this package: high ▼ security
- CVE-2026-42041 affects this package: high ▼ security
- CVE-2026-42036 affects this package: high ▼ security
- CVE-2026-67316 affects this package: high ▼ security
- CVE-2026-44490 affects this package: high ▼ security
- CVE-2026-67312 affects this package: high ▼ security
- CVE-2026-44496 affects this package: high ▼ security
- CVE-2026-0621 affects this package: high ▼ security
- CVE-2026-42039 affects this package: high ▼ security
- CVE-2026-42042 affects this package: high ▼ security
- CVE-2026-67318 affects this package: high ▼ security
- CVE-2026-42040 affects this package: high ▼ security
- CVE-2026-42035 affects this package: high ▼ security
- CVE-2026-42043 affects this package: high ▼ security
- CVE-2026-44495 affects this package: high ▼ security
- CVE-2025-66414 affects this package: high ▼ security
- CVE-2026-42038 affects this package: high ▼ security
- CVE-2026-44488 affects this package: high ▼ security
- CVE-2026-42034 affects this package: high ▼ security
- CVE-2026-67313 affects this package: high ▼ security
- CVE-2026-42037 affects this package: high ▼ security
- CVE-2026-42044 affects this package: high ▼ security
- CVE-2026-42033 affects this package: high ▼ security
- CVE-2026-44492 affects this package: high ▼ security
- CVE-2026-67315 affects this package: high ▼ security
- CVE-2026-25536 affects this package: high ▼ security
- CVE-2026-67317 affects this package: high ▼ security
- CVE-2026-42264 affects this package: high ▼ security
- 2 Aug 26 +10
- 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
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. functional
- Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
- Capabilities: Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet. functional
- Licence: MIT functional
- 1 Aug 26 +15
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: our sandbox run of this package did not complete, so we have no schema to compare. security
- Tool coverage: Tool coverage not yet verified: our sandbox run of this package did not complete, so we have no tool definitions to assess. functional
- Schema quality: Schema quality not yet verified: our sandbox run of this package did not complete, so we have no schema to assess. functional
- Capabilities: Protocol version not yet verified: our sandbox run of this package did not complete, so we never saw its MCP handshake. functional
- 31 Jul 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
- 30 Jul 26 −34
- Known CVEs: fail → unverified ▼ security
- Provenance: fail → unverified ▼ security
- Malware scan: pass → unverified ▼ security
- Install scripts: pass → unverified ▼ security
- License: pass → unverified ▼ functional
- Dependency health: partial → unverified ▼ functional
- Maintenance: pass → unverified ▼ functional
- Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
- Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. functional
- Licence: MIT functional
- 29 Jul 26 +12
- CVE-2026-42044 affects this package: high ▼ security
- CVE-2026-42033 affects this package: high ▼ security
- CVE-2026-44492 affects this package: high ▼ security
- CVE-2026-44494 affects this package: high ▼ security
- GHSA-mwf2-3pr3-8698 affects this package: high ▼ security
- CVE-2026-44486 affects this package: high ▼ security
- CVE-2026-42041 affects this package: high ▼ security
- CVE-2026-42036 affects this package: high ▼ security
- GHSA-f4gw-2p7v-4548 affects this package: high ▼ security
- CVE-2026-44490 affects this package: high ▼ security
- GHSA-7q8q-rj6j-mhjq affects this package: high ▼ security
- CVE-2026-44496 affects this package: high ▼ security
- CVE-2026-0621 affects this package: high ▼ security
- CVE-2026-42039 affects this package: high ▼ security
- GHSA-42h9-826w-cgv3 affects this package: high ▼ security
- CVE-2026-42042 affects this package: high ▼ security
- CVE-2026-42040 affects this package: high ▼ security
- CVE-2026-42035 affects this package: high ▼ security
- CVE-2026-42043 affects this package: high ▼ security
- CVE-2026-44495 affects this package: high ▼ security
- CVE-2025-66414 affects this package: high ▼ security
- CVE-2026-42038 affects this package: high ▼ security
- CVE-2026-44488 affects this package: high ▼ security
- CVE-2026-42034 affects this package: high ▼ security
- CVE-2026-42037 affects this package: high ▼ security
- CVE-2026-42264 affects this package: high ▼ security
- CVE-2026-44487 affects this package: high ▼ security
- GHSA-jqh4-m9w3-8hp9 affects this package: high ▼ security
- GHSA-mmx7-hfxf-jppx affects this package: high ▼ security
- CVE-2026-25536 affects this package: high ▼ security
- GHSA-pmv8-rq9r-6j72 affects this package: high ▼ security
- Known CVEs: unverified → fail ▼ security
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- License: unverified → pass ▲ functional
- Maintenance: unverified → pass ▲ functional
- Tool coverage: Tool coverage not yet verified: our sandbox run of this package did not complete, so we have no tool definitions to assess. functional
- Schema quality: Schema quality not yet verified: our sandbox run of this package did not complete, so we have no schema to assess. functional
- Licence: MIT functional
- 28 Jul 26 +3
No change was recorded against any check on this day. Supply Chain Security went from 52 to 61.
- 27 Jul 26 19
First indexed and scored.
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 3 Aug 2026 · Analysed npm/@evocrawl/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
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 |
Dependencies 136 packages
136 packages in the resolved dependency tree · 135 deprecated · 46 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
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.