Atomik Dev MCP Server

@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.

Trust grade
A
93/100
Last scanned get badge →
Trust
A · 93/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
A Why this grade threat 100 − adoption risk = 93/100

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:

PointsAdoption-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 1

high Shell/command execution in server code (index.js)MTC-SRC-002

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

Tools 64

Each tool and what it can reach — statically extracted from the published source.

  • aplicar_animacaono sensitive capability
  • aplicar_css_no_elementono sensitive capability
  • aplicar_cursorno sensitive capability
  • aplicar_cursor_glowno sensitive capability
  • aplicar_estilos_em_loteno sensitive capability
  • aplicar_transicao_secaono sensitive capability
  • atualizar_cores_em_massano sensitive capability
  • atualizar_peso_em_massano sensitive capability
  • atualizar_tamanho_em_massano sensitive capability
  • buscar_elementosno sensitive capability
Show 54 more tools ↓
  • capturar_telano sensitive capability
  • checar_designno sensitive capability
  • criar_cor_globalno sensitive capability
  • criar_elementono sensitive capability
  • criar_elementos_em_loteno sensitive capability
  • criar_popupno sensitive capability
  • definir_bordano sensitive capability
  • definir_border_radiusno sensitive capability
  • definir_corno sensitive capability
  • definir_efeitosno sensitive capability
  • definir_espacamentono sensitive capability
  • definir_fundono sensitive capability
  • definir_largurano sensitive capability
  • definir_layout_flexno sensitive capability
  • definir_posicaono sensitive capability
  • definir_sombrano sensitive capability
  • definir_tamanhono sensitive capability
  • definir_tipografiano sensitive capability
  • desfazerno sensitive capability
  • duplicar_elementono sensitive capability
  • editar_cor_globalno sensitive capability
  • editar_elementono sensitive capability
  • envolver_htmlno sensitive capability
  • figma_aplicar_coresno sensitive capability
  • figma_aplicar_tipografiano sensitive capability
  • figma_importar_gridno sensitive capability
  • guia_designno sensitive capability
  • inserir_componenteno sensitive capability
  • inserir_css_snippetno sensitive capability
  • inserir_cursor_growno sensitive capability
  • inserir_cursor_labelno sensitive capability
  • inserir_js_snippetno sensitive capability
  • inserir_luz_fundono sensitive capability
  • inserir_multiplos_componentesno sensitive capability
  • inserir_patternno sensitive capability
  • inserir_tag_cssno sensitive capability
  • inserir_videono sensitive capability
  • ler_elementono sensitive capability
  • ler_estrutura_paginano sensitive capability
  • limpar_selecaono sensitive capability
  • listar_componentesno sensitive capability
  • listar_kit_coresno sensitive capability
  • listar_kit_tipografiano sensitive capability
  • medir_elementono sensitive capability
  • mover_elementono sensitive capability
  • mudar_breakpoint_editorno sensitive capability
  • obter_selecao_atualno sensitive capability
  • refazerno sensitive capability
  • remover_elementono sensitive capability
  • salvar_paginano sensitive capability
  • selecionar_elementono sensitive capability
  • substituir_link_em_massano sensitive capability
  • validar_cssno sensitive capability
  • varrer_paginano sensitive capability

What this scan could not see

Versions 2

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.

VersionScoreFindingsEngineScanned
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

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.

MCP Trust Score: A · 93/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/atomik-dev-mcp/badge.svg)](https://mcptrustchecker.com/registry/atomik-dev-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/atomik-dev-mcp"><img src="https://mcptrustchecker.com/registry/atomik-dev-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/atomik-dev-mcp/badge.json via https://img.shields.io/endpoint?url=…

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 @atomik-dev/mcp --online

Use the free API → How scoring works

More in Developer Tools