MCP Observatory
npm analyzed 4.38.0

@kubb/plugin-mcp

v4.38.0
npm

Model Context Protocol (MCP) plugin for Kubb, generating MCP-compatible tools and schemas from OpenAPI specifications for AI assistants.

maintainer
stijnvanhulle
license
MIT
first seen
2026-05-22
last seen
2026-06-14
releases · 30d
151
short id
risk33/100 · heuristic grade
B low
  • recent driftinferred+20
  • inherited (deps)attested+15
  • tool safetyinferred+12
  • trust mitigatorsmixed−14

attestedinferredmixed

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

risk trajectory2 movements
  • C · 43 → B · 33
  • B · 21 → C · 43
vulnerabilities0 CVEs

no known CVEs for this server.

inherited (deps) · grade factor +15

inherited via dependencies3
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 safety1 findings · grade factor +12
  1. highdangerous code

    dynamic exec: new Function()

skills & danger signalsnpm-tarball
prompt-surface shipped agent-instruction files + hidden-content / dangerous-code findings — quoted from the analyzed source

analyzed v4.38.0 · analyzer v17 · 1d ago

danger signals2

other grade factorsevidence elsewhere
embed badgereadme-ready
live risk-grade badge preview [![MCP Observatory risk grade](https://mcpobservatory.com/servers/npm:@kubb/plugin-mcp/badge.svg)](https://mcpobservatory.com/servers/npm:@kubb/plugin-mcp/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 stijnvanhulle.