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 (17 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 →
detect_redos ~103
Statically analyze a regex pattern for catastrophic-backtracking (ReDoS) risk. Flags nested unbounded quantifiers ((a+)+), overlapping alternation under a repeat ((a|ab)*), and adjacent overlapping quantifiers (\d+\d+). Heuristic linter, not a formal proof. Pass the pattern body only, no delimiters or flags.
| Name | Type | Req | Description |
|---|---|---|---|
| pattern | string | yes | The regex pattern body to analyze, e.g. (a+)+ |
No output schema declared.
No examples provided.
detect_secrets ~50
Scan text for leaked API keys, tokens, and credentials (OpenAI, Anthropic, AWS, GitHub, Stripe, etc.).
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | Text or code to scan for secrets |
No output schema declared.
No examples provided.
detect_weasel_words ~104
Scan text for weasel words: vague hedging phrases that imply evidence or consensus without naming a checkable source ("studies show", "many experts believe", "it is widely known"). Dictionary-based heuristic over a curated phrase list, distinct from detect_filler_words' "hedge" category, which covers personal uncertainty ("maybe", "I think") rather than unattributed third-party authority.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | The text to scan for weasel words |
No output schema declared.
No examples provided.
detect_wordy_phrases ~101
Scan text against a curated table of wordy/redundant phrases ("due to the fact that", "in order to", "at this point in time") and flag each occurrence with a suggested concise replacement, an occurrence count, and character offsets. Dictionary-based heuristic: a flagged phrase is a candidate to tighten, not always wrong in context.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | The text to scan for wordy/redundant phrases |
No output schema declared.
No examples provided.
diff_env_example ~67
Diff a .env file against its .env.example template: flags keys missing from either side, plus keys present in both with an empty placeholder value in the example.
| Name | Type | Req | Description |
|---|---|---|---|
| env | string | yes | The .env file contents |
| example | string | yes | The .env.example file contents |
No output schema declared.
No examples provided.
diff_json ~46
Compare two JSON strings and return a structured diff showing added, removed, and changed keys.
| Name | Type | Req | Description |
|---|---|---|---|
| left | string | yes | Original JSON |
| right | string | yes | New/modified JSON |
No output schema declared.
No examples provided.
diff_json_detailed ~54
Diff two JSON objects (parsed values, not strings): returns a flat list of every path with its op (added/removed/changed/unchanged), plus counts.
| Name | Type | Req | Description |
|---|---|---|---|
| a | – | – | – |
| b | – | – | – |
No output schema declared.
No examples provided.
diff_json_patch ~105
Compare two JSON documents and generate an RFC 6902 JSON Patch (a list of add/remove/replace operations) that transforms the first into the second. Object keys produce add/remove/replace; arrays are compared position by position (not a minimal edit-distance diff, so a reordering is not detected as a move).
| Name | Type | Req | Description |
|---|---|---|---|
| a | string | yes | The source JSON document, as a JSON string |
| b | string | yes | The target JSON document, as a JSON string |
No output schema declared.
No examples provided.
docker_run_to_compose ~167
Convert one or more `docker run` commands into a docker-compose.yml (Compose Specification, no obsolete version: key). Handles \ line continuations, quoting, combined short flags (-it, -p8080:80), and several commands (one service each). Maps ports, volumes and --mount (declaring named volumes), env vars, --env-file, restart, networks (as external) and network_mode, healthchecks, resource limits, ulimits, --gpus, logging, labels, capabilities and the command after the image. Returns the YAML, the service names and warnings for flags with no Compose equivalent (like --rm). Parses only; nothing is executed.
| Name | Type | Req | Description |
|---|---|---|---|
| command | string | yes | One or more docker run commands, one per line or joined with && |
No output schema declared.
No examples provided.
escape_string ~49
Escape special characters in a string for use in JSON, JavaScript, HTML, URL, or CSV.
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | String to escape |
| mode | string | yes | Escape target format |
No output schema declared.
No examples provided.
estimate_audio_file_size ~216
Estimate how large an audio file will be before recording or exporting it. Mode "pcm" computes the uncompressed size from sample rate, bit depth, and channel count, plus a canonical 44-byte WAV header. Mode "compressed" computes it from a target bitrate. Pure arithmetic: no file is read, written, or encoded.
| Name | Type | Req | Description |
|---|---|---|---|
| bitDepth | number | – | Required for mode "pcm", bits per sample, e.g. 16 or 24 |
| bitrateKbps | number | – | Required for mode "compressed", e.g. 192 for a typical MP3 |
| channels | number | – | Required for mode "pcm", e.g. 1 = mono, 2 = stereo |
| durationSeconds | number | yes | Audio duration in seconds |
| mode | string | yes | "pcm" requires sampleRateHz/bitDepth/channels; "compressed" requires bitrateKbps |
| sampleRateHz | number | – | Required for mode "pcm", e.g. 44100 for CD quality |
No output schema declared.
No examples provided.
estimate_data_transfer_time ~178
Estimate the theoretical time to transfer a file of a given size over a connection of a given speed (decimal/SI file size units, standard networking speed units where Mbps is megabits/second and MBps is megabytes/second). Pass targetSeconds instead of speed/speedUnit to run the reverse calculation: the bandwidth required to hit that target time.
| Name | Type | Req | Description |
|---|---|---|---|
| fileSize | number | yes | The file size, in fileSizeUnit |
| fileSizeUnit | string | yes | The unit fileSize is expressed in |
| speed | number | – | The connection speed, in speedUnit (omit and pass targetSeconds for the reverse calculation) |
| speedUnit | string | – | The unit speed is expressed in |
| targetSeconds | number | – | Target transfer time in seconds; when set, computes the required bandwidth instead of the transfer time |
No output schema declared.
No examples provided.
estimate_password_entropy ~110
Estimate a password's entropy in bits from the character classes it actually draws from (lowercase, uppercase, digits, symbols, other/Unicode), using the pool-size x length method. Returns a strength label and crack-time estimates at four guess-rate scenarios, plus warnings for repeated runs, sequential runs, short length, and single-character-class passwords. Measures resistance to brute force over the theoretical character space, not real-world guessability against a breach database.
| Name | Type | Req | Description |
|---|---|---|---|
| password | string | yes | The password to analyze |
No output schema declared.
No examples provided.
estimate_tokens ~95
Estimate the token count and API cost for a text string across popular LLMs (GPT-4o, Claude, Gemini, etc.).
| Name | Type | Req | Description |
|---|---|---|---|
| model | string | – | Model slug (e.g. gpt-4o, claude-sonnet-4): omit for all models |
| output_tokens | integer | – | Expected output tokens (defaults to same as input) |
| text | string | yes | Text to estimate tokens for |
No output schema declared.
No examples provided.
expand_query ~38
Expand a search query with synonyms and stemmed variants for better retrieval.
| Name | Type | Req | Description |
|---|---|---|---|
| max_synonyms | integer | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
extract_entities ~31
Extract emails, phones, dates, IPs, currencies, hashtags from text.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | – |
No output schema declared.
No examples provided.
extract_json ~25
Extract JSON blocks from mixed LLM output text.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | – |
No output schema declared.
No examples provided.
extract_keywords ~41
Extract top keywords using TF-IDF scoring.
| Name | Type | Req | Description |
|---|---|---|---|
| max_keywords | integer | – | – |
| min_word_len | integer | – | – |
| text | string | yes | – |
No output schema declared.
No examples provided.
extract_markdown_footnotes ~72
Extract every Markdown-Extra-style footnote reference ([^label]) and definition ([^label]: text, with 4-space/tab-indented continuation lines) from a document, then flag references with no matching definition and definitions that are never referenced.
| Name | Type | Req | Description |
|---|---|---|---|
| markdown | string | yes | The Markdown document text |
No output schema declared.
No examples provided.
extract_markdown_link_references ~76
Extract every reference-style Markdown link ([text][ref], including the shortcut form [text][] and image references ![alt][ref]) alongside its [ref]: url "title" definition, then flag usages with no matching definition and definitions that no usage ever references.
| Name | Type | Req | Description |
|---|---|---|---|
| markdown | string | yes | The Markdown document text |
No output schema declared.
No examples provided.
extract_prompt_template_variables ~104
Extract every {{variable}}-style placeholder from a prompt template, reporting each unique variable's occurrence count and flagging ones used more than once. Optionally cross-check against a providedVars list to flag variables the template uses that are missing, and provided names the template never references.
| Name | Type | Req | Description |
|---|---|---|---|
| providedVars | array | – | Optional list of variable names already available, to cross-check against the template |
| template | string | yes | The prompt template text containing {{variable}} placeholders |
No output schema declared.
No examples provided.
extract_svg_sprite_symbols ~91
Parse an SVG sprite sheet's <symbol> definitions and list each one's id, viewBox, width, and height, alongside a ready-to-paste <use href="#id"></use> usage snippet. A symbol with no id is skipped (counted in skippedCount) since it can't be referenced by a <use> element at all.
| Name | Type | Req | Description |
|---|---|---|---|
| svg | string | yes | The SVG sprite sheet markup |
No output schema declared.
No examples provided.
extract_tables ~26
Extract HTML tables into JSON arrays with headers and rows.
| Name | Type | Req | Description |
|---|---|---|---|
| html | string | yes | – |
No output schema declared.
No examples provided.
extract_urls ~23
Extract all URLs from text or HTML.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | – |
No output schema declared.
No examples provided.
find_cron_overlaps ~110
Given two or more standard 5-field cron expressions, find every minute over the next N days where two or more of them fire at the same time, for example a nightly backup job colliding with a report job. Returns each colliding minute with the zero-based indexes of every expression that matched.
| Name | Type | Req | Description |
|---|---|---|---|
| expressions | array | yes | Two to ten standard 5-field cron expressions to check against each other |
| windowDays | number | – | How many days ahead to check, default 30 |
No output schema declared.
No examples provided.
find_csv_duplicate_rows ~164
Parse CSV/TSV data and group rows that share the same value across a chosen set of key columns, or the entire row if no key columns are given, so you can spot and clean up accidental duplicates before an import. Row numbers count data rows only (the header row, if any, is not counted).
| Name | Type | Req | Description |
|---|---|---|---|
| caseSensitive | boolean | – | Whether comparison is case-sensitive |
| csv | string | yes | CSV/TSV data to scan for duplicate rows |
| delimiter | string | – | Field delimiter (default ",") |
| hasHeader | boolean | – | Whether the first row is a header |
| keyColumns | array | – | Column names to compare; omit to compare the entire row |
| trimWhitespace | boolean | – | Whether to trim whitespace before comparing |
No output schema declared.
No examples provided.
find_duplicate_lockfile_versions ~104
Parse an npm (package-lock.json), yarn (yarn.lock), or pnpm (pnpm-lock.yaml) lockfile and report every package installed at more than one resolved version, with a count of how many install locations resolve to each version. Format is auto-detected from content unless given explicitly.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Force a format instead of auto-detecting it from content |
| lockfile | string | yes | The full lockfile contents |
No output schema declared.
No examples provided.
find_yaml_duplicate_keys ~54
Parse a YAML document and report every mapping key that collides with an earlier key in the same mapping scope, with the line and column of each repeated occurrence.
| Name | Type | Req | Description |
|---|---|---|---|
| yaml | string | yes | The YAML document to check |
No output schema declared.
No examples provided.
flatten_json ~37
Flatten nested JSON to dot-notation keys.
| Name | Type | Req | Description |
|---|---|---|---|
| json | – | – | – |
| separator | string | – | – |
| unflatten | boolean | – | – |
No output schema declared.
No examples provided.
format_few_shot_examples ~59
Format a list of input/output example pairs into a standard few-shot prompt template: numbered, XML-tagged, or delimiter-separated.
| Name | Type | Req | Description |
|---|---|---|---|
| delimiter | string | – | – |
| examples | array | yes | – |
| format | string | – | – |
No output schema declared.
No examples provided.
format_graphql ~46
Format or minify a GraphQL query or schema.
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | GraphQL query or schema string |
| minify | boolean | – | Minify instead of format |
No output schema declared.
No examples provided.
format_html ~32
Format and indent HTML markup.
| Name | Type | Req | Description |
|---|---|---|---|
| indent | integer | – | – |
| input | string | yes | HTML string to format |
No output schema declared.
No examples provided.
format_json ~150
Parse, validate and pretty-print a JSON string (strict RFC 8259). Indent with spaces or tabs, or minify with indent 0; optionally sort keys alphabetically at every level. Invalid JSON returns a specific error (trailing comma, unquoted key, single quotes, missing comma, comment, unclosed bracket) with its line and column. Valid JSON also lists warnings for duplicate keys and integers too large for a JavaScript number.
| Name | Type | Req | Description |
|---|---|---|---|
| indent | – | – | Spaces per level (default 2, 0 minifies) or "tab" |
| input | string | yes | JSON string to format |
| sortKeys | boolean | – | Sort object keys alphabetically at every level (default false) |
No output schema declared.
No examples provided.
format_ndjson ~60
Validate newline-delimited JSON (NDJSON/JSON Lines), report per-line errors, and pretty-print each valid line.
| Name | Type | Req | Description |
|---|---|---|---|
| indent | integer | – | Spaces per indent level |
| input | string | yes | NDJSON content: one JSON value per line |
No output schema declared.
No examples provided.
format_sql ~43
Format a SQL query with proper indentation and keyword uppercasing.
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | SQL query to format |
| uppercase | boolean | – | Uppercase SQL keywords |
No output schema declared.
No examples provided.
generate_csp_nonce ~94
Generate a cryptographically random, base64-encoded nonce for a Content-Security-Policy script-src or style-src directive, along with ready-to-paste header directive and <script>/<style nonce="..."> tag snippets. Generates a fresh, unique value on every call.
| Name | Type | Req | Description |
|---|---|---|---|
| byteLength | integer | – | Number of random bytes to encode (default 16 = 128 bits, the CSP spec's recommended minimum) |
No output schema declared.
No examples provided.
generate_etag ~134
Compute a content-hash ETag for the given content: digest it with MD5, SHA-1, or SHA-256, hex-encode it, and quote it into the exact string an ETag response header expects, with an optional weak-validator (W/) prefix. Hashes whatever content you give it; does not replicate any specific web server's own size/modification-time-based ETag algorithm.
| Name | Type | Req | Description |
|---|---|---|---|
| algorithm | string | – | Hash algorithm to use |
| content | string | yes | The content to hash into an ETag |
| weak | boolean | – | Whether to produce a weak validator (W/ prefix) |
No output schema declared.
No examples provided.
generate_hotp ~144
Generate an HOTP code (RFC 4226) for a given counter value from a base32-encoded shared secret. Supports 6-8 digit codes and SHA-1/SHA-256/SHA-512 (SHA-1 is the default per the RFC). The secret is never stored, only used for this one HMAC computation.
| Name | Type | Req | Description |
|---|---|---|---|
| algorithm | string | – | HMAC algorithm, default SHA1 |
| counter | integer | yes | The HOTP counter value |
| digits | integer | – | Code length, default 6 |
| secret | string | yes | The base32-encoded shared secret (RFC 4648, case-insensitive, padding optional) |
No output schema declared.
No examples provided.
generate_markdown_toc ~146
Scan a Markdown document's ATX headings (# through ######) and build a nested table of contents with GitHub-style anchor slugs, disambiguating duplicate headings with -1, -2, ... suffixes. 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 for headings |
| maxLevel | integer | – | Deepest heading level to include, defaults to 6 |
| minLevel | integer | – | Shallowest heading level to include, defaults to 1 |
| ordered | boolean | – | Render as a numbered list instead of a bullet list, defaults to false |
No output schema declared.
No examples provided.
generate_password ~53
Generate a cryptographically secure random password.
| Name | Type | Req | Description |
|---|---|---|---|
| length | integer | – | Password length |
| lowercase | boolean | – | – |
| numbers | boolean | – | – |
| symbols | boolean | – | – |
| uppercase | boolean | – | – |
No output schema declared.
No examples provided.
generate_qr ~41
Generate a QR code as an SVG string.
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | Text or URL to encode |
| size | integer | – | SVG size in px |
No output schema declared.
No examples provided.
generate_random_data ~54
Generate random mock data: names, emails, UUIDs, phone numbers, dates, colors, IPs, etc.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | Number of items |
| type | string | yes | Data type to generate |
No output schema declared.
No examples provided.
generate_robots_txt ~108
Generate a robots.txt file from one or more User-agent groups (each with Allow/Disallow rules and an optional Crawl-delay) plus a list of Sitemap URLs. The inverse of validate_robots_txt: a group with no Allow or Disallow rules gets an explicit empty Disallow line, the standard way to allow crawling everything.
| Name | Type | Req | Description |
|---|---|---|---|
| groups | array | yes | User-agent groups to emit, in order |
| sitemaps | array | – | Absolute sitemap URLs to append as Sitemap directives |
No output schema declared.
No examples provided.
generate_sri_hash ~90
Compute a Subresource Integrity (SRI) hash for a script or stylesheet's content: digest it with SHA-256, SHA-384, and SHA-512 and return each as the `<algorithm>-<base64>` string an HTML `integrity` attribute expects. Returns all three algorithms at once.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The exact file/script content to hash, byte-for-byte |
No output schema declared.
No examples provided.
generate_totp ~168
Generate the current TOTP code (RFC 6238) from a base32-encoded shared secret, plus how many seconds remain before it rotates. Defaults (30s period, 6 digits, SHA-1) match what Google Authenticator and most other authenticator apps use. Pass an explicit timestamp for deterministic/testable output.
| Name | Type | Req | Description |
|---|---|---|---|
| algorithm | string | – | HMAC algorithm, default SHA1 |
| digits | integer | – | Code length, default 6 |
| periodSeconds | integer | – | Time-step window in seconds, default 30 |
| secret | string | yes | The base32-encoded shared secret (RFC 4648, case-insensitive, padding optional) |
| timestamp | integer | – | Unix timestamp in seconds to compute the code for; defaults to the current time |
No output schema declared.
No examples provided.
generate_ulid ~31
Generate a ULID (Universally Unique Lexicographically Sortable Identifier).
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | – |
No output schema declared.
No examples provided.
generate_uuid ~45
Generate one or more UUIDs (v4 random or v7 time-ordered).
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | How many to generate |
| version | string | – | UUID version |
No output schema declared.
No examples provided.
hash ~48
Hash a string using MD5, SHA-1, SHA-256, SHA-384, or SHA-512.
| Name | Type | Req | Description |
|---|---|---|---|
| algorithm | string | – | – |
| input | string | yes | String to hash |
No output schema declared.
No examples provided.
hash_all ~47
Hash a string with all algorithms (MD5, SHA-1, SHA-256, SHA-384, SHA-512) at once.
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | String to hash |
No output schema declared.
No examples provided.
html_entities_decode ~39
Decode HTML entities back to plain text (e.g. < → <).
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | String with HTML entities to decode |
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.