Devtool (talocode) MCP Server
@talocode/devtool
npm
v0.2.0
Published by @talocode — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.
Unified CLI toolbox for developers — base64, JWT, timestamps, UUID, JSON, hash, URL, colors, case, and more
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 − 2 = 98. 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 |
|---|---|
| −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 0
Tools 66
Each tool and what it can reach — statically extracted from the published source.
base64_decodeno sensitive capabilitybase64_encodeno sensitive capabilitycase_camelno sensitive capabilitycase_kebabno sensitive capabilitycase_pascalno sensitive capabilitycase_snakeno sensitive capabilitycolor_hex_to_rgbno sensitive capabilitycron_describeno sensitive capabilitycron_nextno sensitive capabilitydiff_charno sensitive capability
Show 56 more tools ↓
diff_linesno sensitive capabilitygen_addressno sensitive capabilitygen_emailno sensitive capabilitygen_nameno sensitive capabilitygen_paragraphno sensitive capabilitygen_phoneno sensitive capabilitygen_usernameno sensitive capabilitygen_uuidno sensitive capabilityhash_md5no sensitive capabilityhash_sha1no sensitive capabilityhash_sha256no sensitive capabilityhash_sha512no sensitive capabilityhtml_decodeno sensitive capabilityhtml_encodeno sensitive capabilityhtml_stripno sensitive capabilityip_cidrno sensitive capabilityip_infono sensitive capabilityip_validateno sensitive capabilityjson_formatno sensitive capabilityjson_minifyno sensitive capabilityjson_validateno sensitive capabilityjwt_decodeno sensitive capabilitymarkdown_stripno sensitive capabilitymarkdown_tableno sensitive capabilitymarkdown_to_htmlno sensitive capabilitymath_bytesno sensitive capabilitymath_c_to_fno sensitive capabilitymath_f_to_cno sensitive capabilitymath_kb_to_mbno sensitive capabilitymath_mb_to_kbno sensitive capabilitymath_px_to_remno sensitive capabilitymath_rem_to_pxno sensitive capabilitynumber_from_hexno sensitive capabilitynumber_to_binno sensitive capabilitynumber_to_hexno sensitive capabilitynumber_to_octno sensitive capabilityregex_matchno sensitive capabilityregex_testno sensitive capabilitystr_lenno sensitive capabilitystr_lowerno sensitive capabilitystr_reverseno sensitive capabilitystr_trimno sensitive capabilitystr_upperno sensitive capabilityts_from_dateno sensitive capabilityts_nowno sensitive capabilityts_now_msno sensitive capabilityts_to_dateno sensitive capabilitytz_convertno sensitive capabilitytz_listno sensitive capabilitytz_nowno sensitive capabilityurl_decodeno sensitive capabilityurl_encodeno sensitive capabilityurl_parseno sensitive capabilityuuid_v4no sensitive capabilityuuid_v7no sensitive capabilityuuid_validateno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (66 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 |
|---|---|---|---|---|
v0.2.0 latest |
A 98/100 | 0 | 1.13.0 | 2026-09-09 |
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 @talocode/devtool --onlineOther implementations of Devtool 1
Independent packages implementing the same tool, scanned with the same engine. Compare all 2 side by side →
More in Developer Tools
Hotel booking MCP server — 300K+ properties, real confirmation numbers, loyalty programs. Builders monetize every booking via Stripe Connect. The first MCP server that completes real hotel reservations inside AI conversations.
Manage AdGuard Home through AI assistants
Read-only Azure DevOps for MCP clients using only your existing browser session — no PAT, no Azure CLI. Browse work items, pull requests, comments, attachments and Artifacts feeds across every project, repo and feed you can access.
MCP server for Adobe Experience Manager Assets integration development
Servidor MCP para el tiempo oficial de España (API pública OpenData de AEMET). Predicción, observación y avisos como herramientas MCP tipadas.
A standalone MCP stdio bridge for Affinity by Canva's local MCP SSE server.