Caveat verdict

docparse

va-docparse

88
🟢 Trusted
No high-risk patterns surfaced by the deep scan — automated capability review, not behavioral proof.

Document parsing skill connecting to a user-configured MCP server endpoint via user-provided API key; sink detection is from documented pip install commands, not malicious execution.

⚠ Flagged for review — coarse, uncorroborated signal, not a confirmed exploit. Review the config yourself before installing.

Automated static analysis — not a human review. Caveat flags capabilities, not confirmed intent, and can produce false positives. Disagree with this verdict? Use Dispute below.

23
security
50
transparency
70
maintenance

Permission integrity

Code accesses API keys/tokens but declares no environment variables

credential_access

Findings (5)

Pattern match critical

Possible hardcoded credential

SKILL.md · code · API_KEY: "your-api-key

Pattern match medium

Instructs covert action — may act without user awareness

mcp/docparse.py · prose · downgraded · Silently

Pattern match medium

subprocess execution — runs system commands from Python

setup.py · prose · downgraded · subprocess.run(

Pattern match medium

HTTP request to bare IP address — common in malicious payloads

setup.py · prose · downgraded · http://10.24.9.2

Pattern match low

Python os.environ.get — reads environment variable

mcp/docparse.py · prose · downgraded · os.environ.get(

Why the tier is capped

Execution sink present in raw bytes (Hard Floor: class D). Final tier capped at Caution — cannot be lifted by any downgrade, example-payload opt-in, or allowlist.

Permissions & capabilities

No declared permissions — minimal attack surface.

network_incredential_access

Is this flag fair?

Check another skill Browse the registry Auditing your own skills or configs? Use the API