Utilix
NPM · @UTILIX-TECH/MCP · 2 COMPONENTS
300+ offline developer utilities, plus 22 AI tools with a free API key. JSON, JWT, regex, cron, SQL.
Available components
Last scanned (18 hours ago)
Scores higher than 0% of npm servers
Category Developer Tools
Recent critical change
CVE-2024-21534 affects this package (12 Nov 2026). See the changelog before you install this server.
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security73
- No malware found by supply-chain analysis.Pass
- CVE check failed: an unpatched critical CVE affects this package; the score is capped at 0. See how to fix → View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 47 of 141 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 29537 tokens (~90/item across 327 items; 327 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 87% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 7 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "trim_to_tokens" implies "truncate" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 327 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 18 Nov 26 0
- Package version: 0.110.0 → 0.111.0 functional
- 17 Nov 26 0
- Package version: 0.109.0 → 0.110.0 functional
- 16 Nov 26 0
- Tool safety: pass → unverified ▼ security
- Stability: 0.13 → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.108.0 → 0.109.0 functional
- 15 Nov 26 0
- Package version: 0.107.0 → 0.108.0 functional
- 14 Nov 26 0
- Package version: 0.106.0 → 0.107.0 functional
- 13 Nov 26 0
- Stability: 0.03 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.105.1 → 0.106.0 functional
- 12 Nov 26 −43
- CVE-2024-21534 affects this package: high ▼ critical
- CVE-2025-1302 affects this package: high ▼ critical
- Known CVEs: unverified → fail ▼ critical
- Score status: scored → failed ▼ critical
- Tool safety: pass → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Dependency health: unverified → 0.84 ▲ functional
- Score status: failed → scored ▲ functional
- First check of Schema quality: unverified functional
- Package version: 0.103.0 → 0.105.1 functional
- Package version: 0.103.0 → 0.105.0 functional
- Package version: 0.103.0 → 0.104.2 functional
- Package version: 0.103.0 → 0.104.1 functional
- 11 Nov 26 43
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Analysed npm/@utilix-tech/mcp@0.111.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 3 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-hw8r-x6gr-5gjp | CVE-2025-1302 | critical | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H | yes |
| GHSA-pppg-cpfq-h7wr | CVE-2024-21534 | critical | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H | yes |
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 141 packages
| Packages resolved | 141 |
|---|---|
| Deprecated | 1 |
| Stale | 46 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
validate_aria ~101
Parse an HTML snippet and check every role and aria-* attribute against a curated table of WAI-ARIA 1.2 roles: unknown role names, an aria-* attribute not permitted on the given role, and a widget role missing its required aria-* state (e.g. role="checkbox" without aria-checked). Covers a curated subset of common roles, not the full ARIA spec.
| Name | Type | Req | Description |
|---|---|---|---|
| html | string | yes | The HTML snippet to check |
No output schema declared.
No examples provided.
validate_barcode ~72
Validate an EAN-13, EAN-8, or UPC-A barcode number via its weighted mod-10 check digit algorithm. The format is inferred from the digit length (8, 12, or 13).
| Name | Type | Req | Description |
|---|---|---|---|
| barcode | string | yes | The barcode digits, with optional spaces or hyphens |
No output schema declared.
No examples provided.
validate_card_number ~78
Validate a credit card number via the Luhn checksum and detect its network (Visa, Mastercard, American Express, Discover, Diners Club, JCB, Maestro, UnionPay) from its prefix and length. No card data is stored or transmitted.
| Name | Type | Req | Description |
|---|---|---|---|
| number | string | yes | The card number, digits with optional spaces or hyphens |
No output schema declared.
No examples provided.
validate_editorconfig ~95
Validate an .editorconfig file: parse it into its root flag and glob sections, and flag structural mistakes against the EditorConfig spec — unknown properties, invalid values for known properties (indent_style, end_of_line, charset, indent_size, tab_width, max_line_length), a root declaration outside the file's preamble, and duplicate properties within the same section.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | The .editorconfig file contents |
No output schema declared.
No examples provided.
validate_fence_language_tags ~67
Scan a Markdown document's fenced code blocks (``` or ~~~) and flag ones with a missing, unknown, or inconsistently-cased language tag, checked against a curated list of common syntax-highlighter language identifiers.
| Name | Type | Req | Description |
|---|---|---|---|
| markdown | string | yes | The Markdown document to scan |
No output schema declared.
No examples provided.
validate_geojson ~123
Validate a GeoJSON document's structure against RFC 7946: the correct geometry type and coordinates shape for each of the seven geometry types, linear ring closure for Polygon/MultiPolygon, a Feature's required properties/geometry members, and a FeatureCollection's required features array. Also returns non-failing warnings when a Polygon ring winds the "wrong" way under RFC 7946's right-hand rule recommendation. Pure structural validation; no map is rendered and no tile server is contacted.
| Name | Type | Req | Description |
|---|---|---|---|
| geojson | string | yes | The GeoJSON document, as a JSON string |
No output schema declared.
No examples provided.
validate_iban ~66
Validate an IBAN via the mod-97 checksum defined by ISO 13616 and format it into the standard human-readable grouped form. Cross-checks the total length against the country's registered fixed length where known.
| Name | Type | Req | Description |
|---|---|---|---|
| iban | string | yes | The IBAN, with or without spaces |
No output schema declared.
No examples provided.
validate_isbn ~64
Validate an ISBN-10 or ISBN-13 number via its checksum (inferred from the character count) and convert it to the other format where possible.
| Name | Type | Req | Description |
|---|---|---|---|
| isbn | string | yes | The ISBN-10 or ISBN-13, with or without hyphens/spaces |
No output schema declared.
No examples provided.
validate_isin ~100
Validate a 12-character ISIN (ISO 6166) via its Luhn-style mod-10 check digit. The 2-letter country code and 9-character alphanumeric security identifier are transliterated (A=10 ... Z=35) into a numeric string before the Luhn algorithm is applied, the same way credit card numbers are checksummed.
| Name | Type | Req | Description |
|---|---|---|---|
| isin | string | yes | The 12-character ISIN, with or without spaces |
No output schema declared.
No examples provided.
validate_json ~50
Validate a JSON string against a JSON Schema (Draft-7). Returns pass/fail with error details.
| Name | Type | Req | Description |
|---|---|---|---|
| data | string | yes | JSON data to validate |
| schema | string | yes | JSON Schema string |
No output schema declared.
No examples provided.
validate_json_schema ~33
Validate JSON data against a JSON Schema (Draft-07).
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | – |
| schema | object | yes | – |
No output schema declared.
No examples provided.
validate_manifest ~77
Validate a web app manifest.json against the W3C Web App Manifest spec's installability requirements: name/short_name, start_url, a recognized display mode, and an icons array covering a 512x512 icon and a maskable icon, plus recommended theme_color/background_color fields.
| Name | Type | Req | Description |
|---|---|---|---|
| manifest | string | yes | The manifest.json contents |
No output schema declared.
No examples provided.
validate_markdown_blockquote_nesting ~89
Walk a Markdown document line by line and flag blockquote nesting that jumps by more than one level at once, e.g. going straight from `>` to `>>>` without a `>>` line in between, or a quote block whose first line already starts at a nesting level above 1.
| Name | Type | Req | Description |
|---|---|---|---|
| markdown | string | yes | The Markdown document to scan for blockquote lines |
No output schema declared.
No examples provided.
validate_markdown_heading_hierarchy ~95
Scan a Markdown document's ATX headings and flag heading-structure issues: a level that skips one or more levels going deeper, more than one H1, an empty heading, a duplicate heading at the same level, or a document that doesn't start at H1. Setext-style headings are not recognized, and headings inside fenced code blocks are ignored.
| Name | Type | Req | Description |
|---|---|---|---|
| markdown | string | yes | The Markdown document to scan |
No output schema declared.
No examples provided.
validate_mermaid_syntax ~112
Heuristic syntax validation for a Mermaid diagram definition: recognizes flowchart/graph, sequenceDiagram, classDiagram, stateDiagram(-v2), erDiagram, and pie by their header keyword, then runs diagram-specific structural checks (unterminated subgraph, unbalanced brackets, malformed edges for flowcharts; a participant referenced before its explicit declaration for sequence diagrams). A line-based heuristic, not a full Mermaid grammar; never renders the diagram.
| Name | Type | Req | Description |
|---|---|---|---|
| diagram | string | yes | The full Mermaid diagram definition text |
No output schema declared.
No examples provided.
validate_package_exports ~108
Validate a package.json "exports" field: flag common dual-package (ESM/CJS) misconfigurations — a "types" condition not listed first, a missing "default" fallback, a "require"/"import" pointing at the wrong file extension, mixing subpath and condition keys in the same object, and a subpath pattern with no matching "*" in its target.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | The full package.json file contents (only the "exports" field is read) |
No output schema declared.
No examples provided.
validate_robots_txt ~68
Validate a robots.txt file: parse it into User-agent groups and flag structural mistakes — directives before any User-agent, unknown directives, non-absolute Sitemap URLs, malformed Crawl-delay values, missing leading slashes, and duplicate rules.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | The robots.txt file contents |
No output schema declared.
No examples provided.
validate_routing_number ~79
Validate a 9-digit US bank routing number (ABA/RTN) via the weighted mod-10 checksum from the ABA's routing number specification. Also identifies the routing number's type and Federal Reserve district from its first two digits.
| Name | Type | Req | Description |
|---|---|---|---|
| routingNumber | string | yes | The 9-digit routing number, with optional spaces or hyphens |
No output schema declared.
No examples provided.
validate_sitemap ~80
Validate a sitemap.xml (urlset) or sitemap index (sitemapindex) against the sitemaps.org protocol: required <loc>, absolute URLs, valid <changefreq>/<priority>/<lastmod> values, the 50,000-URL limit, and duplicate entries.
| Name | Type | Req | Description |
|---|---|---|---|
| xml | string | yes | The sitemap.xml or sitemap index XML contents |
No output schema declared.
No examples provided.
validate_tsconfig ~87
Validate a tsconfig.json file: parse it as JSONC (// and block comments plus trailing commas are stripped, matching how tsc itself reads the file) and flag structural mistakes — unknown top-level keys, unknown compilerOptions keys, wrong types, and malformed files/include/exclude/references/paths.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | The tsconfig.json file contents (JSONC allowed) |
No output schema declared.
No examples provided.
validate_vin ~90
Validate a 17-character VIN via the ISO 3779 / NHTSA weighted mod-11 check digit at position 9, and split it into its World Manufacturer Identifier (WMI), Vehicle Descriptor Section (VDS), and Vehicle Identifier Section (VIS). Does not decode make, model, or model year.
| Name | Type | Req | Description |
|---|---|---|---|
| vin | string | yes | The 17-character VIN, with or without spaces |
No output schema declared.
No examples provided.
validate_yaml ~29
Validate YAML syntax and return stats or error details.
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | YAML string to validate |
No output schema declared.
No examples provided.
vector_similarity ~52
Compute cosine similarity, dot product, Euclidean distance, and Manhattan distance between two equal-length numeric vectors (e.g. embeddings from an external model).
| Name | Type | Req | Description |
|---|---|---|---|
| a | array | yes | – |
| b | array | yes | – |
No output schema declared.
No examples provided.
verify_webhook_signature ~168
Recompute an HMAC over a raw webhook payload and compare it to a provided signature, the check every webhook receiver (Stripe, GitHub, Shopify, etc.) has to do before trusting a request. Accepts a signature with or without the common "sha256=" prefix style, and matches against either hex or base64 encoding since providers differ on which they send.
| Name | Type | Req | Description |
|---|---|---|---|
| algorithm | string | – | The HMAC hash algorithm the signature was computed with (default sha256) |
| payload | string | yes | The raw webhook request body, exactly as received (do not re-serialize JSON) |
| secret | string | yes | The shared webhook signing secret |
| signature | string | yes | The signature to verify, with or without a "sha256=" style prefix, hex or base64 encoded |
No output schema declared.
No examples provided.
word_count ~35
Count words, characters, sentences, and estimate reading time for a block of text.
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | Text to analyze |
No output schema declared.
No examples provided.
xml_to_json ~25
Convert an XML document to JSON.
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | XML string |
No output schema declared.
No examples provided.
yaml_to_json ~25
Convert a YAML string to JSON.
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | YAML string |
No output schema declared.
No examples provided.
How do I install the Utilix MCP server?
Utilix runs locally as an npm package, launched with npx -y @utilix-tech/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @utilix-tech/mcp
claude mcp add utilix-tech-utilix-mcp -- npx -y @utilix-tech/mcp
What is the Utilix MCP server?
Utilix is an MCP server listed in the public MCP registry as io.github.utilix-tech/utilix-mcp. 300+ offline developer utilities, plus 22 AI tools with a free API key. JSON, JWT, regex, cron, SQL. This page covers its npm package (@utilix-tech/mcp).
What tools does the Utilix MCP server expose?
Utilix exposes 327 tools: format_json, minify_json, diff_json, json_to_csv, csv_to_json, and 322 more. Their descriptions and schemas cost roughly 29,537 tokens of context every time the server is loaded.
Is the Utilix MCP server still maintained?
Utilix is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Utilix MCP server under?
Utilix declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.