npm JavaScript not analyzable

@adcp/sdk

v12.1.1
npm

not analyzable — repository too large to scan in full

AdCP SDK — client, server, and compliance harnesses for the AdContext Protocol (MCP + A2A)

maintainer
brianokelley
license
Apache-2.0
first seen
2026-05-30
last seen
2026-08-02
releases · 30d
20
short id
risk 41/100 · heuristic grade
C elevated

Source not yet analyzed — this grade rests on attested signals (CVEs, supply-chain) only. It is a floor: reading the code could raise it, not lower it.

  • capability exposure inferred + 35
  • inherited (deps) attested + 15
  • trust mitigators mixed − 9

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 1m ago · see ecosystem CVEs →

risk trajectory 2 movements
  • C · 47 C · 41
  • C · 59 C · 47
capability exposure grade factor +35
Inferred surface — each links to servers holding it:
vulnerabilities 0 CVEs

No known CVEs for this server.

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:@adcp/sdk/badge.svg)](https://mcpobservatory.com/servers/npm:@adcp/sdk/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 brianokelley.