Conversions across 221 color spaces, tested against cited sources: CSS strings, gamut, LUTs
Zpup is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Write a small 3D scene as JSON, get fixable errors back, and see the flat SVG from any angle.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user zpup-mcp '--' npx -y @zpup/mcp
# 2 — ask your agent for something these tools do
# get_reference, check_scene, get_scene and 2 more
Zpup costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Zpup as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user zpup-mcp '--' npx -y @zpup/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
5 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Returns the reference for writing a Zpup scene: the scene format, every shape and its options, conventions for axes and angles, and common mistakes. Read it once before writing a scene.
No parameter schema on file.
Checks a scene without drawing it. Returns every error with its path and how to fix it, and warnings for things that are valid but probably not intended (angles in radians, shapes outside the image, shapes of different colors passing through each other). A scene is plain JSON: { width, height,…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| scene | no | — |
Returns the scene the server remembers, as JSON: the last valid scene sent, with every change applied since. Use it to see the current indexes after several edits, or to keep the scene.
No parameter schema on file.
Draws a small 3D scene as a flat SVG picture and returns a PNG of it to look at, the SVG text, and any warnings. An invalid scene draws nothing and returns every error with its path and how to fix it. Pass views to see the same scene from several angles in one call, which is the quickest way to…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| scene | no | — | |
| changes | array | no | — |
| views | array | no | — |
| svg | boolean | no | — |
| preview_size | number | no | Longer side of the PNG in pixels. Default 512. |
| save_to | string | no | — |
Makes an SVG that turns the scene forever about one axis, with no JavaScript in the file, so it plays inside an <img> tag or a README. Returns PNG stills at even steps of the turn, so you can see what the animation shows. These files are large (tens to hundreds of KB), so pass save_to; the SVG…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| scene | no | — | |
| changes | array | no | — |
| axis | string | no | Which view angle turns. Default "y", a turntable. |
| duration | number | no | Seconds for one full turn. Default 8. |
| keyframes | number | no | Angles computed exactly, 4 to 720. More is smoother and larger. Default 36. |
| direction | string | no | — |
| preview_frames | integer | no | — |
| preview_size | number | no | Longer side of the PNG in pixels. Default 512. |
| save_to | string | no | Absolute path ending in .svg to write the file to. |
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Zpup or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tools were statically extracted from the published source (5 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| get_reference | no tags | |
| check_scene | no tags | |
| get_scene | no tags | |
| render_scene | no tags | |
| render_spin | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.3.0. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Zpup can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.