test_research4
npm
v0.5.20
Published by trevsmart — 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 |
|---|---|---|
| −37.7 | Obfuscated / encoded payload in server code ×10 MTC-SRC-004 | injection |
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.
In the server's implementation (`index.js:1`): 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: \x2e\x2f\x73\x72\x63\x2f\x6c\x69\x62\x2f\x6c\x6f\x67\x67\x65\x72\x2e\x6a\x73
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 index.js
In the server's implementation (`src/client.js:1`): 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: \x2e\x2f\x63\x6f\x6e\x66\x69\x67\x2e\x6a\x73
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/client.js
In the server's implementation (`src/config.js:1`): 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: \x61\x62\x63\x64\x65\x66\x67\x68\x69\x6a\x6b\x6c\x6d\x6e\x6f\x70\x71\x72\x73\x74\x75\x76\x77\x78\x79\x7a\x41\x42\x43\x44\x45\x46\x47\x48\x49\x4a\x4b\x4c\x4d\x4e
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/config.js
In the server's implementation (`src/lib/OrgWatcher.js:1`): 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: \x6e\x6f\x64\x65\x3a\x65\x76\x65\x6e\x74\x73
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/lib/OrgWatcher.js
In the server's implementation (`src/lib/destructiveOperationElicitation.js:1`): 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: \x2e\x2e\x2f\x73\x74\x61\x74\x65\x2e\x6a\x73
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/lib/destructiveOperationElicitation.js
In the server's implementation (`src/lib/handlerRegistry.js:1`): 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: \x40\x6d\x6f\x64\x65\x6c\x63\x6f\x6e\x74\x65\x78\x74\x70\x72\x6f\x74\x6f\x63\x6f\x6c\x2f\x73\x64\x6b\x2f\x74\x79\x70\x65\x73\x2e\x6a\x73
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/lib/handlerRegistry.js
In the server's implementation (`src/lib/icons.js:1`): 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: \x6e\x6f\x64\x65\x3a\x70\x61\x74\x68
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/lib/icons.js
In the server's implementation (`src/lib/initialization.js:1`): 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: \x6e\x6f\x64\x65\x3a\x70\x61\x74\x68
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/lib/initialization.js
In the server's implementation (`src/lib/logger.js:1`): 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: \x6e\x6f\x64\x65\x3a\x70\x61\x74\x68
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/lib/logger.js
In the server's implementation (`src/lib/mcpApps/manifest.js:1`): 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: \x61\x62\x63\x64\x65\x66\x67\x68\x69\x6a\x6b\x6c\x6d\x6e\x6f\x70\x71\x72\x73\x74\x75\x76\x77\x78\x79\x7a\x41\x42\x43\x44\x45\x46\x47\x48\x49\x4a\x4b\x4c\x4d\x4e
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/lib/mcpApps/manifest.js
In the server's implementation (`src/lib/auditTrailDownloader.js:1`): 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 src/lib/auditTrailDownloader.js
In the server's implementation (`src/lib/salesforceServices.js:1`): 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/lib/salesforceServices.js
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.5.20 latest |
D 62/100 | 12 | 1.5.0 | 2026-07-22 |
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.
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 test_research4 --online
Security scan results for the 199bio Mcp Limitless 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.
Security scan results for the 3d MCP server.