Mini Test MCP Server
mini-test-mcp
npm
v1.0.9
Published by mingzhanliao — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 7 = 93. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
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 a deduction.
Findings 2
high Shell/command execution in server code (cli.js)MTC-SRC-002
In the server's implementation (`cli.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: import { spawn } from 'child_process'; import path from 'path'; import { fileURLToPath } from 'url'; import { platform
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 cli.js
high Shell/command execution in server code (src/services/devtool-service.js)MTC-SRC-002
In the server's implementation (`src/services/devtool-service.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: import { spawn } from 'child_process'; import { existsSync } from 'fs'; import { logger } from '../utils/logger.js';
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/services/devtool-service.js
Tools 27
Each tool and what it can reach — statically extracted from the published source.
config_getno sensitive capabilitydevtool_startno sensitive capabilitydevtool_statusno sensitive capabilitydevtool_stopno sensitive capabilitydevtool_validate_configno sensitive capabilityminium_auto_connectno sensitive capabilityminium_closeno sensitive capabilityminium_connectno sensitive capabilityminium_element_attributeno sensitive capabilityminium_element_inputno sensitive capability
Show 17 more tools ↓
minium_element_offsetno sensitive capabilityminium_element_propertyno sensitive capabilityminium_element_sizeno sensitive capabilityminium_element_tapno sensitive capabilityminium_element_textno sensitive capabilityminium_get_console_logsno sensitive capabilityminium_get_elementno sensitive capabilityminium_get_elementsno sensitive capabilityminium_navigate_tono sensitive capabilityminium_page_call_methodno sensitive capabilityminium_page_datano sensitive capabilityminium_page_set_datano sensitive capabilityminium_page_sizeno sensitive capabilityminium_screenshotno sensitive capabilityminium_switch_tabno sensitive capabilityminium_waitno sensitive capabilityminium_wait_for_elementno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (27 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
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.0.9 latest |
A 93/100 | 2 | 1.10.0 | 2026-07-25 |
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 mini-test-mcp --onlineMore in Developer Tools
Security scan results for the 1stay MCP server.
Security scan results for the Adguard Home MCP server.
Security scan results for the Ado Browser MCP server.
Security scan results for the Adobe Experience Dev MCP server.
Security scan results for the Aemet MCP server.
Security scan results for the Affinity Mcp Bridge MCP server.