Devutils (hlteoh37) MCP Server

mcp-devutils npm v2.9.16

Published by hlteoh37 — 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.

MCP server with 45 developer utilities (16 free + 29 pro). Free: UUID, hash, HMAC, base64, timestamps, JWT decode, random strings, URL encode/decode, JSON format, YAML/JSON convert, regex test, cron explain, color convert, HTTP status, slugify, HTML escap

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/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
Moderate
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.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 96/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 − 4 = 96. 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
−3 capability blast radius (moderate) — 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 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 46

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

  • jwt_createreads sensitive data
  • sql_formatreads sensitive data
  • aes_decryptno sensitive capability
  • aes_encryptno sensitive capability
  • base64no sensitive capability
  • byte_countno sensitive capability
  • case_convertno sensitive capability
  • char_infono sensitive capability
  • chmod_calcno sensitive capability
  • cidrno sensitive capability
Show 36 more tools ↓
  • color_convertno sensitive capability
  • cron_explainno sensitive capability
  • csv_jsonno sensitive capability
  • data_sizeno sensitive capability
  • devutils_statusno sensitive capability
  • diffno sensitive capability
  • env_parseno sensitive capability
  • epoch_convertno sensitive capability
  • escape_htmlno sensitive capability
  • hashno sensitive capability
  • hex_encodeno sensitive capability
  • hmacno sensitive capability
  • http_statusno sensitive capability
  • ip_infono sensitive capability
  • json_diffno sensitive capability
  • json_formatno sensitive capability
  • json_queryno sensitive capability
  • jwt_decodeno sensitive capability
  • lorem_ipsumno sensitive capability
  • markdown_tocno sensitive capability
  • nanoidno sensitive capability
  • number_baseno sensitive capability
  • password_strengthno sensitive capability
  • random_stringno sensitive capability
  • regex_replaceno sensitive capability
  • regex_testno sensitive capability
  • rsa_keygenno sensitive capability
  • scrypt_hashno sensitive capability
  • semver_compareno sensitive capability
  • slugno sensitive capability
  • string_escapeno sensitive capability
  • timestampno sensitive capability
  • url_encodeno sensitive capability
  • uuidno sensitive capability
  • word_countno sensitive capability
  • yaml_jsonno sensitive capability

What this scan could not see

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.

VersionScoreFindingsEngineScanned
v2.9.16 latest A 96/100 0 1.13.0 2026-09-07

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 · 96/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/mcp-devutils/badge.svg)](https://mcptrustchecker.com/registry/mcp-devutils)
HTML
<a href="https://mcptrustchecker.com/registry/mcp-devutils"><img src="https://mcptrustchecker.com/registry/mcp-devutils/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/mcp-devutils/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 mcp-devutils --online

Use the free API → How scoring works

Other implementations of Devutils 2

Independent packages implementing the same tool, scanned with the same engine. Compare all 3 side by side →

More in Developer Tools