Devkit (npm) MCP Server
devkit-mcp
npm
v1.1.0
Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.
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 − 5 = 95. 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 |
|---|---|
| −3 | capability blast radius (moderate) — client exposure if the model is manipulated |
| −2 | publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read |
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
medium Untrusted input can drive an external actionMTC-FLOW-005
Untrusted-input tools ([http_fetch]) co-exist with external-action tools ([http_fetch]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.
Evidence: untrusted [http_fetch] → sinks [http_fetch]
Fix: Require confirmation for state-changing/egress actions triggered after processing untrusted content.
Location: flow http_fetch → http_fetch
Tools 37
Each tool and what it can reach — statically extracted from the published source.
http_fetchingests untrusted inputnetwork egresscolor_hex_to_hslno sensitive capabilitycolor_hex_to_rgbno sensitive capabilitycolor_hsl_to_hexno sensitive capabilitycolor_mixno sensitive capabilitycolor_rgb_to_hexno sensitive capabilitydecode_htmlno sensitive capabilitydecode_unicodeno sensitive capabilitydecode_urlno sensitive capabilitydiff_textno sensitive capability
Show 27 more tools ↓
encode_htmlno sensitive capabilityencode_unicodeno sensitive capabilityencode_urlno sensitive capabilityformat_json_to_tomlno sensitive capabilityformat_json_to_yamlno sensitive capabilityformat_minify_jsonno sensitive capabilityformat_pretty_jsonno sensitive capabilityformat_toml_to_jsonno sensitive capabilityformat_yaml_to_jsonno sensitive capabilityhash_base64no sensitive capabilityhash_file_checksumno sensitive capabilityhash_hmacno sensitive capabilityhash_md5no sensitive capabilityhash_sha1no sensitive capabilityhash_sha256no sensitive capabilityhash_sha512no sensitive capabilityjson_schemano sensitive capabilitypwd_genno sensitive capabilityregex_extractno sensitive capabilityregex_replaceno sensitive capabilityregex_testno sensitive capabilitytime_date_to_timestampno sensitive capabilitytime_durationno sensitive capabilitytime_nowno sensitive capabilitytime_timestamp_to_dateno sensitive capabilityuuid_bulkno sensitive capabilityuuid_genno sensitive capability
Toxic flows 1
Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).
What this scan could not see
- Tools were statically extracted from the published source (37 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.1.0 latest |
A 95/100 | 1 | 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 devkit-mcp --onlineOther implementations of Devkit 2
Independent packages implementing the same tool, scanned with the same engine. Compare all 3 side by side →
Security scan results for the Devkit (mapbox) MCP server.
Security scan results for the Devkit (dpm-tools) MCP server.
More 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.