@maestro-ai/mcp-server
npm
v6.1.0
Published by @maestro-ai — 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 |
|---|---|---|
| −6.7 | Possible combosquat of mcp ×4 MTC-SUP-006 | 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.
In the server's implementation (`dist/analyzers/security-analyzer.js:76`): 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 dist/analyzers/security-analyzer.js
In the server's implementation (`dist/content/skills/specialist-desenvolvimento-frontend/mcp_functions/process_frontend.py:614`): 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 dist/content/skills/specialist-desenvolvimento-frontend/mcp_functions/process_frontend.py
In the server's implementation (`dist/content/skills/specialist-desenvolvimento-frontend/mcp_functions/validate_frontend.py:691`): 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 dist/content/skills/specialist-desenvolvimento-frontend/mcp_functions/validate_frontend.py
In the server's implementation (`dist/content/skills/vulnerability-scanner/scripts/security_scan.py:63`): 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 dist/content/skills/vulnerability-scanner/scripts/security_scan.py
In the server's implementation (`dist/content/skills/lint-and-validate/scripts/lint_runner.py:80`): 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 dist/content/skills/lint-and-validate/scripts/lint_runner.py
In the server's implementation (`dist/content/skills/performance-profiling/scripts/lighthouse_audit.py:22`): 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 dist/content/skills/performance-profiling/scripts/lighthouse_audit.py
In the server's implementation (`dist/content/skills/testing-patterns/scripts/test_runner.py:91`): 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 dist/content/skills/testing-patterns/scripts/test_runner.py
In the server's implementation (`dist/content/skills/vulnerability-scanner/scripts/security_scan.py:64`): 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 dist/content/skills/vulnerability-scanner/scripts/security_scan.py
In the server's implementation (`dist/content/skills/specialist-documentacao-tecnica/mcp_functions/init_documentation_structure.py:431`): 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.get('https://api.example.com/v1/users'
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 dist/content/skills/specialist-documentacao-tecnica/mcp_functions/init_documentation_structure.py
"@maestro-ai/mcp-server" is "mcp" with a decorative suffix — a common combosquat pattern.
Fix: Confirm you meant "mcp". Install packages only from their documented, official name.
Location: package @maestro-ai/mcp-server
"@maestro-ai/mcp-server" is "@playwright/mcp" with a decorative suffix — a common combosquat pattern.
Fix: Confirm you meant "@playwright/mcp". Install packages only from their documented, official name.
Location: package @maestro-ai/mcp-server
"@maestro-ai/mcp-server" is "@stripe/mcp" with a decorative suffix — a common combosquat pattern.
Fix: Confirm you meant "@stripe/mcp". Install packages only from their documented, official name.
Location: package @maestro-ai/mcp-server
"@maestro-ai/mcp-server" is "@browsermcp/mcp" with a decorative suffix — a common combosquat pattern.
Fix: Confirm you meant "@browsermcp/mcp". Install packages only from their documented, official name.
Location: package @maestro-ai/mcp-server
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 |
|---|---|---|---|---|
v6.1.0 latest |
A 93/100 | 13 | 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 @maestro-ai/mcp-server --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.