Twinmotion MCP MCP server
Checked 2026-09-07. Alive: no. Handshake: verified.
Category: media-design. API and field schema.
Facts
| id | registry--io.scanbimlabs--twinmotion-mcp |
| name | Twinmotion MCP |
| registry_name | io.scanbimlabs/twinmotion-mcp |
| repo_url | not available |
| endpoint_url | https://twinmotion-mcp.itmartin24.workers.dev/mcp |
| transport | streamable-http |
| alive | no |
| liveness_reason | unreachable |
| check_reachable | no |
| check_recent_commit | no |
| check_installable | not verifiable |
| handshake_status | verified |
| handshake_checked_at | 2026-09-07T18:54:29Z |
| handshake_protocol_version | 2024-11-05 |
| handshake_auth_hint | not available |
| handshake_auth_discoverable | not available |
| handshake_failure_layer | none |
| handshake_latency_ms | 998 |
| handshake_tools_state | listed |
| handshake_tool_count | 5 |
| maintenance_status | unknown |
| last_commit_at | not available |
| category | media-design |
| license_spdx | not available |
How to install or connect
Connect your MCP client to https://twinmotion-mcp.itmartin24.workers.dev/mcp.
What the checks mean
alive combines the applicable repository, package, and endpoint checks. A null result is not verifiable, not a failure. The MCP handshake is a separate structural probe and is not a security audit. Read the methodology.