Prysm MCP Server
@pinkpixel/prysm-mcp
npm
v1.1.2
Published by @pinkpixel — no publish provenance and no vendor-owned scope, so the publisher could not be verified. The repository link below is self-declared.
Every server starts at 100. These are the exact deductions the deterministic engine applied — each one reproducible, none of it an opinion or an LLM's guess:
| Points | What was found | Category |
|---|---|---|
| −23.1 | Dynamic evaluation of a non-literal value ×2 MTC-SRC-010 | injection |
| −6.3 | Unsafe deserialization MTC-SRC-007 | permissions |
| −2.1 | Package has no source repository MTC-SUP-011 | supply-chain |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind the deduction.
Findings 8
high Dynamic evaluation of a non-literal value (prysm-llm/scraper/utils/helpers.js)MTC-SRC-010
In the server's implementation (`prysm-llm/scraper/utils/helpers.js:41`): Evaluating a runtime value as code (rather than a fixed literal) executes whatever reaches it — a direct RCE primitive, and almost never necessary in legitimate code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: eval(
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server prysm-llm/scraper/utils/helpers.js
high Dynamic evaluation of a non-literal value (prysm-llm/scraper/utils/paginationStrategies.js)MTC-SRC-010
In the server's implementation (`prysm-llm/scraper/utils/paginationStrategies.js:490`): Evaluating a runtime value as code (rather than a fixed literal) executes whatever reaches it — a direct RCE primitive, and almost never necessary in legitimate code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: eval(
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server prysm-llm/scraper/utils/paginationStrategies.js
high Dynamic code execution in server code (prysm-llm/scraper/utils/helpers.js)MTC-SRC-001
In the server's implementation (`prysm-llm/scraper/utils/helpers.js:41`): Evaluating strings as code is the most direct RCE primitive; if any tool input reaches it, the server executes attacker-chosen code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: eval(
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server prysm-llm/scraper/utils/helpers.js
high Dynamic code execution in server code (prysm-llm/scraper/utils/paginationStrategies.js)MTC-SRC-001
In the server's implementation (`prysm-llm/scraper/utils/paginationStrategies.js:490`): Evaluating strings as code is the most direct RCE primitive; if any tool input reaches it, the server executes attacker-chosen code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: eval(
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server prysm-llm/scraper/utils/paginationStrategies.js
high Shell/command execution in server code (test-mcp.js)MTC-SRC-002
In the server's implementation (`test-mcp.js:4`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: child_process
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server test-mcp.js
medium Dynamic module load from a non-literal (prysm-llm/scraper/bin/cli.js)MTC-SRC-005
In the server's implementation (`prysm-llm/scraper/bin/cli.js:57`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: require(mainScraperPath)
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server prysm-llm/scraper/bin/cli.js
medium Unsafe deserialization (prysm-llm/scraper/api/server.js)MTC-SRC-007
In the server's implementation (`prysm-llm/scraper/api/server.js:40`): Deserializing untrusted data with these APIs can execute arbitrary code (a well-known RCE gadget class). This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: yaml.load(
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server prysm-llm/scraper/api/server.js
low Package has no source repositoryMTC-SUP-011
"@pinkpixel/prysm-mcp" declares no repository URL, so its published artifact cannot be compared against reviewable source.
Fix: Prefer packages that link to public, reviewable source.
Location: package @pinkpixel/prysm-mcp
What this scan could not see
- No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Versions
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v1.1.2 latest |
D 69/100 | 8 | 1.5.0 | 2026-07-22 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan @pinkpixel/prysm-mcp --onlineMore in Other
Security scan results for the 0xgasless MCP server.
Security scan results for the 24htrack MCP server.
Security scan results for the 3d Asset Processing MCP server.
Security scan results for the A2amarket MCP server.
Security scan results for the Ableton Copilot MCP server.
Security scan results for the Academy MCP server.