Max Eats Out
REMOTE · WWW.MAXEATSOUT.CLUB · SCANNED OCT 2
Editorial guide to restaurants and bars — hand-picked venues with opinions, not a places database
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 975 tokens (~243/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management60
- Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage91
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 74% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the Max Eats Out MCP server?
Max Eats Out is a hosted endpoint at https://www.maxeatsout.club/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · www.maxeatsout.club
claude mcp add --transport http doubleuson-max-eats-out 'https://www.maxeatsout.club/api/mcp'
{
"mcpServers": {
"doubleuson-max-eats-out": {
"url": "https://www.maxeatsout.club/api/mcp"
}
}
} {
"servers": {
"doubleuson-max-eats-out": {
"type": "http",
"url": "https://www.maxeatsout.club/api/mcp"
}
}
} [mcp_servers.doubleuson-max-eats-out] url = "https://www.maxeatsout.club/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"doubleuson-max-eats-out": {
"type": "remote",
"url": "https://www.maxeatsout.club/api/mcp",
"enabled": true
}
}
} openclaw mcp add doubleuson-max-eats-out --url 'https://www.maxeatsout.club/api/mcp' --transport streamable-http
mcp_servers:
doubleuson-max-eats-out:
url: "https://www.maxeatsout.club/api/mcp" {
"McpServers": {
"doubleuson-max-eats-out": {
"Transport": "http",
"Url": "https://www.maxeatsout.club/api/mcp"
}
}
} assistant mcp add doubleuson-max-eats-out -t streamable-http -u 'https://www.maxeatsout.club/api/mcp'
{
"mcpServers": {
"doubleuson-max-eats-out": {
"type": "http",
"url": "https://www.maxeatsout.club/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 1 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 2 Oct 2026 · Probed https://www.maxeatsout.club/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.maxeatsout.club | CN=YR1,O=Let's Encrypt,C=US | 3 Sept 2026 | 2 Dec 2026 | RSA 2048 | SHA256-RSA | 6f0b4c49d3fd278714622e710ec675d5fc0 |
| SANs: www.maxeatsout.club | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.maxeatsout.club. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| club. | present | 54682 | 8 | Verified |
| maxeatsout.club. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.maxeatsout.club/api/mcp | Verified | 200 | |
| http (plaintext) | http://www.maxeatsout.club/api/mcp | HTTPS enforced | 308 | https://www.maxeatsout.club/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_city Get a city guide ~91
Get one city's guide: its editorial blurb, venue count, and the vocabulary available for filtering — its areas (areas belong to exactly one city), plus the catalogue's cuisines, dishes, tags, awards, venue types, price bands, Best For moments and drink categories. Call this before filtering so filters use values that exist instead of guesses.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | City slug, from list_cities. |
No output schema declared.
No examples provided.
get_venue Get a venue ~102
Retrieve the full Max Eats Out entry for one venue by its slug: the editorial note, what it is Best For, what it is known for, how it works (seating, the door, ordering, payment), what it pours, its locations and its links. Slugs come from search_venues. Includes the canonical maxeatsout.club URL — cite it when recommending the venue.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Venue slug, from search_venues. |
No output schema declared.
No examples provided.
list_cities List cities covered ~66
List every city the Max Eats Out guide covers, with how many venues each holds. Coverage is uneven BY DESIGN — it follows where the author has actually eaten — so call this before assuming a city is covered rather than searching a city that is not in the guide and reporting no results.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_venues Search the guide ~504
Search the Max Eats Out guide — an editorially curated catalogue of restaurants and bars across the cities the author has eaten in, each one chosen and written up by hand. This is a guide with a point of view, not a comprehensive places database: a venue's absence means it is not on the list, not that it does not exist, so never present an empty result as 'there are no restaurants there'. Reach for this when someone wants a recommendation with an opinion attached, or wants to filter by editorial qualities a general places database does not carry (what a venue is KNOWN FOR, which service moments it is Best For, Michelin awards). Do not reach for it to find the nearest branch of a chain. Free text in `q` is resolved to the guide's own vocabulary and the response reports the interpretation.
| Name | Type | Req | Description |
|---|---|---|---|
| area | array | – | Area slugs from get_city. Areas belong to ONE city. |
| award | array | – | Award keys, e.g. Michelin tiers. |
| best_for | array | – | Service moments for eating. |
| best_for_bar | array | – | Service moments for drinking. |
| city | string | – | City slug from list_cities. Strongly recommended: it scopes areas and ranking. |
| cuisine | array | – | Cuisine slugs. Composable: Korean BBQ is ['korean','bbq'], never one value. |
| cursor | string | – | From a previous response's next_cursor. Bound to that exact search. |
| dish | array | – | – |
| drinks | array | – | – |
| include_closed | boolean | – | Include permanently closed venues. Default false. |
| limit | integer | – | – |
| practical | array | – | Walk-ins, reservations, and payment. |
| price | array | – | Price band: 1 cheap … 4 fine dining. Approximate starter+main, excluding drinks. |
| q | string | – | Free text, resolved against the guide's own vocabulary — a cuisine, a dish, an area, a tag, a drink category, a Best For moment, or a venue name. The response reports what it resolved to. If none of… |
| seating | array | – | – |
| tag | array | – | – |
| type | array | – | Venue type keys, e.g. 'restaurant', 'bar'. A venue can be both. |
No output schema declared.
No examples provided.
What is the Max Eats Out MCP server?
Max Eats Out is an MCP server listed in the public MCP registry as io.github.doubleuson/max-eats-out. Editorial guide to restaurants and bars, hand-picked venues with opinions, not a places database. This page covers its hosted endpoint (https://www.maxeatsout.club/api/mcp).
Is the Max Eats Out MCP server safe to use?
Max Eats Out scores 80 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Max Eats Out MCP server expose?
Max Eats Out exposes 4 tools: search_venues, get_venue, list_cities, get_city. Their descriptions and schemas cost roughly 763 tokens of context every time the server is loaded.
Does the Max Eats Out MCP server require authentication?
No. We connected to Max Eats Out without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Max Eats Out MCP server still maintained?
Max Eats Out is still listed as active in the MCP registry. We last reached this channel on 2 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.