SkillAudit report — sooperset/mcp-atlassian
Scanned 2026-04-24 by SkillAudit v0.2 (static checks + LLM-assisted prompt-injection red-team).
Commit: d8bc786 · Stars: 5013 · Days since last push: 13
LLM prompt-injection probe: no-tool-surface
Overall grade: F (10/100)
| Axis | Score | Grade | |
|---|---|---|---|
| security | 10/100 | F | ❌ |
| permissions | 100/100 | A | ✅ |
| credentials | 70/100 | C | ⚠️ |
| maintenance | 90/100 | A | ✅ |
| compatibility | 100/100 | A | ✅ |
| docs | 90/100 | A | ✅ |
Security findings
Production sources:
- HIGH
src/mcp_atlassian/jira/users.py:244— HTTP client call with user-controlled argument 'url' — no URL allowlist / validation found in file
response = requests.get(
- HIGH
src/mcp_atlassian/utils/oauth.py:177— HTTP client call with user-controlled argument 'token_endpoint' — no URL allowlist / validation found in file
response = requests.post(token_endpoint, data=payload, timeout=HTTP_TIMEOUT)
- HIGH
src/mcp_atlassian/utils/oauth.py:322— HTTP client call with user-controlled argument 'CLOUD_ID_URL' — no URL allowlist / validation found in file
response = requests.get(CLOUD_ID_URL, headers=headers, timeout=HTTP_TIMEOUT)
Test-site findings (lower weight): 21 total in test/ paths — first 3 shown
- HIGH
tests/e2e/cloud/conftest.py:123— Template-string URL with interpolation — no validation possible on composed string
resp = requests.get(
- HIGH
tests/e2e/cloud/conftest.py:136— Template-string URL with interpolation — no validation possible on composed string
resp = requests.get(
- HIGH
tests/e2e/cloud/conftest.py:158— Template-string URL with interpolation — no validation possible on composed string
resp = requests.post(
Permissions
_No findings on this axis._
Credentials
Production sources:
- WARN
.env.example— .env file present in repo tree — verify it's a template, not real secrets
.env.example
- WARN
tests/e2e/docker/.env.example— .env file present in repo tree — verify it's a template, not real secrets
tests/e2e/docker/.env.example
Test-site findings (lower weight): 2 total in test/ paths — first 3 shown
- HIGH
tests/unit/utils/test_custom_headers.py:135— Hardcoded OpenAI / Anthropic-style API key found in source
sk-*** (OpenAI / Anthropic-style API key, 19 chars)
- HIGH
tests/unit/utils/test_custom_headers.py:145— Hardcoded OpenAI / Anthropic-style API key found in source
sk-*** (OpenAI / Anthropic-style API key, 19 chars)
Maintenance
Production sources:
- WARN
(meta)— 270 open issues — triage backlog
270 open
Compatibility
_No findings on this axis._
Documentation
Production sources:
- WARN
README— README has no usage/example section
no usage section
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 →