Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.JonathanWeerakkody/vectorise

NPM · VECTORIZER-MCP · 2 COMPONENTS

Vectorize images to SVG and export to PDF, EPS, DXF, PNG, JPG, or WEBP via Vectorise.Me.

0 this week 73 Trust /100

Last scanned (14 hours ago)

Scores higher than 46% of npm servers

Category Design and Media

Trust breakdown (7 categories)

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 Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 31 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
  • Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
  • 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 126 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability72
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 795 tokens (~159/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 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
What we tested

Checks we ran (15)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.

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 →

Changelog

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.

  • 19 Nov 26 0
    • Stability: 0.97 → pass security
  • 18 Nov 26 0
    • Stability: pass → 0.97 functional
  • 12 Nov 26 0
    • Stability: 0.97 → pass security
  • 11 Nov 26 +1

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

  • 9 Nov 26 +1

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

  • 8 Nov 26 −2
    • Stability: pass → 0.87 functional
  • 2 Nov 26 0
    • Stability: 0.97 → pass security
  • 1 Nov 26 +1

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

Diagnostics

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/vectorizer-mcp@0.2.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 1 finding
ID CVE Severity Vector Fix available
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 93 packages
Packages resolved 93
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~795 tokens

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 →

Tool Tokens
export_svg ~102

Convert an SVG file to PDF, EPS, DXF, PNG, JPG, or WEBP via Vectorise.Me. EPS and DXF require a Pro plan. Writes the result next to the input (or to output_path).

NameTypeReqDescription
formatstringyesTarget output format
output_pathstring–Where to save the output. Defaults to the input path with the new extension
svg_pathstringyesAbsolute path to the input SVG file

No output schema declared.

No examples provided.

get_capabilities ~29

List available export formats and per-format options supported by the Vectorise.Me API. No auth required.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_usage ~29

Show the plan, API credit balance, and recent daily usage for the configured Vectorise.Me API key.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

vectorize_batch ~308

Convert up to 20 raster image files to SVG in one call. The same settings (preset, quality_tier, etc.) apply to every image. Files are converted sequentially and each gets an independent result — one bad file does not fail the batch. SVGs are saved next to each input (or into output_dir). Credits are charged per successful conversion.

NameTypeReqDescription
color_modestring–Colour handling. Default color
image_pathsarrayyesAbsolute paths of the input image files (1–20)
output_dirstring–Directory to save all SVGs into. Defaults to saving next to each input file
palette_countinteger–Target number of colours (sets manual palette mode)
preserve_exact_colorsboolean–Keep source colours without merging similar shades
presetstring–Friendly preset matching the app UI: auto (engine detects image type), logo (sharp edges, exact brand colours), illustration (drawings/cartoons/clipart), photo (smooth tonal gradients), pixel_art (pi…
quality_profilestring–Advanced: engine profile. Prefer `preset` unless you know the engine. Default auto
quality_tierstring–Speed/quality trade-off. Default balanced_crisp (credits: fast=1, balanced_crisp=2, high_precision=5)

No output schema declared.

No examples provided.

vectorize_image ~327

Convert a raster image file (JPG, PNG, BMP, WEBP, AVIF — up to 25 MB) into a scalable SVG vector. Writes the SVG next to the input file (or to output_path) and returns the saved path plus conversion stats. For most images just set `preset` (logo, photo, illustration, pixel_art, technical_drawing) or leave everything unset for full auto-detection. Use quality_tier to trade speed vs fidelity.

NameTypeReqDescription
color_modestring–Colour handling. Default color
image_pathstringyesAbsolute path to the input image file
output_pathstring–Where to save the SVG. Defaults to the input path with a .svg extension
palette_countinteger–Target number of colours (sets manual palette mode)
preserve_exact_colorsboolean–Keep source colours without merging similar shades
presetstring–Friendly preset matching the app UI: auto (engine detects image type), logo (sharp edges, exact brand colours), illustration (drawings/cartoons/clipart), photo (smooth tonal gradients), pixel_art (pi…
quality_profilestring–Advanced: engine profile. Prefer `preset` unless you know the engine. Default auto
quality_tierstring–Speed/quality trade-off. Default balanced_crisp (credits: fast=1, balanced_crisp=2, high_precision=5)

No output schema declared.

No examples provided.

Install

How do I install the io.github.JonathanWeerakkody/vectorise MCP server?

io.github.JonathanWeerakkody/vectorise runs locally as an npm package, launched with npx -y vectorizer-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 · vectorizer-mcp

# add to Claude Code
claude mcp add jonathanweerakkody-vectorise -- npx -y vectorizer-mcp
Common questions

What is the io.github.JonathanWeerakkody/vectorise MCP server?

io.github.JonathanWeerakkody/vectorise is an MCP server listed in the public MCP registry as io.github.JonathanWeerakkody/vectorise. Vectorize images to SVG and export to PDF, EPS, DXF, PNG, JPG, or WEBP via Vectorise.Me. This page covers its npm package (vectorizer-mcp).

Is the io.github.JonathanWeerakkody/vectorise MCP server safe to use?

io.github.JonathanWeerakkody/vectorise scores 73 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 2026. It declares no install or post-install scripts. 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.JonathanWeerakkody/vectorise MCP server expose?

io.github.JonathanWeerakkody/vectorise exposes 5 tools: vectorize_image, vectorize_batch, export_svg, get_usage, get_capabilities. Their descriptions and schemas cost roughly 795 tokens of context every time the server is loaded.

Is the io.github.JonathanWeerakkody/vectorise MCP server still maintained?

io.github.JonathanWeerakkody/vectorise 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 io.github.JonathanWeerakkody/vectorise MCP server under?

io.github.JonathanWeerakkody/vectorise declares the MIT 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.JonathanWeerakkody/vectorise MCP server?

VerifyMCP ran 15 checks on io.github.JonathanWeerakkody/vectorise, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.JonathanWeerakkody/vectorise: Security disclosure. 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.