MCP server for interacting with the Scryfall MTG API
mc-asset — Minecraft Pixel Asset Engine 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
Deterministic Minecraft pixel-art engine: textures, animation sheets, and pack validation.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user mc-asset-minecraft-pixel-asset-engine-mcp '--' npx -y mc-asset mcp
# 2 — ask your agent for something these tools do
# analyze_asset, pixelize_asset, render_pixel_asset and 17 more
mc-asset — Minecraft Pixel Asset Engine costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
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 mc-asset — Minecraft Pixel Asset Engine 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 mc-asset-minecraft-pixel-asset-engine-mcp '--' npx -y mc-asset 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.
20 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.
Analyze a raster image (PNG, JPEG, WebP) and return a read-only report: dimensions, palette, predicted alpha classification, pixel-art characteristics, and processing recommendations. Reads only, never writes.
No parameter schema on file.
Run a reference raster image through the deterministic pixelize pipeline and return PNG bytes and/or the editable .mcpx source. The input must be PNG, JPEG, or WebP, never .mcpx.
No parameter schema on file.
Render a hand-authored ASCII Grid (inline text or a .grid file, exactly one) into PNG bytes and/or the editable .mcpx source, with an optional batch applied after parsing. For pixel-level authorship without per-pixel tool calls.
No parameter schema on file.
Apply a batch of Core pixel/layer/region operations to an editable .mcpx source in one call (atomic by default: the first failure rolls everything back). This is the batch-edit slot; never split pixel work across hundreds of per-pixel tool calls.
No parameter schema on file.
Recolor an editable .mcpx source with a builtin material id, optionally limited to one region id, and return PNG bytes and/or the recolored source.
No parameter schema on file.
Fan out one editable .mcpx source into per-material variants under an explicit output directory, each starting from the pristine source so reruns stay byte-identical.
No parameter schema on file.
Validate an asset file and return a read-only verdict with findings. Reads only, never writes; an optional explicit .mcmeta path is used verbatim.
No parameter schema on file.
Decode a raster image (PNG, JPEG, WebP) into the Pixel Canvas with an optional batch applied after import. Returns PNG bytes and/or the editable .mcpx source via explicit output paths or embedded artifacts; no force, mkdir, or in-place writes.
No parameter schema on file.
Build an editable .mcpx source into a texture or re-serialize the source, with an optional batch applied after parsing. Returns PNG bytes and/or the built source via explicit output paths or embedded artifacts; no force, mkdir, or in-place writes.
No parameter schema on file.
Apply one spatial transformation (flip, rotate, crop, pad, resize, or translate) to a raster image or .mcpx source. Returns PNG bytes and/or the editable source via explicit output paths or embedded artifacts; no force, mkdir, or in-place writes.
No parameter schema on file.
Reduce the distinct colors of a raster image or .mcpx source to a target count, optionally scoped by a selection. Returns PNG bytes and/or the editable source via explicit output paths or embedded artifacts; no force, mkdir, or in-place writes.
No parameter schema on file.
Detect or eliminate isolated, noise, or outlier pixels in a raster image or .mcpx source, optionally scoped by a selection. Returns PNG bytes and/or the editable source via explicit output paths or embedded artifacts; no force, mkdir, or in-place writes.
No parameter schema on file.
Run the palette extract or inspect subcommand over an image and return a read-only report of unique colors, distribution, roles, or contrast. Reads only, never writes.
No parameter schema on file.
Run the material list or show subcommand and return a read-only report of builtin material definitions or one material
No parameter schema on file.
Analyze seams, edge repetition, and brightness continuity of a tileable image, with an optional tiled preview grid. Reads the input and returns a report, or writes a preview PNG only to the explicit output path; never invents filenames.
No parameter schema on file.
Generate a deterministic procedural texture from a named pattern, size, palette, and seed. Returns PNG bytes and/or the editable .mcpx source via explicit output paths or embedded artifacts; no force, mkdir, or in-place writes.
No parameter schema on file.
Preview an image in ascii, palette-map, scale, or nine-slice mode. Read-only except scale and nine-slice, which may write a PNG only to the explicit output path; never invents filenames.
No parameter schema on file.
No parameter schema on file.
Scan a resource pack root for namespace, model, texture, and atlas integrity and return a read-only verdict with findings. Reads only, never writes.
No parameter schema on file.
Scale a GUI sprite to N or WxH with the mcmeta stretch/tile/nine_slice mapping. Returns PNG bytes and/or the scaled PNG via an explicit output path; never invents filenames.
No parameter schema on file.
- 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 mc-asset — Minecraft Pixel Asset Engine 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 | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| 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.
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, 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. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
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.2. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
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 mc-asset — Minecraft Pixel Asset Engine 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.