Skip to content

SnagRes MCP server

com.snagres/reservationssnagres.comstreamable-httpv1.1.1Scanned

Live tables, release times and booking odds at hard-to-book restaurants in NYC, SF, LA and Chicago.

5 tools: 5 change things.

Tools: 0 delete, 0 irreversible, 5 write, 0 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

5 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the SnagRes MCP server can do

The SnagRes MCP server is published by snagres.com, a domain the MCP Registry verified. It has 5 tools. It can create or change data (5 tools: open_now, restaurant_intel, when_does_it_release, hardest_tables and 1 more), but cannot delete data. None of its tools only reads.

None of its tools reads private data, brings in text other people write, or sends data out.

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 10, 2026, version 1.1.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

5 tools

Changes things 5Claude Code: ask
  • hardest_tablesThe hardest restaurants to book in a city, ranked by how rarely a table is actually reachable, measured rather than opinion.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Hardest tables in a city
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • last_table_spottedThe most recent table SnagRes saw open anywhere, with the time it was spotted.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Latest table spotted
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • open_nowTables 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.1 finding

    Why it is in this group

    • The name "open_now" says "open": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "open_now" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "open_now" says "open": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Tables open right now
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • restaurant_intelThe 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.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: How hard is it to book
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • when_does_it_releaseWhen a restaurant puts new dates up and how far ahead it books.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: When reservations open
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:47 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
5
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 5 tools that change things (5 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://snagres.com/mcp: tools/list returned 5 tools to an anonymous client, including open_now (write), restaurant_intel (write), when_does_it_release (write), hardest_tables (write), last_table_spotted (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "open_now" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "open_now" says "open": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.1.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http reservations https://snagres.com/mcp
claude mcp add --transport http reservations https://snagres.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__reservations__open_now",
      "mcp__reservations__restaurant_intel",
      "mcp__reservations__when_does_it_release",
      "mcp__reservations__hardest_tables",
      "mcp__reservations__last_table_spotted"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as reservations. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.snagres/reservations/verify?hash=13b4ae39e94fc644db8361acb71db6109fe9e6977e5f23d593a36da831e2b871" | jq -e '.changed == false'

Pinned hash 13b4ae39e94f, from Nov 10, 2026, 03:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.snagres/reservations/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.snagres/reservations
[![Anlyon Radar](https://radar.anlyon.com/badge/com.snagres/reservations.svg)](https://radar.anlyon.com/servers/com.snagres/reservations)

Source: MCP Registry. Synced Nov 10, 2026, 03:17 UTC.

SnagRes MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the SnagRes MCP server safe?

No scan can promise that. What its definitions show: 5 tools, 5 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the SnagRes MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the SnagRes MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the SnagRes MCP server have?

5 tools: 5 write. open_now, restaurant_intel, when_does_it_release, hardest_tables and last_table_spotted.

Does the SnagRes MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the SnagRes MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the SnagRes MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 10, 2026.