io.github.JonathanWeerakkody/vectorise
NPM · VECTORIZER-MCP · 2 COMPONENTS · SCANNED SEP 25
Vectorize images to SVG and export to PDF, EPS, DXF, PNG, JPG, or WEBP via Vectorise.Me.
Available components
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 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 69 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 Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
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
claude mcp add jonathanweerakkody-vectorise -- npx -y vectorizer-mcp
{
"mcpServers": {
"jonathanweerakkody-vectorise": {
"command": "npx",
"args": [
"-y",
"vectorizer-mcp"
]
}
}
} {
"servers": {
"jonathanweerakkody-vectorise": {
"command": "npx",
"args": [
"-y",
"vectorizer-mcp"
]
}
}
} codex mcp add jonathanweerakkody-vectorise -- npx -y vectorizer-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"jonathanweerakkody-vectorise": {
"type": "local",
"command": [
"npx",
"-y",
"vectorizer-mcp"
],
"enabled": true
}
}
} openclaw mcp add jonathanweerakkody-vectorise --command npx --arg -y --arg vectorizer-mcp
mcp_servers:
jonathanweerakkody-vectorise:
command: "npx"
args: ["-y", "vectorizer-mcp"] {
"McpServers": {
"jonathanweerakkody-vectorise": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"vectorizer-mcp"
]
}
}
} assistant mcp add jonathanweerakkody-vectorise -t stdio -c npx -a -y vectorizer-mcp
{
"mcpServers": {
"jonathanweerakkody-vectorise": {
"command": "npx",
"args": [
"-y",
"vectorizer-mcp"
]
}
}
} 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.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Sept 26 −3
- Stability: pass → 0.80 functional
- 22 Sept 26 0
- Stability: 0.97 → pass security
- 21 Sept 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.
- 19 Sept 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.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
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 25 Sept 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 →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| 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 →
export_svg Export SVG to another format ~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).
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | yes | Target output format |
| output_path | string | – | Where to save the output. Defaults to the input path with the new extension |
| svg_path | string | yes | Absolute path to the input SVG file |
No output schema declared.
No examples provided.
get_capabilities Get export 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 Get API usage and credits ~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 Vectorize multiple images to SVG ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| color_mode | string | – | Colour handling. Default color |
| image_paths | array | yes | Absolute paths of the input image files (1–20) |
| output_dir | string | – | Directory to save all SVGs into. Defaults to saving next to each input file |
| palette_count | integer | – | Target number of colours (sets manual palette mode) |
| preserve_exact_colors | boolean | – | Keep source colours without merging similar shades |
| preset | string | – | 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_profile | string | – | Advanced: engine profile. Prefer `preset` unless you know the engine. Default auto |
| quality_tier | string | – | 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 Vectorize image to SVG ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| color_mode | string | – | Colour handling. Default color |
| image_path | string | yes | Absolute path to the input image file |
| output_path | string | – | Where to save the SVG. Defaults to the input path with a .svg extension |
| palette_count | integer | – | Target number of colours (sets manual palette mode) |
| preserve_exact_colors | boolean | – | Keep source colours without merging similar shades |
| preset | string | – | 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_profile | string | – | Advanced: engine profile. Prefer `preset` unless you know the engine. Default auto |
| quality_tier | string | – | Speed/quality trade-off. Default balanced_crisp (credits: fast=1, balanced_crisp=2, high_precision=5) |
No output schema declared.
No examples provided.
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 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 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 25 September 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.