Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.Ricky610329/mup

NPM · MUP-MCP-SERVER · SCANNED SEP 25

MCP server that turns HTML MUP panels into interactive UI tools for LLMs.

Available components

npm · mup-mcp-server 78
0 this week 78 Trust /100
Trust breakdown (7 categories)

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 Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability54
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 399 tokens (~399/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
  • Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the io.github.Ricky610329/mup MCP server?

io.github.Ricky610329/mup runs locally as an npm package, launched with npx -y mup-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · mup-mcp-server

# add to Claude Code
claude mcp add ricky610329-mup -- npx -y mup-mcp-server
// .cursor/mcp.json
{
  "mcpServers": {
    "ricky610329-mup": {
      "command": "npx",
      "args": [
        "-y",
        "mup-mcp-server"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "ricky610329-mup": {
      "command": "npx",
      "args": [
        "-y",
        "mup-mcp-server"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add ricky610329-mup -- npx -y mup-mcp-server
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ricky610329-mup": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "mup-mcp-server"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add ricky610329-mup --command npx --arg -y --arg mup-mcp-server
# ~/.hermes/config.yaml
mcp_servers:
  ricky610329-mup:
    command: "npx"
    args: ["-y", "mup-mcp-server"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "ricky610329-mup": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "mup-mcp-server"
      ]
    }
  }
}
# add to Vellum
assistant mcp add ricky610329-mup -t stdio -c npx -a -y mup-mcp-server
// mcp.json
{
  "mcpServers": {
    "ricky610329-mup": {
      "command": "npx",
      "args": [
        "-y",
        "mup-mcp-server"
      ]
    }
  }
}
Changelog

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.

  • 25 Sept 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 24 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 23 Sept 26 0
    • Stability: 0.97 → pass security
    • Security disclosure: unverified → fail ▼ functional
  • 22 Sept 26 +1
    • Security disclosure: fail → unverified ▼ functional
  • 20 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.

  • 18 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.

  • 17 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 16 Sept 26 0
    • Stability: 0.97 → pass security
Diagnostics

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 25 Sept 2026 · Analysed npm/mup-mcp-server@0.1.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 96 packages
Packages resolved 96
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 1 exposed · ~399 tokens

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 →

Tool Tokens
mup ~399

MUP — Interactive UI panels in browser at http://localhost:3200. Auto-activated on first use. Call: { "mupId": "...", "functionName": "...", "functionArgs": { ... } } Actions: checkInteractions, save, load, workspaces, list, history, pipe

NameTypeReqDescription
actionstring–"checkInteractions" to check user UI activity, "list" to list MUPs, "pipe" to manage data pipes. Omit when calling a function.
debounceMsnumber–Debounce interval in ms (default 500).
descriptionstring–Workspace description — what you're working on. Used with save action.
functionArgsobject–Arguments for the function. Can be a JSON object or JSON string.
functionNamestring–Function to call (e.g. makeMove, renderChart, setPixels)
mupIdstring–MUP ID (e.g. mup-chess, mup-chart). Auto-activated on first use.
namestring–Workspace name for save/load/deleteWorkspace actions.
pipeIdstring–Pipe ID for delete/enable/disable.
sincenumber–Unix timestamp (ms). Only return interactions after this time. Used with checkInteractions.
sourceFunctionstring–Optional: call this function on source to get data (else uses stateData).
sourceMupIdstring–Pipe source MUP ID.
subActionstring–For pipe action: "create", "list", "delete", "enable", "disable"
targetFunctionstring–Function to call on target MUP.
targetMupIdstring–Pipe target MUP ID.
transformobject–Key mapping: { targetArgName: "source.path" }. Use "." for entire data, "'literal'" for strings.

No output schema declared.

No examples provided.

Common questions

What is the io.github.Ricky610329/mup MCP server?

io.github.Ricky610329/mup is an MCP server listed in the public MCP registry as io.github.Ricky610329/mup. MCP server that turns HTML MUP panels into interactive UI tools for LLMs. This page covers its npm package (mup-mcp-server).

Is the io.github.Ricky610329/mup MCP server safe to use?

io.github.Ricky610329/mup scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 2026. It declares no install or post-install scripts. 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 io.github.Ricky610329/mup MCP server expose?

io.github.Ricky610329/mup exposes 1 tool: mup. Their descriptions and schemas cost roughly 399 tokens of context every time the server is loaded.

Is the io.github.Ricky610329/mup MCP server still maintained?

io.github.Ricky610329/mup is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.Ricky610329/mup MCP server under?

io.github.Ricky610329/mup declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.