mcpbeat Sign in

Voyager Commerce MCP Server

by blathrop07 Your server? Claim it
not responding

Voyager Commerce is listed as active in the registry but did not answer our last check.

AI ticket commerce for theme parks, zoos, museums, and aquariums via any AI agent

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 51 days of history · worst day 0%
51 days agonow
0.0%
Uptime 24h
0 of 91 checks
Tools
hidden behind auth
573 ms
Response time
average over 24h
open, no key
Access
streamable-http

Voyager Commerce does not always answer

Over the last week it answered 0.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 6 min ago.

run in your terminal
claude mcp add voyager-commerce --transport http https://review-002-voyager-ai-commerce.zeus.gatewayticketing.hosting/mcp?storefrontId=9e55112e-b1c9-4f8f-8531-e9aed2158066
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "voyager-commerce": {
      "url": "https://review-002-voyager-ai-commerce.zeus.gatewayticketing.hosting/mcp?storefrontId=9e55112e-b1c9-4f8f-8531-e9aed2158066"
    }
  }
}
~/.codex/config.toml
[mcp_servers.voyager-commerce]
url = "https://review-002-voyager-ai-commerce.zeus.gatewayticketing.hosting/mcp?storefrontId=9e55112e-b1c9-4f8f-8531-e9aed2158066"
.cursor/mcp.json
{
  "mcpServers": {
    "voyager-commerce": {
      "url": "https://review-002-voyager-ai-commerce.zeus.gatewayticketing.hosting/mcp?storefrontId=9e55112e-b1c9-4f8f-8531-e9aed2158066"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "voyager-commerce": {
      "url": "https://review-002-voyager-ai-commerce.zeus.gatewayticketing.hosting/mcp?storefrontId=9e55112e-b1c9-4f8f-8531-e9aed2158066"
    }
  }
}

Endpoints

URLTransportStateLatencyChecked
https://review-002-voyager-ai-commerce.zeus.gatewayticketing.hosting/mcp?storefrontId=9e55112e-b1c9-4f8f-8531-e9aed2158066 streamable-http answering 573 ms 6 min ago

Alternatives to Voyager Commerce

same job, measured the same way
Tickscope
by seungdori

Real-time, free crypto market data for any AI agent — via MCP.

75 installs/wk local only
UnClick
by malamutemayhem

AI agent tool marketplace. 60+ tools for social, e-commerce, accounting, and messaging.

238 installs/wk local only
Trust Gate
by botagram

Merchant trust verification for agentic commerce. Verify any merchant before autonomous payment.

19 installs/wk local only
x402-market
by asaishota

Let AI agents pay-per-call for any HTTP API via x402 on Base mainnet. One tool: pay_and_call.

36 installs/wk local only
Freshdesk
by pipeworx-io

Freshdesk MCP Pack — helpdesk ticket and contact management via Freshdesk API v2.

40 tools answering
Facet UCP Shopping
by facet

The independent agent-commerce protocol for AI-agent checkout on any online store.

23 tools answering
Zendesk MCP
by markusvankempen

Zendesk MCP: 14 tools for AI agents — create, search, assign, comment, and close support tickets.

100 installs/wk local only
Crystallize MCP
by hayodev

Crystallize headless commerce tools for AI agents via Model Context Protocol

47 installs/wk local only

Voyager Commerce — questions

Answers built from our own checks of this server.

Is Voyager Commerce working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 91 checks got a reply (0.0%), average response time 573 ms. The bar chart above shows every period we have measured.
Is Voyager Commerce still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
The registry lists Voyager Commerce as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Voyager Commerce?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Voyager Commerce need an API key?
No. Voyager Commerce completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. This is what we observed, not what the docs claim.