io.github.taygunsavas/patina-unity-mcp
Patina Unity MCP
Is the Patina Unity MCP server down? Yes. It has given no valid answer since 2026-10-16: not found.
Control the Unity Editor from MCP hosts through a local Rust server and C# Unity bridge.
not found down since 2026-10-16 · probed 2026-11-15 · unchanged since 2026-10-30
npm error notarget In most cases you or one of your dependencies are requesting npm error notarget a package version that doesn't exist. npm error A complete lo
- Run it
- npx -y com.taygunsavas.patina-unity-mcp@1.2.2 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Repository
- https://github.com/taygunsavas/patina-unity-mcp
- Registry
- active, updated 2026-10-12 · registry entry
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- io.github.tathagat22/plumb-mcp · alive
- io.github.taurgis/sfcc-dev-mcp · alive
- io.github.tavily-ai/tavily-mcp · alive
- io.github.taybenlor/runno · alive
- io.github.taytrom/bitsbound-contract-automation · crashed on start
- Forbiz io.github.tbernabo/forbiz-mcp · alive
- io.github.tcehjaava/tmdb-mcp-server · alive
- io.github.tci-nebula/mermaid-render-mcp · alive
Servers that mention patina or unity.
- Patina io.github.ramakrishnanhulk20/patina · alive
- Patina io.github.taxmanhaven/patina · alive
- Clarid HMDA Validator ai.clarid/hmda · needs auth
- ai.getvda/llm-observability-orchestration-agent-langchain-community · newer protocol
- Perlucem TBPI — Bank Performance Intelligence ai.perlucem/tbpi · needs auth
- Pozeidon ai.pozeidon/pozeidon · needs auth
- ai.tellas.bip/tellas-bip · needs auth
- HoodEx app.hoodex/hoodex · 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
- No valid answer since 2026-10-16, in every probe since then.
- The endpoint answers HTTP 404. The registry entry points to a URL that is not an MCP endpoint any more. Publish a new version of the registry entry with the current URL.