SkillAudit report — modelcontextprotocol/servers

Scanned 2026-04-23 by SkillAudit v0.2 (static checks + LLM-assisted prompt-injection red-team).

Commit: 4503e2d · Stars: 84406 · Days since last push: 5

LLM prompt-injection probe: skipped — set ANTHROPIC_API_KEY to enable the LLM-assisted prompt-injection red-team

Overall grade: C (70/100)

Security findings

Production sources:

• WARN src/everything/tools/gzip-file-as-resource.ts:190 — HTTP client call with user-controlled argument 'url' (validation markers present but not verified against this call-site)

const response = await fetch(url, { signal: controller.signal });

Permissions

_No findings on this axis._

Credentials

_No findings on this axis._

Maintenance

Production sources:

• WARN (meta) — 386 open issues — triage backlog

386 open

Compatibility

Production sources:

• WARN (meta) — No engines (Node) or python_requires declared — cross-client compatibility unverified

Documentation

Production sources:

• WARN package.json — package.json missing repository field

no repository

Methodology

SkillAudit v0.2 clones the repo at the provided ref (default: default branch, HEAD) into an ephemeral sandbox, runs six static checks over .js/.ts/.py sources, queries the GitHub API for maintenance signals, and runs an LLM-assisted prompt-injection red-team over the MCP tool surface. Each axis is scored against the rubric at .

The prompt-injection axis extracts each server.tool(...) / @app.tool registration + the first ~60 lines of handler body, hands them to Claude Haiku 4.5 with a red-team system prompt, and asks for structured findings on untrusted-content flow into tool responses. One API call per scan, bounded at ~15K input tokens.

How to improve this grade

• Security — static: validate tool-input URLs against an allowlist before fetch/axios calls; use execFile with argv arrays instead of exec with template strings; never pass untrusted strings to subprocess with shell=True.
• Security — prompt injection: never return fetched web-page / file / email content verbatim in a tool response. Wrap with a framing marker (e.g., <untrusted-content>...</untrusted-content>), summarize rather than inline, and never let untrusted content share a turn with credentials or other tool output.
• Credentials findings: redact env-var reads before log lines and error messages; treat any string that ends up in a tool response as public.
• Maintenance: if the repo is inactive, document the maintenance model — "MCP tool, no breaking changes expected" is a legitimate signal.
• Docs: add a README install + usage section with a copy-pasteable command; add a SECURITY.md with a disclosure channel.

_Report generated by skillaudit.dev_