travelMCP Directory MCP server
Checked 2026-09-07. Alive: no. Handshake: verified.
Category: commerce-retail. API and field schema.
Facts
| id | registry--ai.omnitravel--travelmcp-directory |
| name | travelMCP Directory |
| registry_name | ai.omnitravel/travelmcp-directory |
| repo_url | not available |
| endpoint_url | https://omnitravel.ai/mcp |
| transport | streamable-http |
| alive | no |
| liveness_reason | stale |
| check_reachable | yes |
| check_recent_commit | no |
| check_installable | yes |
| handshake_status | verified |
| handshake_checked_at | 2026-09-07T18:13:05Z |
| handshake_protocol_version | 2025-06-18 |
| handshake_auth_hint | not available |
| handshake_auth_discoverable | not available |
| handshake_failure_layer | none |
| handshake_latency_ms | 1489 |
| handshake_tools_state | listed |
| handshake_tool_count | 3 |
| maintenance_status | unknown |
| last_commit_at | not available |
| category | commerce-retail |
| license_spdx | not available |
How to install or connect
Connect your MCP client to https://omnitravel.ai/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.