Twilize MCP server
Checked 2026-09-07. Alive: no. Handshake: unknown.
Category: communication. API and field schema.
Facts
| id | subhatta123--twilize |
| name | Twilize |
| registry_name | io.github.subhatta123/twilize |
| repo_url | https://github.com/subhatta123/twilize |
| endpoint_url | https://web-production-dcbcb.up.railway.app/mcp |
| transport | mixed |
| alive | no |
| liveness_reason | unreachable |
| check_reachable | no |
| check_recent_commit | no |
| check_installable | not verifiable |
| handshake_status | unknown |
| handshake_checked_at | 2026-09-07T18:59:36Z |
| handshake_protocol_version | not available |
| handshake_auth_hint | http:405 |
| handshake_auth_discoverable | not available |
| handshake_failure_layer | http |
| handshake_latency_ms | 1038 |
| handshake_tools_state | not available |
| handshake_tool_count | not available |
| maintenance_status | unknown |
| last_commit_at | not available |
| category | communication |
| license_spdx | not available |
How to install or connect
Connect your MCP client to https://web-production-dcbcb.up.railway.app/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.