npm JavaScript analyzed 0.14.1

@apify/actors-mcp-server

v0.14.1
npm

Apify MCP Server

maintainer
b4nan
license
MIT
first seen
2026-05-22
last seen
2026-08-02
releases · 30d
50
short id
risk 41/100 · heuristic grade
C elevated
  • vulnerabilities attested + 13
  • capability exposure inferred + 35
  • inherited (deps) attested + 15
  • trust mitigators mixed − 22

attested inferred mixed

The A–E grade is our heuristic synthesis — a "review this" prompt, not a verdict. Each factor is tagged by what backs it: attested (a verifiable record), reported (a third party's claim), or inferred (our own heuristic, e.g. permissions). See methodology.

graded 2m ago · see ecosystem CVEs →

risk trajectory 7 movements
  • B · 32 C · 41
  • B · 25 B · 32
  • B · 21 B · 25
  • B · 25 B · 21
  • B · 21 B · 25
  • B · 25 B · 21
  • B · 32 B · 25
capability exposure grade factor +35
Inferred surface — each links to servers holding it:
vulnerabilities 2 CVEs · grade factor +13
HIGH
Apify Model Context Protocol (MCP) server: Actor MCP path authority injection leaks Apify token CVE-2026-50143 CVSS 8.1 affects [{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.10.11"}]}] fixed in 0.10.11 GHSA GHSA
MEDIUM
Apify Model Context Protocol (MCP) server: Domain Allowlist Bypass in fetch-apify-docs via String Pr … EPSS 0% CVE-2026-46341 CVSS 6.1 affects [{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.9.21"}]}] fixed in 0.9.21 GHSA GHSA

inherited (deps) · grade factor +15

inherited via dependencies 3
HIGH
@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse via @modelcontextprotocol/sdk · 1 hop CVE-2026-25536 fixed in 1.26.0
HIGH
Anthropic's MCP TypeScript SDK has a ReDoS vulnerability via @modelcontextprotocol/sdk · 1 hop CVE-2026-0621 fixed in 1.25.2
HIGH
Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default via @modelcontextprotocol/sdk · 1 hop CVE-2025-66414 fixed in 1.24.0
tool safety all quiet

No tool-safety findings — heuristic detectors run on the compute-risk cadence; a finding appears when a tool trips a rule.

embed badge readme-ready
live risk-grade badge preview [![MCP Observatory risk grade](https://mcpobservatory.com/servers/npm:@apify/actors-mcp-server/badge.svg)](https://mcpobservatory.com/servers/npm:@apify/actors-mcp-server/security)

Heuristic, inferred signals — false positives (legitimately powerful tools, forks, language ports) are expected. Treat each as "review this", not a verdict. See the ecosystem-wide picture on the security hub, or the fleet security of b4nan.