ZX84 (damieng-zx/zx84) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it: we have no way to read this server ourselves. No publisher has claimed this listing.

C
Emerging
74/100
13 days ago

ZX84

An MCP server providing a ZX Spectrum emulator for AI testing, enabling loading and running of Spectrum software with debugging, display, and audio features.

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

damieng-zx

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
⚠️
Known vulnerabilities in dependencies: 3 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
// known CVEs in dependencies3 high5 medium5 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

highsolid-js@1.9.0GHSA-3qxh-p7jc-5xh6

Solid Lacks Escaping of HTML in JSX Fragments allows for Cross-Site Scripting (XSS)

highvite@6.1.0GHSA-fx2h-pf6j-xcff

vite: `server.fs.deny` bypass on Windows alternate paths

highvite@6.1.0GHSA-p9ff-h696-f583

Vite Vulnerable to Arbitrary File Read via Vite Dev Server WebSocket

mediumvite@6.1.0GHSA-356w-63v5-8wf4

Vite has an `server.fs.deny` bypass with an invalid `request-target`

mediumvite@6.1.0GHSA-4w7w-66w2-5vf9

Vite Vulnerable to Path Traversal in Optimized Deps `.map` Handling

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

52/52 tools missing one or more hints — breakpoint (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); delete_breakpoint (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); port_watchpoint (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +49 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool inputs are validated

48/52 tool handlers declare input schemas (92%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool test coverage

29/52 tools referenced in tests (56%)

Write tests that reference each tool by name so every tool has at least one test.

Dev dependencies

3 critical/high in dev-only deps (does not ship to users)

Upgrade dev dependencies when convenient.

Tool description accuracy

screenshot: description implies read-only but handler writes/deletes/executes; stop_trace: description implies read-only but handler writes/deletes/executes

Update tool descriptions to accurately reflect all capabilities — especially write, delete, or execute operations.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 6 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/damieng-zx84-wilp0b)](https://m8ven.ai/mcp/damieng-zx84-wilp0b)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 465ec579beda4d6081fe5f1649d8b78d5359d904
code hash: f4097453f0c5345a1245349e7f225405bdba31e56c8feaeaf30ca7e87ae783c9
verified: 8/16/2026, 5:49:11 PM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client