SnagRes
REMOTE · SNAGRES.COM
Live tables, release times and booking odds at hard-to-book restaurants in NYC, SF, LA and Chicago.
Available components
Last scanned (15 hours ago)
Scores higher than 64% of remote servers
Reachable. Last reached 23 Oct 2026.
Category E-commerce
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 Security74
- 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
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 503 tokens (~100/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 71% 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 23 Oct 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.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 18 Oct 26 70
First indexed and scored.
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 23 Oct 2026 · Probed https://snagres.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=snagres.com | CN=WE1,O=Google Trust Services,C=US | 15 Sept 2026 | 14 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 8981044ffe1ae31413df43555f03364c |
| SANs: snagres.com, *.snagres.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of snagres.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| snagres.com. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://snagres.com/mcp | Verified | 200 | |
| http (plaintext) | http://snagres.com/mcp | HTTPS enforced | 301 | https://snagres.com/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 →
hardest_tables Hardest tables in a city ~61
The hardest restaurants to book in a city, ranked by how rarely a table is actually reachable, measured rather than opinion. Use this for 'what are the hardest reservations' or to set expectations.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
last_table_spotted Latest table spotted ~48
The most recent table SnagRes saw open anywhere, with the time it was spotted. Use it to show the service is live, or as a sense of what is moving right now.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
open_now Tables open right now ~99
Tables bookable right now at the hardest restaurants in New York, San Francisco, Los Angeles and Chicago, with exact times, across Resy, OpenTable, Tock and SevenRooms. Use this when someone asks what they can get tonight or this week. Changes by the minute.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | nyc, sf, la or chi. Defaults to nyc. |
| limit | integer | – | Max rows, up to 50. |
No output schema declared.
No examples provided.
restaurant_intel How hard is it to book ~92
The measured booking record for one restaurant: how often a two-top and a four-top are actually open, how many dates were checked, its booking window and release hour. Use this to answer whether a restaurant is realistically gettable, or why someone keeps failing to book it. Figures are measured from SnagRes's own availability checks.
| Name | Type | Req | Description |
|---|---|---|---|
| restaurant | string | yes | Restaurant name, e.g. 'Carbone'. |
No output schema declared.
No examples provided.
when_does_it_release When reservations open ~106
When a restaurant puts new dates up and how far ahead it books. Give a dining date to get the exact day and local time that date becomes bookable. Use this for 'when can I book X for Saturday' or 'when do X reservations open'. Each restaurant sets its own hour and window, so the answer is per restaurant, not per platform.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | Optional dining date, YYYY-MM-DD. |
| restaurant | string | yes | Restaurant name. |
No output schema declared.
No examples provided.
How do I install the SnagRes MCP server?
SnagRes is a hosted endpoint at https://snagres.com/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 · snagres.com
claude mcp add --transport http com-snagres-reservations 'https://snagres.com/mcp'
What is the SnagRes MCP server?
SnagRes is an MCP server listed in the public MCP registry as com.snagres/reservations. Live tables, release times and booking odds at hard-to-book restaurants in NYC, SF, LA and Chicago. This page covers its hosted endpoint (https://snagres.com/mcp).
Is the SnagRes MCP server safe to use?
SnagRes scores 73 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 SnagRes MCP server expose?
SnagRes exposes 5 tools: open_now, restaurant_intel, when_does_it_release, hardest_tables, last_table_spotted. Their descriptions and schemas cost roughly 406 tokens of context every time the server is loaded.
Does the SnagRes MCP server require authentication?
No. We connected to SnagRes without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the SnagRes MCP server still maintained?
SnagRes is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.