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 →
html_entities_encode ~36
Encode special characters as HTML entities (e.g. < → <).
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | HTML string to encode |
No output schema declared.
No examples provided.
html_to_jsx ~170
Convert an HTML snippet to React JSX: class to className, for to htmlFor (and 60+ other attribute renames, SVG attributes like stroke-width to strokeWidth), inline style strings to style objects, self-closing void elements, comments to {/* */}, escaped braces in text, input value/checked to defaultValue/defaultChecked, and inline event handlers wrapped in arrow functions. Multiple top-level nodes are wrapped in a fragment. Optionally wraps the result in an exported function component. Returns the JSX plus warnings about anything that needs a manual look.
| Name | Type | Req | Description |
|---|---|---|---|
| componentName | string | – | Optional PascalCase component name, e.g. "Hero"; wraps the JSX in `export default function Hero() { return (...) }` |
| html | string | yes | The HTML snippet or document to convert |
No output schema declared.
No examples provided.
html_to_markdown ~26
Convert HTML to Markdown.
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | HTML string to convert |
No output schema declared.
No examples provided.
infer_csv_column_types ~146
Parse CSV/TSV data and infer each column's data type (integer, float, boolean, ISO 8601 date, or string) by classifying every non-empty value and finding the tightest type that fits them all: all-integer values infer as integer, a mix of integers and decimals infers as float, and anything that doesn't fit a narrower type falls back to string. Empty cells mark a column nullable but don't affect its inferred type.
| Name | Type | Req | Description |
|---|---|---|---|
| csv | string | yes | CSV/TSV data to infer column types from |
| delimiter | string | – | Field delimiter (default ",") |
| hasHeader | boolean | – | Whether the first row is a header |
No output schema declared.
No examples provided.
inspect_gif_frames ~89
Walk a GIF87a/89a file's block structure (image descriptors, graphic control extensions, the NETSCAPE2.0 application extension) to report frame count, total animation duration, and loop count, without decoding any LZW-compressed pixel data.
| Name | Type | Req | Description |
|---|---|---|---|
| gif_base64 | string | yes | Base64-encoded GIF file bytes, optionally prefixed with a data: URL scheme |
No output schema declared.
No examples provided.
intersect_semver_ranges ~110
Determine whether two semver ranges overlap and, if so, the intersecting range. Supports the same caret/tilde/comparison-operator/exact-version syntax (combined with || or space-separated AND) as the semver tool.
| Name | Type | Req | Description |
|---|---|---|---|
| rangeA | string | yes | The first semver range, e.g. "^1.2.0" |
| rangeB | string | yes | The second semver range, e.g. ">=1.5.0 <2.0.0" |
No output schema declared.
No examples provided.
json_schema_to_typescript ~126
Convert a JSON Schema document into TypeScript interfaces/types. Unlike json_to_typescript (which infers types from an example data payload), this reads the schema's declared type/enum/required keywords directly, so optional vs. required fields and enum/union types come through accurately. Understands local $ref into $defs/definitions, items for arrays, additionalProperties, and renders description as a JSDoc comment.
| Name | Type | Req | Description |
|---|---|---|---|
| root_name | string | – | Name for the root generated interface/type |
| schema | string | yes | The JSON Schema document, as a JSON string |
No output schema declared.
No examples provided.
json_to_csv ~30
Convert a JSON array of objects to CSV format.
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | JSON array of objects |
No output schema declared.
No examples provided.
json_to_go ~37
Generate Go struct definitions from a JSON object.
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | JSON string |
| name | string | – | Root struct name |
No output schema declared.
No examples provided.
json_to_python ~45
Generate Python TypedDict, dataclass, or Pydantic models from a JSON object.
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | JSON string |
| style | string | – | Output style |
No output schema declared.
No examples provided.
json_to_typescript ~38
Generate TypeScript interfaces from a JSON object.
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | JSON string |
| name | string | – | Root interface name |
No output schema declared.
No examples provided.
json_to_yaml ~25
Convert a JSON string to YAML.
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | JSON string |
No output schema declared.
No examples provided.
json_to_zod ~29
Generate a Zod schema from a JSON object.
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | JSON string |
No output schema declared.
No examples provided.
jsonpath ~50
Evaluate a JSONPath expression against a JSON string and return matching values.
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | JSON string |
| path | string | yes | JSONPath expression e.g. $.store.book[*].author |
No output schema declared.
No examples provided.
line_operations ~45
Sort, deduplicate, reverse, shuffle, trim, or number lines of text.
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | Multi-line text |
| operation | string | yes | Operation to apply |
No output schema declared.
No examples provided.
lint_conventional_commit ~169
Lint a commit message against the Conventional Commits v1.0.0 spec: header format (type(scope)!: description), blank-line separation before the body/footers, footer token format, and BREAKING CHANGE casing. Returns the parsed type/scope/description/body/footers plus a list of error and warning findings.
| Name | Type | Req | Description |
|---|---|---|---|
| maxHeaderLength | number | – | Header length that triggers a warning (default 100) |
| message | string | yes | The full commit message: header, optional blank line, optional body, optional footers |
| types | array | – | Override the recognized type list (default: build, chore, ci, docs, feat, fix, perf, refactor, revert, style, test). Unrecognized types are a warning, not an error. |
No output schema declared.
No examples provided.
lint_dockerfile ~91
Lint a Dockerfile for 4 common mistakes: a base image with no tag or pinned to `:latest`, a final stage with no WORKDIR, a final stage with no USER (running as root), and ADD used on a plain local file/directory where COPY would do. Returns a list of findings plus the parsed build stages.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The full Dockerfile text |
No output schema declared.
No examples provided.
lint_tool_schema ~138
Lint an LLM tool/function-calling definition (OpenAI, Anthropic, or MCP format — a single definition, an array of them, or a {tools:[...]} wrapper) for mistakes that measurably hurt model accuracy: a missing or vague description, an invalid tool name, a non-object top-level parameter schema, properties missing descriptions, an empty enum, a "required" entry with no matching property, or duplicate tool names.
| Name | Type | Req | Description |
|---|---|---|---|
| schema | string | yes | JSON text: a single tool definition, an array of them, or a {tools:[...]} wrapper, in OpenAI/Anthropic/MCP format |
No output schema declared.
No examples provided.
list_close_codes ~36
List every well-known WebSocket close code (1000-1015) defined directly by RFC 6455, in ascending order.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_websocket_opcodes ~44
List every WebSocket frame opcode (0x0-0xF), the full 4-bit opcode space defined by RFC 6455, in ascending order.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
lookup_close_code ~56
Look up what a WebSocket close code means, per the RFC 6455 close code definitions and the IANA WebSocket Close Code Number Registry reserved ranges.
| Name | Type | Req | Description |
|---|---|---|---|
| code | integer | yes | The WebSocket close code to look up |
No output schema declared.
No examples provided.
lookup_emoji ~112
Search a curated table of several hundred common emoji by name, GitHub-style shortcode, or keyword (mode "search", the default), or look one up exactly by shortcode, character, or category (modes "shortcode", "char", "category"). Not the full 3,000+ Unicode emoji set.
| Name | Type | Req | Description |
|---|---|---|---|
| mode | string | – | Lookup mode; defaults to "search" |
| query | string | yes | The search text, exact shortcode, exact emoji character, or category name, depending on mode |
No output schema declared.
No examples provided.
lookup_mime ~68
Look up the MIME type for a file extension, or the file extension(s) registered for a MIME type, from a static table of well-known content types.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | A file extension (with or without a leading dot) or a MIME type (containing a "/") |
No output schema declared.
No examples provided.
lookup_websocket_opcode ~107
Look up what a WebSocket frame opcode means per RFC 6455: 0x0-0x2 are data frames (continuation, text, binary), 0x8-0xA are control frames (close, ping, pong), and the rest of the 4-bit opcode space is reserved for future protocol revisions.
| Name | Type | Req | Description |
|---|---|---|---|
| opcode | integer | yes | The WebSocket frame opcode to look up (0-15 / 0x0-0xF) |
No output schema declared.
No examples provided.
lorem_ipsum ~29
Generate Lorem Ipsum placeholder text.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | – |
| unit | string | – | – |
No output schema declared.
No examples provided.
merge_json ~31
Deep merge two JSON objects.
| Name | Type | Req | Description |
|---|---|---|---|
| base | – | – | – |
| override | – | – | – |
| strategy | string | – | – |
No output schema declared.
No examples provided.
minify_css ~29
Minify CSS by removing whitespace and comments.
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | CSS to minify |
No output schema declared.
No examples provided.
minify_js ~32
Minify JavaScript by removing whitespace and comments.
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | JavaScript code to minify |
No output schema declared.
No examples provided.
minify_json ~31
Minify a JSON string by removing all whitespace.
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | JSON string to minify |
No output schema declared.
No examples provided.
ndjson_to_csv ~59
Convert NDJSON (newline-delimited JSON, one flat object per line) into CSV, inferring the header row from the union of keys across every line.
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | NDJSON content: one flat JSON object per line |
No output schema declared.
No examples provided.
number_to_words ~45
Convert a number to its English words representation, Roman numerals, or ordinal form.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Output format |
| number | number | yes | Number to convert |
No output schema declared.
No examples provided.
optimize_svg ~27
Optimize and minify an SVG string.
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | SVG content to optimize |
No output schema declared.
No examples provided.
parse_accept_language ~80
Parse an existing Accept-Language header value (with or without a leading "Accept-Language:" label) into its ranked locale/quality pairs, sorted by descending quality per RFC 9110 section 12.5.4 (a missing ";q=" defaults to 1).
| Name | Type | Req | Description |
|---|---|---|---|
| header | string | yes | The Accept-Language header value to parse |
No output schema declared.
No examples provided.
parse_alt_svc_header ~66
Parse an existing Alt-Svc header value (with or without a leading "Alt-Svc:" label), including the special "clear" value, into its individual alternative services with plain-English protocol notes.
| Name | Type | Req | Description |
|---|---|---|---|
| header | string | yes | The Alt-Svc header value to parse |
No output schema declared.
No examples provided.
parse_authorization_header ~102
Parse an Authorization header value into its scheme and credentials. `Basic` is base64-decoded into username/password, `Bearer` returns the token as-is, and any other scheme (Digest, OAuth, custom) is parsed as comma-separated `key=value` / `key="value"` parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| header | string | yes | The Authorization header value to parse, e.g. "Bearer eyJ..." or "Basic YWxpY2U6..." |
No output schema declared.
No examples provided.
parse_caa_record ~81
Parse a CAA DNS record's zone-file text representation (as returned by `dig CAA` or stored in a zone file), e.g. `0 issue "letsencrypt.org"`, into its flags, tag, authorized domain, and any "; key=value" parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| raw | string | yes | The CAA record string to parse |
No output schema declared.
No examples provided.
parse_clear_site_data_header ~63
Parse an existing Clear-Site-Data header value (with or without a leading "Clear-Site-Data:" label, quoted or unquoted) into its individual directives.
| Name | Type | Req | Description |
|---|---|---|---|
| header | string | yes | The Clear-Site-Data header value to parse |
No output schema declared.
No examples provided.
parse_client_hint_headers ~106
Parse raw request-header text, one "Header-Name: value" per line, into decoded client hint values: brand/version pairs for Sec-CH-UA-style headers, booleans for ?1/?0 values, unquoted strings, and numbers. Lines whose header name isn't a recognized client hint are returned separately under "unrecognized" rather than dropped.
| Name | Type | Req | Description |
|---|---|---|---|
| headers | string | yes | Raw request-header text to parse, one "Header-Name: value" per line |
No output schema declared.
No examples provided.
parse_commit_trailers ~108
Parse a commit message's trailer block (Co-authored-by, Signed-off-by, Fixes, Reviewed-by, etc.) per git's RFC 822-style trailer convention (git-interpret-trailers): the last paragraph of the message, where every line is either a "Key: value" pair or an indented continuation of the previous trailer's value. Returns the trailers plus the message body with the trailer block removed.
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | The full commit message |
No output schema declared.
No examples provided.
parse_connection_string ~102
Parse a database connection URI (postgres://, mysql://, mongodb://, mongodb+srv://, redis://, amqp://, and similar generic scheme:// connection strings) into its scheme, credentials, one or more hosts (mongodb-style comma-separated host lists included), database/path, and query parameters. Pure offline parse: never connects, resolves DNS, or validates the driver/scheme combination.
| Name | Type | Req | Description |
|---|---|---|---|
| connectionString | string | yes | The database connection string to parse |
No output schema declared.
No examples provided.
parse_content_disposition ~53
Parse a Content-Disposition header value into its disposition type, filename (decoding an RFC 5987 filename* parameter if present), and raw parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| header | string | yes | The raw Content-Disposition header value |
No output schema declared.
No examples provided.
parse_content_range_header ~91
Parse a Content-Range response header (e.g. "bytes 200-1000/67589" or "bytes */67589" for an unsatisfiable range) into its unit, byte bounds, and total resource size, so you can verify what a server actually sent back for a partial/resumable request.
| Name | Type | Req | Description |
|---|---|---|---|
| header | string | yes | The Content-Range header value to parse |
No output schema declared.
No examples provided.
parse_cron ~41
Parse a cron expression and return a human-readable description.
| Name | Type | Req | Description |
|---|---|---|---|
| expression | string | yes | Cron expression e.g. "0 9 * * MON-FRI" |
No output schema declared.
No examples provided.
parse_csv ~37
Parse a CSV string and return the data as JSON.
| Name | Type | Req | Description |
|---|---|---|---|
| delimiter | string | – | Field delimiter |
| input | string | yes | CSV content |
No output schema declared.
No examples provided.
parse_docker_image ~49
Parse a Docker image reference into registry, namespace, repository, tag, and digest.
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | Docker image reference e.g. "nginx:1.21-alpine" |
No output schema declared.
No examples provided.
parse_env ~33
Parse a .env file and return all key-value pairs with validation.
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | .env file contents |
No output schema declared.
No examples provided.
parse_github_url ~93
Parse a github.com URL (repo, pull request, issue, commit, file, directory, or release tag) into structured components, including an optional #L10-L20 line-range anchor for file URLs. SSH remotes and other Git hosts are out of scope.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The github.com URL to parse, e.g. https://github.com/owner/repo/pull/123 |
No output schema declared.
No examples provided.
parse_har ~53
Parse a browser DevTools .har network export into a readable list of requests (method, URL, status, size, timing) plus aggregate summary stats.
| Name | Type | Req | Description |
|---|---|---|---|
| har | string | yes | Raw HAR file contents (JSON) |
No output schema declared.
No examples provided.
parse_hsts_header ~77
Parse an existing Strict-Transport-Security header value (with or without a leading "Strict-Transport-Security:" label) into its max-age, includeSubDomains, and preload fields, flagging whether it qualifies for browser HSTS preload lists.
| Name | Type | Req | Description |
|---|---|---|---|
| header | string | yes | The Strict-Transport-Security header value to parse |
No output schema declared.
No examples provided.
parse_ipv6_address ~123
Expand an IPv6 address to its full 8-group form and compress it to its RFC 5952 canonical shortest form, classify its address type (loopback, link-local, unique-local, multicast, IPv4-mapped, documentation, or global unicast), and separate out an optional zone ID. Understands an embedded IPv4 suffix like "::ffff:192.168.1.1".
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The IPv6 address to expand/compress, e.g. "2001:db8::ff00:42:8329" |
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.