Pyxel MCP
PYPI · PYXEL-MCP · SCANNED SEP 20
MCP server for Pyxel, a retro game engine for Python
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 Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 1 of 32 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency35
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 6 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability81
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1042 tokens (~94/item across 11 items; 8 tools + 3 resources), lean.Pass
- 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 Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the Pyxel MCP server?
Pyxel MCP runs locally as a PyPI package, launched with uvx pyxel-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · pyxel-mcp
claude mcp add kitao-pyxel-mcp -- uvx pyxel-mcp
{
"mcpServers": {
"kitao-pyxel-mcp": {
"command": "uvx",
"args": [
"pyxel-mcp"
]
}
}
} {
"servers": {
"kitao-pyxel-mcp": {
"command": "uvx",
"args": [
"pyxel-mcp"
]
}
}
} codex mcp add kitao-pyxel-mcp -- uvx pyxel-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"kitao-pyxel-mcp": {
"type": "local",
"command": [
"uvx",
"pyxel-mcp"
],
"enabled": true
}
}
} openclaw mcp add kitao-pyxel-mcp --command uvx --arg pyxel-mcp
mcp_servers:
kitao-pyxel-mcp:
command: "uvx"
args: ["pyxel-mcp"] {
"McpServers": {
"kitao-pyxel-mcp": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"pyxel-mcp"
]
}
}
} assistant mcp add kitao-pyxel-mcp -t stdio -c uvx -a pyxel-mcp
{
"mcpServers": {
"kitao-pyxel-mcp": {
"command": "uvx",
"args": [
"pyxel-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.
- 19 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.
- 18 Sept 26 −3
- Stability: pass → 0.80 functional
- 17 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- Stability: 0.97 → pass security
- 16 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- 14 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.
- 13 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- Schema quality: 80 → 94 ▼ functional
- MCP protocol: Implements a current MCP spec version (2026-07-28). functional
- Package version: 1.2.0 → 1.3.0 functional
- 12 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.
- 11 Sept 26 +12
- Malware scan: unverified → pass ▲ security
- 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 20 Sept 2026 · Analysed pypi/pyxel-mcp@1.3.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 32 packages
| Packages resolved | 32 |
|---|---|
| No linked repository | 1 |
| 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 →
diff_frames ~39
Compare two PNG frames pixel by pixel and return their changed region and ratio.
| Name | Type | Req | Description |
|---|---|---|---|
| frame_a | string | yes | – |
| frame_b | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| changed_pixels | – | – | – |
| errors | array | yes | – |
| identical | – | – | – |
| ok | boolean | yes | – |
| ratio | – | – | – |
| region | – | – | – |
| size_a | – | – | – |
| size_b | – | – | – |
| size_match | – | – | – |
| total_pixels | – | – | – |
| warnings | array | – | – |
No examples provided.
pyxel_info ~24
Report installed versions, paths, examples, and Pyxel resource URIs.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| errors | array | yes | – |
| examples | array | – | – |
| ok | boolean | yes | – |
| python_version | – | – | – |
| pyxel_mcp_version | – | – | – |
| pyxel_version | – | – | – |
| resources | object | – | – |
| stubs_path | – | – | – |
No examples provided.
read_audio ~44
Render one Pyxel sound or music slot to WAV and return measurable audio data.
| Name | Type | Req | Description |
|---|---|---|---|
| output_path | string | yes | – |
| script | string | yes | – |
| target | – | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| channels | – | – | – |
| duration_seconds | – | – | – |
| errors | array | yes | – |
| notes | array | – | – |
| ok | boolean | yes | – |
| path | – | – | – |
| peak_amplitude | – | – | – |
| sample_rate | – | – | – |
| warnings | array | – | – |
No examples provided.
read_image ~91
Read palette-index pixels from a Pyxel image-bank region and optionally render it to PNG; inline=true returns the render as image content and makes render_path optional.
| Name | Type | Req | Description |
|---|---|---|---|
| h | – | – | – |
| image | integer | yes | – |
| inline | boolean | – | – |
| render_path | – | – | – |
| script | string | yes | – |
| w | – | – | – |
| x | integer | – | – |
| y | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| bank_size | – | – | – |
| color_count | object | – | – |
| errors | array | yes | – |
| image_index | – | – | – |
| ok | boolean | yes | – |
| pixels | – | – | – |
| region | – | – | – |
| rendered | – | – | – |
No examples provided.
read_palette ~30
Read the active Pyxel palette and the palette indices used by image banks.
| Name | Type | Req | Description |
|---|---|---|---|
| script | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| colors | object | – | – |
| errors | array | yes | – |
| extended_palette | – | – | – |
| ok | boolean | yes | – |
| palette_size | – | – | – |
| used_indices | array | – | – |
No examples provided.
read_tilemap ~69
Read Pyxel tile coordinates, usage, bounds, source bank, and optional rendered output; inline=true returns the render as image content and makes render_path optional.
| Name | Type | Req | Description |
|---|---|---|---|
| inline | boolean | – | – |
| render_path | – | – | – |
| script | string | yes | – |
| tilemap | integer | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| errors | array | yes | – |
| imgsrc | – | – | – |
| ok | boolean | yes | – |
| region | – | – | – |
| rendered | – | – | – |
| size | – | – | – |
| tilemap_index | – | – | – |
| tiles | – | – | – |
| usage | object | – | – |
| zero_tile_nonempty | – | – | – |
| zero_tile_used | – | – | – |
No examples provided.
run ~110
Run a Pyxel script headlessly for a frame budget or until a condition holds, with scheduled input and state, screen, or video capture. screen_image snapshots with inline=true also return the PNG as image content, and a single inline frame may omit its output path.
| Name | Type | Req | Description |
|---|---|---|---|
| frames | integer | yes | – |
| inputs | – | – | – |
| random_seed | – | – | – |
| script | string | yes | – |
| snapshots | – | – | – |
| stall_window_frames | – | – | – |
| timeout | integer | – | – |
| until | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| elapsed_seconds | number | yes | – |
| errors | array | yes | – |
| exit_status | string | yes | – |
| frame_count | integer | yes | – |
| log | string | yes | – |
| ok | boolean | yes | – |
| seeded | boolean | yes | – |
| snapshots | array | yes | – |
| until_met | – | – | True once `until` held, False when it was evaluated without ever holding, None when it was never evaluated. |
No examples provided.
validate ~25
Check Python syntax and report recognizable Pyxel code patterns.
| Name | Type | Req | Description |
|---|---|---|---|
| script | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| errors | array | yes | – |
| issues | array | – | – |
| ok | boolean | yes | – |
No examples provided.
What is the Pyxel MCP server?
Pyxel MCP is listed in the public MCP registry as io.github.kitao/pyxel-mcp. MCP server for Pyxel, a retro game engine for Python. This page covers its PyPI package (pyxel-mcp).
Is the Pyxel MCP server safe to use?
Pyxel MCP scores 64 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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 Pyxel MCP server expose?
Pyxel MCP exposes 8 tools: run, validate, pyxel_info, read_palette, read_image, and 3 more. Their descriptions and schemas cost roughly 432 tokens of context every time the server is loaded.
Is the Pyxel MCP server still maintained?
Pyxel MCP is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.