SkillAudit report — langchain-ai/langchain-mcp-adapters
Scanned 2026-04-24 by SkillAudit v0.2 (static checks + LLM-assisted prompt-injection red-team).
Commit: 174c48e · Stars: 3498 · Days since last push: 1
LLM prompt-injection probe: no-tool-surface
Overall grade: A (100/100)
| Axis | Score | Grade | |
|---|---|---|---|
| security | 100/100 | A | ✅ |
| permissions | 100/100 | A | ✅ |
| credentials | 100/100 | A | ✅ |
| maintenance | 100/100 | A | ✅ |
| compatibility | 100/100 | A | ✅ |
| docs | 100/100 | A | ✅ |
Security findings
_No findings on this axis._
Permissions
_No findings on this axis._
Credentials
_No findings on this axis._
Maintenance
_No findings on this axis._
Compatibility
_No findings on this axis._
Documentation
_No findings on this axis._
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
execFilewith argv arrays instead ofexecwith template strings; never pass untrusted strings tosubprocesswithshell=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_
Want your repo audited?
First 100 audits go to waitlist signups in order. The engine runs against public GitHub URLs today.
Join the waitlist →