SkillAudit report — axiomhq/mcp
Scanned 2026-04-24 by SkillAudit v0.2 (static checks + LLM-assisted prompt-injection red-team).
Commit: c48f3b3 · Stars: 11 · Days since last push: 6
LLM prompt-injection probe: skipped — set ANTHROPIC_API_KEY to enable the LLM-assisted prompt-injection red-team
Overall grade: F (0/100)
| Axis | Score | Grade | |
|---|---|---|---|
| security | 0/100 | F | ❌ |
| permissions | 100/100 | A | ✅ |
| credentials | 100/100 | A | ✅ |
| maintenance | 100/100 | A | ✅ |
| compatibility | 70/100 | C | ⚠️ |
| docs | 90/100 | A | ✅ |
Security findings
Production sources:
- WARN
apps/mcp/src/auth.tsx:389— HTTP client call with user-controlled argument 'iconUrl' (validation markers present but not verified against this call-site)
const response = await fetch(iconUrl, {
- HIGH
apps/mcp/src/auth.tsx:218— Template-string URL with interpolation — no validation possible on composed string
const orgsResponse = await fetch(\${c.env.ATLAS_API_URL}/v1/orgs\, {
- WARN
apps/mcp/src/utils.ts:72— HTTP client call with user-controlled argument 'upstream_url' (validation markers present but not verified against this call-site)
const resp = await fetch(upstream_url, {
- WARN
apps/mcp/src/utils.ts:117— HTTP client call with user-controlled argument 'upstream_url' (validation markers present but not verified against this call-site)
const resp = await fetch(upstream_url, {
- HIGH
packages/mcp/src/axiom/client.ts:65— Template-string URL with interpolation — no validation possible on composed string
const res = await fetch(\${baseUrl}${path}\, options);
- WARN
scripts/oauth-test-server.ts:575— HTTP client call with user-controlled argument 'tokenUrl' (validation markers present but not verified against this call-site)
const tokenResponse = await fetch(tokenUrl, {
- HIGH
scripts/oauth-test-server.ts:463— Template-string URL with interpolation — no validation possible on composed string
const registerResponse = await fetch(\${baseUrl}/register\, {
- HIGH
scripts/oauth-test-server.ts:633— Template-string URL with interpolation — no validation possible on composed string
const upstream = await fetch(\${base}/sse\, {
- WARN
scripts/test-auth.ts:167— HTTP client call with user-controlled argument 'tokenUrl' (validation markers present but not verified against this call-site)
const tokenResponse = await fetch(tokenUrl, {
Permissions
_No findings on this axis._
Credentials
_No findings on this axis._
Maintenance
_No findings on this axis._
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
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 →