npm analyzed 2.0.0-alpha.2

@modelcontextprotocol/client

v2.0.0-alpha.2

npm

Model Context Protocol implementation for TypeScript - Client package

Drift inferred · capture-to-capture

HIGH 2026-06-09 code analysis flagged dynamic code execution in @modelcontextprotocol/client

capabilities 0 tools

transport streamable-http counts 0 tools · 0 res · 0 prompts permission surface via code analysis

no tools enumerated yet for this server.

skills & danger signals npm-tarball

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

analyzed v2.0.0-alpha.2 · analyzer v18 · 7h ago

dynamic code executionnew Function()package/dist/src-RIHfgPRm.mjs:5757const validate = new Function(`${names_1.default.self}`, `${names_1.default.scope}`, sourceCode)(this, this.scope.get());

code evidence v2.0.0-alpha.2 · npm-tarball

evidence-backed findings quoted directly from the published source artifact — not inferred

shell package/dist/index.mjs :2905 this._process = spawn(this._serverParams.command, this._serverParams.args ?? [], {

net package/dist/index.mjs :660 * However, `fetch()` also throws `TypeError` for non-CORS failures (DNS resolution, connection
net package/dist/shimsBrowser.mjs :5 * Whether `fetch()` may throw `TypeError` due to CORS. Only true in browser contexts
net package/dist/shimsNode.mjs :5 * Whether `fetch()` may throw `TypeError` due to CORS. CORS is a browser-only concept —
net package/dist/shimsWorkerd.mjs :5 * Whether `fetch()` may throw `TypeError` due to CORS. CORS is a browser-only concept —