B-

npm:c64bridge

https://www.npmjs.com/package/c64bridge
80/100 · MCP Trust Grade · checked 2h ago · MCP 0.9.2

What it offers — 24 tools · Developer Tools

sid_volume
sid_reset
sid_note_on
sid_note_off
sid_silence_all
Silence
sidplay_file
modplay_file
music_generate
music_compile_and_play
record_and_analyze_audio
analyze_audio
c64_debug
config_list
config_get
config_set
config_batch_update
config_load_from_flash

+6 more tools

Spec / packaging20%100
Security (OWASP MCP)30%70
Maintenance / popularity20%100
Tool hygiene15%70
Transparency / provenance15%55

Findings

INFO Static analysis of npm package c64bridge@0.9.2 (stdio server — no remote endpoint). Reliability/behavioral signals require running it; not measured.
Grade another server

We re-grade npm:c64bridge on a schedule and alert your Slack/webhook the moment its tools change or its grade drops — rug-pull insurance for the connection.

Share this report card

A 1200×630 card with the grade + audit — drop it in a post, Slack, or your repo.

MCP Trust report card — npm:c64bridge grade B-
Share on X Open card image

Embed this grade

A live badge — it re-verifies itself and shows current stability. Static scorecards can't. Paste it in your README or site to show users you're independently audited.

MCP Trust Grade B- · wmcp.sh
[![MCP Trust Grade B-](https://wmcp.sh/mcp/grade/npm%3Ac64bridge/badge.svg)](https://wmcp.sh/mcp/grade/npm%3Ac64bridge)
<a href="https://wmcp.sh/mcp/grade/npm%3Ac64bridge"><img src="https://wmcp.sh/mcp/grade/npm%3Ac64bridge/badge.svg" alt="MCP Trust Grade B- · wmcp.sh"></a>

Agents: check this before connecting

Add the wmcp.sh trust oracle as an MCP server and call grade_mcp_server / check_mcp_drift in your agent's pre-connection gate:

https://wmcp.sh/mcp/trust
How this grade is computed. An open, independent rubric — Spec conformance (20%), Security mapped to the OWASP MCP Top 10 (30%), Reliability (20%), Tool hygiene (15%), Transparency (15%) — run by connecting to the server and inspecting its real MCP surface. The grade is free and identical whether or not the operator pays. v1 uses static + spec signals from a single connection; continuous uptime, real latency, and annotation-truthing (declared readOnly vs observed behavior) layer on via the wmcp.sh proxy.