Is Pyxel MCP safe to use?

Pyxel MCP has an HVTrust score of 48.8/100 (Grade D), ranked #937 of 1328 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Pyxel MCP?

Pyxel MCP scores 48.8/100 on HVTracker's evidence-weighted HVTrust scale. It has 26 GitHub stars and is categorized under MCP Servers.

Pyxel MCP

kitao/pyxel-mcp

MCP server for AI-assisted retro game development with Pyxel

MCP Servers Python Grade D Listed MIT

48.8/100

Rank #937 of 1328

Compare Pyxel MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade B · 3/5 signals

Last push

2026-07-15 · 55d ago

Recent change

Rank +7

Is Pyxel MCP safe? Pyxel MCP scores 48.8/100 (Grade D), ranked #937 of 1328 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.4/10; recent commits are unsigned; last pushed 2026-07-15. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#536 MCP Zenml — 48.9 (D) → #537 Weather MCP Server — 48.9 (D) → #539 Google/Meta Ads + GA4 MCP — 48.8 (D) → #540 Dbmcp — 48.7 (D) →

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-09-08

Rank Moved

Rank dropped 19 spots (#918 → #937)

2026-09-07

Rank Moved

Rank dropped 38 spots (#880 → #918)

2026-09-06

Rank Moved

Rank dropped 14 spots (#866 → #880)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 4.4/10. Tighten the weakest checks to improve public safety evidence.

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

Refresh maintenance signals The repo was last pushed 55 days ago. Fresh activity helps separate stable projects from stale ones.

Compare with another agent Get email alerts for Pyxel MCP View MCP Servers Report missing data

28.8

Activity sub-score · out of 100

#538

In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-08-11 2026-09-08

Activity & Reach

Stars

Forks

Last Push

2026-07-15

55 days ago

Commits (4 wk)

Downloads (7d)

pypi

HN mentions (30d)

—

Open Issues

Rank Change

▼19

was #918

Analysis

HVTrust Dimensions vs MCP Servers

48.8 / 100 · 100.0% confidence

Pyxel MCP MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

5.5 / 25

4.4 below avg 9.9

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.6 below avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

12.2 / 17

in line with avg 12.0

Maintenance60% last-push freshness · 40% commit activity

8.3 / 20

3.9 below avg 12.2

AdoptionLog-scaled stars · package downloads

6.0 / 20

0.9 below avg 6.9

Activity Inputs

28.8 / 100

StarsRepository reach

8.6 / 30

FreshnessLast push recency

17.4 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

2.8 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

4.4 / 10

OpenSSF Scorecard · scanned Aug 31, 2026

Signed Commits

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests -1

CII-Best-Practices 0

Code-Review 0

Contributors 0

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging -1

Pinned-Dependencies 0

SAST 0

Security-Policy 10

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 10

Is Pyxel MCP safe?

Public trust evidence for Pyxel MCP is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.

Does Pyxel MCP publish package provenance?

No published build provenance is currently detected for Pyxel MCP. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does Pyxel MCP have an OpenSSF Scorecard?

Pyxel MCP has an OpenSSF Scorecard score of 4.4/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.

Is Pyxel MCP actively maintained?

Slowing down. Last push was 55 days ago — keep an eye on whether activity resumes.

What license does Pyxel MCP use?

Pyxel MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Pyxel MCP's commits signed?

0% of the last 100 commits to Pyxel MCP are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface

Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support

medium confidence

Implemented

Pyxel MCP appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

None detected

No clear third-party provider dependency detected.

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

None detected

No clear plugin system or broad tool surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

high confidence

Match

Published package metadata matches the tracked repo

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

Maintain Pyxel MCP?

For maintainers

HVTrust scores Pyxel MCP from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-09-08

Rank Moved

Rank dropped 19 spots (#918 → #937)

2026-09-07

Rank Moved

Rank dropped 38 spots (#880 → #918)

2026-09-06

Rank Moved

Rank dropped 14 spots (#866 → #880)

2026-09-05

Rank Moved

Rank dropped 58 spots (#808 → #866)

2026-09-04

Rank Moved

Rank dropped 36 spots (#772 → #808)

2026-09-03

Rank Moved

Rank dropped 41 spots (#731 → #772)

2026-09-02

Rank Moved

Rank dropped 35 spots (#696 → #731)

2026-09-01

Rank Moved

Rank dropped 29 spots (#667 → #696)

2026-08-31

Scorecard Added

OSSF Scorecard: 4.4/10

2026-08-31

Rank Moved

Rank rose 405 spots (#1072 → #667)

2026-08-31

HVTrust Changed

HVTrust up 20.6pts (28.8 → 49.4)

2026-08-30

Rank Moved

Rank dropped 55 spots (#1017 → #1072)

2026-08-29

Rank Moved

Rank dropped 52 spots (#965 → #1017)

2026-08-28

Rank Moved

Rank dropped 35 spots (#930 → #965)

2026-08-27

Rank Moved

Rank dropped 25 spots (#905 → #930)

2026-08-26

Rank Moved

Rank dropped 113 spots (#792 → #905)

2026-08-16

Rank Moved

Rank dropped 15 spots (#773 → #788)

2026-08-14

Rank Moved

Rank dropped 16 spots (#756 → #772)

2026-08-14

Activity Score Changed

Activity score down 6pts (39 → 33)

2026-08-10

Rank Moved

Rank dropped 40 spots (#717 → #757)

2026-08-09

Activity Score Changed

Activity score down 10pts (49 → 39)

2026-08-08

Newly Listed

First tracked at rank #689

GitHub → PyPI: pyxel-mcp

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/pyxel-mcp.svg)](https://hvtracker.net/agents/pyxel-mcp)
            
HTML:
            <a href="https://hvtracker.net/agents/pyxel-mcp"><img src="https://hvtracker.net/badge/pyxel-mcp.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON