Skills/PyPI/readystack-mcp-config-audit

readystack-mcp-config-audit@1.0.7.post1

VERIFIED· install only

Publisher claims: "Audit one mcp.json for what an agent config gives away — inline API keys, unpinned npx launches, plaintext remote servers, shell wrappers, auto-approved tools, whole-machine filesystem roots — with li (bundled Node.js runtime)" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher readystack-support · publishing for 48 daysInstalls 73Last detonated 1 h ago
$claude mcp add readystack-mcp-config-audit -- uvx readystack-mcp-config-audit
WatchReport an issue

Coverage

Nothing executable in the bundle ran; the trace covers the install step only.
Tested
every file read, file written and host contacted by what ran
Not tested
use of the skill by an agent

What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.

Before you give it your token

It will ask for
no credential variables read in the code
Where it talks to
no vendor host named in the codeAlso getreadystack.com — not the publisher's domain; check what for before connecting.
What the honeypot saw
no credential files read · no network
What we could not test
use of the skill by an agent

Connect it under the guard. Nothing executable in the bundle ran; the trace covers the install step only. The code names no credential variable; the guard pins the network to what the honeypot saw and logs every call.

$vet-skills run --net declared -- uvx readystack-mcp-config-audit

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (1 scenario; nothing executable in the bundle ran; the trace covers the install step only) on 2026-11-15 and scored it 83/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 0 s · 1 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
0.0sprocessscript backend runs setup only
0.0sprocessscript backend runs setup only
0.0sprocessno install scripts to re-run

Static findings

MEDIUM
npx invocation of non-well-known packagesrc/readystack_mcp_config_audit/js/rules.json:30 · npx invocation of non-well-known package — may execute untrusted code… "sev": "error", "title": "npx launches a package with no version", "msg": "npx with no version resolves the newest published version at every launch, so the code t…Fix: Pin versions and sources; vendor anything fetched at install time.
AST06
MEDIUM
File type combined with upload actionsrc/readystack_mcp_config_audit/js/rules.json:24 · File type combined with upload action — agent may exfiltrate local data files"std": "VS Code mcp.json inputs"Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.
AST07
HIGH
Access to sensitive file pathssrc/readystack_mcp_config_audit/js/cli.js:19 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files…_pycache__'].includes(e.name)) continue; // s158 — .github · .gitlab-ci.yml · .env · .well-known 은 본다 (옛 줄은 점으로 시작하는 것을 전부 건너뛰어 워크플로 검사기가 .github/workflows 를 못 봤다…Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
npx invocation of non-well-known packagesrc/readystack_mcp_config_audit/js/strings.json:3 · npx invocation of non-well-known package — may execute untrusted code…it one mcp.json for what an agent config gives away — inline API keys, unpinned npx launches, plaintext remote servers, shell wrappers, auto-approved tools, whole-machine fi…Fix: Pin versions and sources; vendor anything fetched at install time.
AST06
MEDIUM
npx invocation of non-well-known packagesrc/readystack_mcp_config_audit/js/rules.json:29 · npx invocation of non-well-known package — may execute untrusted code"title": "npx launches a package with no version",Fix: Pin versions and sources; vendor anything fetched at install time.
AST06
MEDIUM
npx invocation of non-well-known packagesrc/readystack_mcp_config_audit/js/package.json:4 · npx invocation of non-well-known package — may execute untrusted code…it one mcp.json for what an agent config gives away — inline API keys, unpinned npx launches, plaintext remote servers, shell wrappers, auto-approved tools, whole-machine fi…Fix: Pin versions and sources; vendor anything fetched at install time.
AST06
MEDIUM
npx invocation of non-well-known packageSKILL.md:6 · npx invocation of non-well-known package — may execute untrusted code…it one mcp.json for what an agent config gives away — inline API keys, unpinned npx launches, plaintext remote servers, shell wrappers, auto-approved tools, whole-machine fi…Fix: Pin versions and sources; vendor anything fetched at install time.
AST06
MEDIUM
npx invocation of non-well-known packagesrc/readystack_mcp_config_audit/js/rules.json:32 · npx invocation of non-well-known package — may execute untrusted code"std": "npm / npx resolution"Fix: Pin versions and sources; vendor anything fetched at install time.
AST06
MEDIUM
npx invocation of non-well-known packagepyproject.toml:8 · npx invocation of non-well-known package — may execute untrusted code…e mcp.json for what an agent config gives away \u2014 inline API keys, unpinned npx launches, plaintext remote servers, shell wrappers, auto-approved tools, whole-machine fi…Fix: Pin versions and sources; vendor anything fetched at install time.
AST06
MEDIUM
File type combined with upload actionsrc/readystack_mcp_config_audit/js/rules.json:16 · File type combined with upload action — agent may exfiltrate local data files"std": "VS Code mcp.json inputs"Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.
AST07
HIGH
Access to sensitive file pathssrc/readystack_mcp_config_audit/js/rules.json:102 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files"msg": "A root of /, ~, $HOME, %USERPROFILE% or a drive letter puts every SSH key, browser profile, .env file and unrelated repository on the machine inside the agent's reach for the whole session.",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05

Cost to the agent

Instructions loaded
≈103 tok
1 file · 20 in bundle

Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.

Known vulnerabilities

No advisories in OSV for readystack-mcp-config-audit@1.0.7.post1 as of 1 h ago. This is the package itself, not its dependencies.