@atomik-dev/mcp
npm
v1.1.0
Published by @atomik-dev — 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.
In the server's implementation (`index.js:8`): 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: port { execSync } from 'child_process'; import { GUIA_RESUMO, SECOES, GUIA_COMPLETO } from './guia-design.js'; const WS
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
Each tool and what it can reach — statically extracted from the published source.
aplicar_animacaono sensitive capabilityaplicar_css_no_elementono sensitive capabilityaplicar_cursorno sensitive capabilityaplicar_cursor_glowno sensitive capabilityaplicar_estilos_em_loteno sensitive capabilityaplicar_transicao_secaono sensitive capabilityatualizar_cores_em_massano sensitive capabilityatualizar_peso_em_massano sensitive capabilityatualizar_tamanho_em_massano sensitive capabilitybuscar_elementosno sensitive capabilitycapturar_telano sensitive capabilitychecar_designno sensitive capabilitycriar_cor_globalno sensitive capabilitycriar_elementono sensitive capabilitycriar_elementos_em_loteno sensitive capabilitycriar_popupno sensitive capabilitydefinir_bordano sensitive capabilitydefinir_border_radiusno sensitive capabilitydefinir_corno sensitive capabilitydefinir_efeitosno sensitive capabilitydefinir_espacamentono sensitive capabilitydefinir_fundono sensitive capabilitydefinir_largurano sensitive capabilitydefinir_layout_flexno sensitive capabilitydefinir_posicaono sensitive capabilitydefinir_sombrano sensitive capabilitydefinir_tamanhono sensitive capabilitydefinir_tipografiano sensitive capabilitydesfazerno sensitive capabilityduplicar_elementono sensitive capabilityeditar_cor_globalno sensitive capabilityeditar_elementono sensitive capabilityenvolver_htmlno sensitive capabilityfigma_aplicar_coresno sensitive capabilityfigma_aplicar_tipografiano sensitive capabilityfigma_importar_gridno sensitive capabilityguia_designno sensitive capabilityinserir_componenteno sensitive capabilityinserir_css_snippetno sensitive capabilityinserir_cursor_growno sensitive capabilityinserir_cursor_labelno sensitive capabilityinserir_js_snippetno sensitive capabilityinserir_luz_fundono sensitive capabilityinserir_multiplos_componentesno sensitive capabilityinserir_patternno sensitive capabilityinserir_tag_cssno sensitive capabilityinserir_videono sensitive capabilityler_elementono sensitive capabilityler_estrutura_paginano sensitive capabilitylimpar_selecaono sensitive capabilitylistar_componentesno sensitive capabilitylistar_kit_coresno sensitive capabilitylistar_kit_tipografiano sensitive capabilitymedir_elementono sensitive capabilitymover_elementono sensitive capabilitymudar_breakpoint_editorno sensitive capabilityobter_selecao_atualno sensitive capabilityrefazerno sensitive capabilityremover_elementono sensitive capabilitysalvar_paginano sensitive capabilityselecionar_elementono sensitive capabilitysubstituir_link_em_massano sensitive capabilityvalidar_cssno sensitive capabilityvarrer_paginano sensitive capabilityScan 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.0 latest |
A 93/100 | 1 | 1.9.0 | 2026-07-24 |
v1.0.2 |
A 93/100 | 1 | 1.8.0 | 2026-07-23 |
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 @atomik-dev/mcp --online
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.