io.github.KshKnsl/rive-vscode-mcp
Rive VS Code MCP
Is the Rive VS Code MCP server down? No. It is up and needs env, probed 2026-11-09.
Inspect Rive files for artboards, animations, state machines, and inputs.
needs env probed 2026-11-15 · unchanged since 2026-11-09
MCP error -32000: Connection closed Error: ENOENT: no such file or directory, realpath 'mcpcost-placeholder' syscall: 'realpath', path: 'mcpcost-placeholder
- Run it
- npx -y rive-vscode-mcp-server@1.0.15 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Repository
- https://github.com/KshKnsl/rive-vscode-mcp
- Registry
- active, updated 2026-11-09 · registry entry
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- Webhook Crash Lab io.github.Krrishkumar125/webhook-crash-lab-mcp · alive
- io.github.KryptosAI/agent-observability · timeout
- io.github.KryptosAI/mcp-observatory · crashed on start
- io.github.KryptosAI/mcp-seatbelt · crashed on start
- Tripwire Guard — evidence-first injection scanner io.github.KubaOpoczka/tripwire-guard · alive
- io.github.Kumar2421/marlo-mcp · alive
- context-doctor io.github.KushalP1/context-doctor · alive
- io.github.KuvopLLC/better-bear · alive
Servers that mention vscode.
- Pleasanter MCP io.github.Implem/pleasanter-mcp · needs your URL
- io.github.estruyf/vscode-demo-time · alive
- io.github.Intina47/context-sync · crashed on start
- io.github.jmshinhwa/gnu-global-cpp-vscode-config-pack · alive
- io.github.sirlordt/vscode-terminal-mcp · no executable
- io.github.jmshinhwa/mcp-config-guard · alive
- MCP VS Code io.github.mario-andreschak/mcp-vscode · needs args
- Hydracept com.hydracept/vscode · needs auth
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server exits because an environment variable is missing. The probe starts the package without secrets. A server that starts without secrets and asks for them on the first tool call is measured.