Gastrosync MCP Server

by yschaub Your server? Claim it

answering

Gastrosync is answering right now. Last checked 15 min ago.

Connect AI assistants to Gastrosync for catering and event management.

Uptime history 11 days of history · worst day 99%

11 days agonow

100.0%

Uptime 24h

91 of 91 checks

—

Tools

hidden behind auth

304 ms

Response time

average over 24h

OAuth sign-in

Access

streamable-http

Nothing serious here today

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

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add gastrosync --transport http https://gastrosync.com/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "gastrosync": {
      "url": "https://gastrosync.com/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.gastrosync]
url = "https://gastrosync.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "gastrosync": {
      "url": "https://gastrosync.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "gastrosync": {
      "url": "https://gastrosync.com/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

URL	Transport	State	Latency	Checked
https://gastrosync.com/mcp	streamable-http	sign-in	423 ms	15 min ago

Alternatives to Gastrosync

same job, measured the same way

Outline MCP Server

by vortiago

Connect AI assistants to Outline for document search, reading, and management

701 installs/wk local only

Qualy

by qualyhq

Connect your AI assistant to Qualy to manage payments, billing, and contacts.

answering

Contextlayer MCP

by autoblocks

Personal context management for AI assistants

47 installs/wk local only

Ctxl

by autoblocks

Personal context management for AI assistants

43 installs/wk local only

Ctxl MCP

by autoblocks

Personal context management for AI assistants

42 installs/wk local only

Hiveclaw

by omiiyamu

Connect AI assistants to HiveClaw — manage projects, talk to AI agents, and more.

13 installs/wk answering

Testrail MCP Server

by uarlouski

Connect AI assistants to TestRail: manage test cases, suites, runs, results, and attachments.

884 installs/wk local only

Chorilo

by chorilo

Choir management for AI assistants: events, RSVP, announcements and sheet music of your choir.

answering

Gastrosync — questions

Answers built from our own checks of this server.

Why is there no tool list for Gastrosync?

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 Gastrosync working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 304 ms. The bar chart above shows every period we have measured.

How do I connect Gastrosync?

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 Gastrosync?

No API key is involved. Gastrosync 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 Gastrosync?

It answers our handshake in 304 ms on average, which is faster than 44% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.