mcpbeat Sign in

CatalogEngine MCP Server

answering

CatalogEngine is answering right now. Last checked 3 min ago.

E-commerce inventory and catalog data structuring tool.

Uptime history 47 days of history · worst day 99%
47 days agonow
100.0%
Uptime 24h
92 of 92 checks
Tools
hidden behind auth
91 ms
Response time
average over 24h
authentication required
Access
sse

Nothing serious here today

Today is the operative word: we check CatalogEngine every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

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 3 min ago.

run in your terminal
claude mcp add catalog-engine --transport http https://catalog-engine-mcp.vercel.app/api/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "catalog-engine": {
      "url": "https://catalog-engine-mcp.vercel.app/api/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.catalog-engine]
url = "https://catalog-engine-mcp.vercel.app/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "catalog-engine": {
      "url": "https://catalog-engine-mcp.vercel.app/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "catalog-engine": {
      "url": "https://catalog-engine-mcp.vercel.app/api/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but it did not say what kind of credentials it expects.

Endpoints

URLTransportStateLatencyChecked
https://catalog-engine-mcp.vercel.app/api/mcp sse needs auth 91 ms 3 min ago

Alternatives to CatalogEngine

same job, measured the same way
Shopops MCP
by enzoemir1

AI e-commerce operations. Inventory, pricing, segmentation, and analytics.

32 installs/wk local only
A
Ordercore MCP
by ordercore

Commerce backend for AI agents: catalog, prices, inventory, orders, idempotent checkout.

47 installs/wk local only
I
Ecommerce Command Center
by atul0016

Daily ecommerce revenue, inventory, listing, shipping, and restock operations intelligence.

57 installs/wk local only
MCP Vtex
by codespar

MCP server for VTEX — e-commerce, orders, products, inventory, shipping

26 installs/wk local only
zobrx
by zobrx

Read-only zobrx e-commerce data: P&L, orders, inventory, marketplace, tax & shelf insights.

58 tools answering
Presso
by presso

Connect e-commerce and marketing data to AI assistants via MCP.

answering
HasData
by hasdata

All HasData scraping tools in one MCP server: Google, TikTok, Instagram, maps, e-commerce and more.

answering
VibeCart
by runjohnray2-lgtm

Agent-native commerce with trusted catalog, durable carts, and Stripe Checkout via MCP and UCP.

4 tools answering

CatalogEngine — questions

Answers built from our own checks of this server.

Why is there no tool list for CatalogEngine?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is CatalogEngine working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 91 ms. The bar chart above shows every period we have measured.
How do I connect CatalogEngine?
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. You will need your own credentials: it refuses anonymous clients.
Does CatalogEngine need an API key?
Yes. Every time we knock, CatalogEngine answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is CatalogEngine?
It answers our handshake in 91 ms on average, which is faster than 84% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.