mcpbeat Sign in

Resy MCP Server

by resy Your server? Claim it
answering

Resy is answering right now. Last checked moments ago.

Uptime history 52 days of history · worst day 99%
52 days agonow
98.9%
Uptime 24h
91 of 92 checks
—
Tools
hidden behind auth
995 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Resy missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of 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 0 min ago.

run in your terminal
claude mcp add mcp --transport http https://apigw.americanexpress.com/dining/v1/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://apigw.americanexpress.com/dining/v1/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.mcp]
url = "https://apigw.americanexpress.com/dining/v1/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://apigw.americanexpress.com/dining/v1/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://apigw.americanexpress.com/dining/v1/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://apigw.americanexpress.com/dining/v1/mcp streamable-http sign-in 965 ms 0 min ago

Alternatives to Resy

same job, measured the same way
Remit MCP
by gabrielmahia

💸 remit-mcp

90 installs/wk local only

Resy — questions

Answers built from our own checks of this server.

Why is there no tool list for Resy?
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: 98.9% of checks in the last 24 hours got a reply.
Is Resy working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 92 checks got a reply (98.9%), average response time 995 ms. The bar chart above shows every period we have measured.
How do I connect Resy?
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 sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to Resy?
No API key is involved. Resy answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is Resy?
It answers our handshake in 995 ms on average, which is faster than 10% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.