_ registry / mcp streamable-http · checked 1h ago

snagres

https://snagres.com

Registry code: 44bcd72cd4bc8895

api record

SnagRes tracks live reservation availability at the hardest restaurants in New York, San Francisco, Los Angeles and Chicago across Resy, OpenTable, Tock and SevenRooms, and holds a measured record of how often each one is actually bookable. Use it to find a table, to judge whether a restaurant is realistically gettable, or to say when it releases. SnagRes never books or holds a table; complete the booking on the restaurant's own platform.

endpoint
https://snagres.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is snagres live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is snagres free to use?
Yes — the hub reached it with no key and no payment.
What tools does snagres have?
5 tools: restaurant_intel, when_does_it_release, open_now, hardest_tables, last_table_spotted.
Is snagres safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
316ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 5 tools
3 open 2 never probed 3 of 5 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • open_now open 1h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "city": {
      "enum": [
        "nyc",
        "sf",
        "la",
        "chi"
      ],
      "type": "string",
      "description": "nyc, sf, la or chi. Defaults to nyc."
    },
    "limit": {
      "type": "integer",
      "description": "Max rows, up to 50."
    }
  }
}
    arguments 19 lines
  • hardest_tables open 1h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "city": {
      "enum": [
        "nyc",
        "sf",
        "la",
        "chi"
      ],
      "type": "string"
    },
    "limit": {
      "type": "integer"
    }
  }
}
    arguments 17 lines
  • last_table_spotted open 1h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • restaurant_intel unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "restaurant"
  ],
  "properties": {
    "restaurant": {
      "type": "string",
      "description": "Restaurant name, e.g. 'Carbone'."
    }
  }
}
    arguments 12 lines
  • when_does_it_release unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "restaurant"
  ],
  "properties": {
    "date": {
      "type": "string",
      "description": "Optional dining date, YYYY-MM-DD."
    },
    "restaurant": {
      "type": "string",
      "description": "Restaurant name."
    }
  }
}
    arguments 16 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 44bcd72cd4bc8895.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/44bcd72cd4bc8895/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/44bcd72cd4bc8895/badge.svg)](https://brick.blue/agent/44bcd72cd4bc8895?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
90%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.