# io.github.Baukaalm/optiq-mcp (npm · optiq-mcp)

Optimise project images locally with verified quality (SSIM or pixel-exact): JPEG, PNG, WebP, AVIF.

- Trust score: 81/100 (high trust)
- Change this week: +14
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `optiq-mcp`: 81/100 (this document), [markdown](https://verifymcp.io/servers/baukaalm-optiq-mcp/optiq-mcp.md), [page](https://verifymcp.io/servers/baukaalm-optiq-mcp/optiq-mcp)

## Channel facts

- Registry: `npm`
- Package: `optiq-mcp`
- Version: `0.1.0-beta.3`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 99/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 3 of 31 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to Baukaalm/optiq).
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 6 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 58/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1519 tokens (~759/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the io.github.Baukaalm/optiq-mcp server?

io.github.Baukaalm/optiq-mcp runs locally as an npm package, launched with npx -y optiq-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add baukaalm-optiq-mcp -- npx -y optiq-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "baukaalm-optiq-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "optiq-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "baukaalm-optiq-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "optiq-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add baukaalm-optiq-mcp -- npx -y optiq-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "baukaalm-optiq-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "optiq-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add baukaalm-optiq-mcp --command npx --arg -y --arg optiq-mcp
```

### Hermes

```yaml
mcp_servers:
  baukaalm-optiq-mcp:
    command: "npx"
    args: ["-y", "optiq-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "baukaalm-optiq-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "optiq-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add baukaalm-optiq-mcp -t stdio -c npx -a -y optiq-mcp
```

### Other

```json
{
  "mcpServers": {
    "baukaalm-optiq-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "optiq-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 79, +12)

- [security improvement] Known CVEs: unverified → pass
- [functional improvement] Dependency health: unverified → 0.95

### 2026-10-29 (score 67, −11)

- [security regression] Known CVEs: pass → unverified
- [security regression] Stability: 0.00 → unverified
- [security regression] Tool safety: pass → unverified
- [functional regression] Schema quality: 431 → 759
- [functional regression] Schema quality: 431 → 748
- [functional regression] Dependency health: 0.96 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.1.0-beta.0 → 0.1.0-beta.3
- [functional] Package version: 0.1.0-beta.0 → 0.1.0-beta.2
- [functional] Package version: 0.1.0-beta.0 → 0.1.0-beta.1

### 2026-10-28 (score 78)

First indexed and scored.

## MCP tools (2)

### `analyze_images` (~632 tokens)

Analyze images (dry run)

Read-only dry run: runs the full optimisation in memory and reports, per image, the format Optiq would choose, bytes before and after, and the measured quality (SSIM, or pixel-exact). Writes nothing. Use it first to show the user the expected savings, then call optimize_images with the same arguments. Main parameters: paths (files or folders), mode (how strict the quality check is), keepFormat/formats (whether and to what the format may change), maxSize (downscale), stripMetadata (drop EXIF/GPS). Cost: it does the same work as optimize_images, several encodes per image, typically 0.3-3 s per image on a modern laptop (fast mode is quicker; very large screenshots in visually-lossless can take tens of seconds). For hundreds of images, try one subfolder first. Progress is reported per file and the call can be cancelled.

Input parameters:

- `formats` (array): Formats Optiq may choose when the format may change. Default: all four (fast mode: no avif). Drop avif if the site must support browsers older than Safari 16.4. JPEG is never chosen for images with t…
- `keepFormat` (boolean): Never change the file format (a .png stays PNG). Default: true for in-place writes and for analysis, false when writing to outDir. Set false in analysis to see what converting to WebP/AVIF would save.
- `maxSize` (integer): Downscale so the longest side is at most this many pixels, e.g. 2560 for camera photos on a website. Smaller images are not enlarged. Allowed in lossless mode too (the resize itself changes pixels).
- `minQuality` (number): Custom SSIM threshold for perceptual modes instead of the mode's default, e.g. 0.98. Higher keeps more detail and saves less. Ignored in lossless mode.
- `minSaving` (number): Keep a file unchanged unless it gets at least this share smaller (0.05 = 5%). Default 0.02. Raise it to avoid churning files for tiny gains.
- `mode` (string): How strict the quality check is. lossless: decoded pixels verified identical (JPEG inputs only get metadata changes). visually-lossless: SSIM >= 0.99. balanced (default): SSIM >= 0.975. fast: same th…
- `paths` (array, required): Image files and/or folders. Folders are searched recursively for jpg, jpeg, png, webp, avif, gif and svg; dot-folders are skipped. Use absolute paths; relative ones resolve against the server's worki…
- `stripMetadata` (boolean): Remove EXIF (including GPS location, camera serial) and XMP. Recommended before publishing personal photos. Colour profiles that matter (non-sRGB ICC) and image orientation are preserved either way.

Output parameters:

- `dryRun` (boolean)
- `files` (array)
- `omittedFiles` (number): Files processed but not listed (the list is capped); totals include them.
- `totals` (object)

### `optimize_images` (~729 tokens)

Optimize images

Optimises images and writes the results. If the user only wants to know how much could be saved, or has not agreed to changes yet, use analyze_images instead: it takes the same arguments and writes nothing. write: "in-place" overwrites each file and keeps its format and name, so references in code stay valid (atomic rename). write: "out-dir" writes to outDir, mirroring the folder structure, and may change formats; extensions change accordingly, so update references. A file is only replaced when the result passes the quality check and is smaller. Files Optiq already compressed lossily are skipped (unless reoptimize is true), so calling this twice is safe. Choosing parameters: mode visually-lossless for hero images, artwork and product photos, lossless for logos and UI assets that must stay exact, balanced otherwise; stripMetadata before publishing personal photos (GPS); formats without avif if old browsers matter. Takes the same time as analyze_images (typically 0.3-3 s per image).

Input parameters:

- `formats` (array): Formats Optiq may choose when the format may change. Default: all four (fast mode: no avif). Drop avif if the site must support browsers older than Safari 16.4. JPEG is never chosen for images with t…
- `keepFormat` (boolean): Never change the file format (a .png stays PNG). Default: true for in-place writes and for analysis, false when writing to outDir. Set false in analysis to see what converting to WebP/AVIF would save.
- `maxSize` (integer): Downscale so the longest side is at most this many pixels, e.g. 2560 for camera photos on a website. Smaller images are not enlarged. Allowed in lossless mode too (the resize itself changes pixels).
- `minQuality` (number): Custom SSIM threshold for perceptual modes instead of the mode's default, e.g. 0.98. Higher keeps more detail and saves less. Ignored in lossless mode.
- `minSaving` (number): Keep a file unchanged unless it gets at least this share smaller (0.05 = 5%). Default 0.02. Raise it to avoid churning files for tiny gains.
- `mode` (string): How strict the quality check is. lossless: decoded pixels verified identical (JPEG inputs only get metadata changes). visually-lossless: SSIM >= 0.99. balanced (default): SSIM >= 0.975. fast: same th…
- `outDir` (string): Required when write is "out-dir".
- `paths` (array, required): Image files and/or folders. Folders are searched recursively for jpg, jpeg, png, webp, avif, gif and svg; dot-folders are skipped. Use absolute paths; relative ones resolve against the server's worki…
- `reoptimize` (boolean): Re-encode files Optiq already compressed lossily. Each lossy pass loses a little more quality; leave false unless the user asks.
- `stripMetadata` (boolean): Remove EXIF (including GPS location, camera serial) and XMP. Recommended before publishing personal photos. Colour profiles that matter (non-sRGB ICC) and image orientation are preserved either way.
- `write` (string, required): "in-place" overwrites inputs; "out-dir" writes to outDir.

Output parameters:

- `dryRun` (boolean)
- `files` (array)
- `omittedFiles` (number): Files processed but not listed (the list is capped); totals include them.
- `totals` (object)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/baukaalm-optiq-mcp/optiq-mcp#diagnostics

## Score history

- 2026-11-05: 81
- 2026-11-04: 81
- 2026-11-03: 80
- 2026-11-02: 80
- 2026-11-01: 79
- 2026-10-31: 79
- 2026-10-30: 79
- 2026-10-29: 67
- 2026-10-28: 78

## Common questions

### What is the io.github.Baukaalm/optiq-mcp server?

io.github.Baukaalm/optiq-mcp is listed in the public MCP registry as io.github.Baukaalm/optiq-mcp. Optimise project images locally with verified quality (SSIM or pixel-exact): JPEG, PNG, WebP, AVIF. This page covers its npm package (optiq-mcp).

### Is the io.github.Baukaalm/optiq-mcp server safe to use?

io.github.Baukaalm/optiq-mcp scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the io.github.Baukaalm/optiq-mcp server expose?

io.github.Baukaalm/optiq-mcp exposes 2 tools: analyze_images, optimize_images. Their descriptions and schemas cost roughly 1,361 tokens of context every time the server is loaded.

### Is the io.github.Baukaalm/optiq-mcp server still maintained?

io.github.Baukaalm/optiq-mcp is still listed as active in the MCP registry. We last reached this channel on 5 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 io.github.Baukaalm/optiq-mcp server under?

io.github.Baukaalm/optiq-mcp declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the io.github.Baukaalm/optiq-mcp server?

VerifyMCP ran 16 checks on io.github.Baukaalm/optiq-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/optiq-mcp
- Socket report: https://socket.dev/npm/package/optiq-mcp
- Repository: https://github.com/Baukaalm/optiq
- Changelog RSS feed: https://verifymcp.io/servers/baukaalm-optiq-mcp/optiq-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/baukaalm-optiq-mcp/optiq-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/baukaalm-optiq-mcp/optiq-mcp.json
- HTML version of this page: https://verifymcp.io/servers/baukaalm-optiq-mcp/optiq-mcp