_ registry / mcp http-sse · checked 2h ago

nyc-restaurant-week

https://nycrestaurantweek.app

Registry code: 520123ef3efab79f

api record

All 636 NYC Restaurant Week Summer 2026 restaurants — filter by cuisine, borough, price, and date.

from a public catalogue that lists it, not from the operator

endpoint
https://nycrestaurantweek.app/mcp
protocol
http-sse ·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 nyc-restaurant-week live?
Yes — it answered the hub's last check (checked 2h ago). It answered 98% of checks over the last 30 days.
Is nyc-restaurant-week free to use?
Yes — the hub reached it with no key and no payment.
What tools does nyc-restaurant-week have?
4 tools: check_date, get_restaurant, search_restaurants, list_filters.
Is nyc-restaurant-week 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
98.3%

90 days 98.7%· all time 98.7%

latency
239ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 454 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • search nyc restaurant week restaurants
  • get restaurant prix-fixe offers
  • check restaurant week rules for a date
takes → gives
text, data → data
tools
4 reads
_ 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 4 tools
2 open 2 never probed 2 of 4 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.

  • search_restaurants reads open 13h ago

    Search the 0 restaurants participating in NYC Restaurant Week Summer 2026 (Jul 20 – Sep 6). All filters are optional and combinable. Prix-fixe tiers are $30 / $45 / $60 for lunch, brunch, or dinner. Saturdays are excluded program-wide; Sunday participation varies. Returns a paginated list with total count — use get_restaurant with a slug for menus, reservation and website links.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "date": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
          "description": "A specific date (YYYY-MM-DD) you want to dine — resolves to the right week and handles Saturday/Sunday rules"
        },
        "meal": {
          "enum": [
            "lunch",
            "dinner",
            "brunch"
          ],
          "type": "string"
        },
        "week": {
          "type": "integer",
          "maximum": 7,
          "minimum": 1,
          "description": "Program week 1–7 (Week 1 starts Jul 20, Week 7 ends Sep 6)"
        },
        "limit": {
          "type": "integer",
          "maximum": 25,
          "minimum": 1,
          "description": "Results per page, default 10, max 25"
        },
        "price": {
          "enum": [
            30,
            45,
            60
          ],
          "type": "number",
          "description": "Maximum prix-fixe price per person: 30, 45, or 60"
        },
        "query": {
          "type": "string",
          "description": "Free-text search over name, description, cuisine, and neighborhood (e.g. 'rooftop', 'omakase', 'steak tribeca')"
        },
        "offset": {
          "type": "integer",
          "minimum": 0,
          "description": "Pagination offset"
        },
        "sunday": {
          "type": "boolean",
          "description": "true = only restaurants offering Restaurant Week on Sundays"
        },
        "borough": {
          "enum": [
            "Manhattan",
            "Brooklyn",
            "Queens",
            "The Bronx",
            "Staten Island"
          ],
          "type": "string"
        },
        "cuisine": {
          "type": "string",
          "description": "Cuisine filter, e.g. Italian, Japanese / Sushi, Steakhouse, French, Korean, Mexican, Seafood, Indian, Thai (see list_filters for all 50+)"
        },
        "has_menu": {
          "type": "boolean",
          "description": "true = only restaurants that published their Restaurant Week menu PDF"
        },
        "collection": {
          "enum": [
            "hidden-gems",
            "date-night",
            "celebrity-chefs",
            "summer-vibes",
            "around-the-boroughs",
            "dress-for-the-occasion",
            "for-the-foodies",
            "classic-restaurants"
          ],
          "type": "string",
          "description": "Curated NYC Tourism collections"
        },
        "neighborhood": {
          "type": "string",
          "description": "e.g. Tribeca, West Village, Astoria, Williamsburg (see list_filters)"
        },
        "bookable_on_opentable": {
          "type": "boolean",
          "description": "true = only restaurants reservable via OpenTable"
        }
      },
      "additionalProperties": false
    }
    arguments 94 lines
  • list_filters reads open 13h ago

    List every available filter value with participant counts: cuisines, boroughs, neighborhoods, price tiers, meals, curated collections, and the seven program weeks with their dates. Useful before searching, or to summarize the program.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • check_date reads unknown 6h ago

    Check whether a date (YYYY-MM-DD) falls within NYC Restaurant Week Summer 2026 and what the rules are that day (which program week, Saturday exclusion, Sunday limitations), plus how many restaurants participate that day.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "date"
      ],
      "properties": {
        "date": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
          "description": "Date to check, YYYY-MM-DD"
        }
      },
      "additionalProperties": false
    }
    arguments 15 lines
  • get_restaurant reads unknown 13h ago

    Get full details for one participating restaurant by slug or name: description, all prix-fixe offers, participating weeks, Restaurant Week menu PDF, website, and OpenTable reservation link.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "restaurant"
      ],
      "properties": {
        "restaurant": {
          "type": "string",
          "description": "Restaurant slug (from search_restaurants) or name, e.g. 'gran-morsi' or 'Gran Morsi'"
        }
      },
      "additionalProperties": false
    }
    arguments 14 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 520123ef3efab79f.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/520123ef3efab79f/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/520123ef3efab79f/badge.svg)](https://brick.blue/agent/520123ef3efab79f?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
80%

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.