NYCfoodie
REMOTE · NYCFOODIE-PRODUCTION.UP.RAILWAY.APP
Editorial NYC restaurant recommendations for AI agents: search, compare, guides, ratings.
Available components
Last scanned (20 hours ago)
Scores higher than 67% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Search and Retrieval
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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 Usability66
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1941 tokens (~242/item across 8 items; 8 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 11 Nov 26 +1
- Stability: 0.97 → pass security
- 10 Nov 26 −1
- Stability: pass → 0.97 functional
- 9 Nov 26 +1
- Stability: 0.97 → pass security
- 8 Nov 26 −1
- Stability: pass → 0.97 functional
- 7 Nov 26 0
- Endpoint reachability: unreachable → reachable ▲ functional
- 6 Nov 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
- 5 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 20 Oct 26 0
- Stability: 0.97 → pass security
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 21 Nov 2026 · Probed https://nycfoodie-production.up.railway.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.up.railway.app | CN=YE2,O=Let's Encrypt,C=US | 27 Sept 2026 | 26 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 618edc56941aa1165ddb080bf9f799eb7c1 |
| SANs: *.up.railway.app, up.railway.app | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of nycfoodie-production.up.railway.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| app. | DS published | 23684 | 8 | Verified |
| railway.app. | No DS | 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://nycfoodie-production.up.railway.app/mcp | Verified | 200 | |
| http (plaintext) | http://nycfoodie-production.up.railway.app/mcp | HTTPS enforced | 301 | https://nycfoodie-production.up.railway.app/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 →
compare_restaurants ~122
Compare 2–5 named restaurants head-to-head as structured data (rating, price, tags, review summary). Use when the user asks to choose between specific places, e.g. 'should I go to X or Y?' or to compare four options on a budget.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | yes | City slug, always required. Currently 'new-york', covering the five boroughs plus the immediate metro (within 30 km of Manhattan). |
| ids | array | – | Alias for restaurants |
| restaurants | array | – | Restaurant ids or names to compare |
No output schema declared.
No examples provided.
find_guides ~165
Find curated editorial guides (ranked lists) matching a theme, e.g. 'best ramen'. Returns each guide with its ranked entries, blurbs and linked restaurants. Use when the user wants the editorial lists themselves rather than individual restaurant picks. Set include_entries=false to list guide titles and metadata without pulling every entry blurb.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | yes | City slug, always required. Currently 'new-york', covering the five boroughs plus the immediate metro (within 30 km of Manhattan). |
| include_entries | boolean | – | Set false to return guide metadata without the ranked entry blurbs (default true) |
| limit | integer | – | Max results (default 10) |
| query | string | – | Theme, e.g. 'best ramen', 'date night' |
No output schema declared.
No examples provided.
find_similar ~132
Find restaurants similar to a named one, scored by shared cuisine, occasion and neighbourhood tags, price-tier proximity and guide co-occurrence. Use for 'like X' or 'alternatives to X' requests.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | yes | City slug, always required. Currently 'new-york', covering the five boroughs plus the immediate metro (within 30 km of Manhattan). |
| id | string | – | Canonical restaurant id, or a name to resolve |
| limit | integer | – | Max results (default 10) |
| name | string | – | Alias for id: the restaurant's exact name |
No output schema declared.
No examples provided.
get_restaurant ~352
Get the full picture for one restaurant in one call: Infatuation rating (0–10), price tier, address, reservation link, booking intel, review summary, tags and every guide it appears in. Use when the user names a specific restaurant. editorial_blurbs carries verbatim Eater guide excerpts (guide title, URL, position, blurb, captured_at) for any venue with Eater guide entries — Eater-only venues have no rating or price, only this prose plus tags. Full review prose is opt-in via include_prose (default: headline and summary only). review.headline is the source's actual headline when one exists, otherwise null — use review.summary for the descriptive text. match_type is 'exact' when the id or name matched verbatim, 'fuzzy' when it was resolved from a partial/typo'd name — never present a fuzzy match as the venue the user named without saying so. booking is null when the source has no booking intel (not the same as walk-in-only); a reservation link alone never implies a booking policy. data_as_of is the dataset vintage and crawled_at is when this venue was last crawled — caveat fast-decaying claims (closures especially) when these are old.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | yes | City slug, always required. Currently 'new-york', covering the five boroughs plus the immediate metro (within 30 km of Manhattan). |
| id | string | – | Canonical restaurant id, or a name to resolve |
| include_prose | boolean | – | Include the full review text (default false: headline + summary only) |
| name | string | – | Alias for id: the restaurant's exact name |
No output schema declared.
No examples provided.
guide_consensus ~149
Rank restaurants by how many distinct guides feature them, optionally filtered by theme. Use for 'where can't I go wrong' or safest-bet picks. Differs from find_guides: this returns ranked restaurants, not the guides themselves. Each row carries guide_appearance_count (a number); get_restaurant's guide_appearances is the full entry list.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | yes | City slug, always required. Currently 'new-york', covering the five boroughs plus the immediate metro (within 30 km of Manhattan). |
| limit | integer | – | Max results (default 10) |
| theme | string | – | Guide theme, e.g. 'ramen', 'brunch' |
No output schema declared.
No examples provided.
search_restaurants ~528
Search restaurants by free text, cuisine, neighbourhood, occasion or price, optionally near a point. Use when the user describes what they want (e.g. 'Italian date night in the West Village', 'ramen near me') rather than naming a specific restaurant. Free text matches names, tags, review prose and guide blurbs (e.g. 'cacio e pepe'). Returns compact matches with Infatuation rating (0–10), price tier, address_line and tags. Cards carry guide_appearance_count (a number); get_restaurant's guide_appearances is the full entry list. Known-closed venues are excluded by default. Coverage for city='new-york' is the five boroughs plus the immediate metro (within 30 km of Manhattan). With no query or filters, returns the highest-rated venues.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | yes | City slug, always required. Currently 'new-york', covering the five boroughs plus the immediate metro (within 30 km of Manhattan). |
| cuisine | string | – | e.g. 'Italian', 'ramen' |
| include_closed | boolean | – | Include known-closed venues (default false) |
| lat | number | – | Latitude for proximity search. Must be given together with lng; radius_km defaults to 5 km when omitted. A location outside the NYC coverage area is rejected with an error. |
| limit | integer | – | Max results (default 10) |
| lng | number | – | Longitude for proximity search. Must be given together with lat; radius_km defaults to 5 km when omitted. |
| min_rating | number | – | Minimum Infatuation rating |
| neighborhood | string | – | e.g. 'West Village', or a borough like 'Brooklyn' |
| occasion | string | – | Occasion tag. Allowed: 'Date Nights', 'Happy Hours', 'Pre-Theater', 'See & Be Seen', 'Serious Takeout Operation', 'Unique Dining Experiences', 'Wasting Your Time & Money'. Hyphens, spaces and undersc… |
| price_tier | integer | – | 1 ($) to 4 ($$$$) |
| query | string | – | Free text, e.g. 'date-night Italian' |
| radius_km | number | – | Search radius in kilometres (default 5 when lat/lng are given without it). Requires lat and lng. |
| sort | string | – | Sort by rating (default) or guide appearances |
No output schema declared.
No examples provided.
submit_feedback ~114
Record feedback on a tool result: a 1–5 rating, a comment, or both (at least one is required). Use after showing the user a recommendation to log what was good or wrong. Each call stores a new feedback entry; it changes nothing the user sees.
| Name | Type | Req | Description |
|---|---|---|---|
| comment | string | – | What was good or wrong |
| rating | integer | – | 1 (poor) to 5 (excellent) |
| tool | string | – | Which tool the feedback is about, e.g. 'search_restaurants' |
No output schema declared.
No examples provided.
top_rated ~379
List the highest-rated restaurants (Infatuation 0–10 scale), with optional cuisine, neighbourhood and price filters. Use for 'best in the city' requests. Differs from search_restaurants: no free-text query, strictly rating-ordered.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | yes | City slug, always required. Currently 'new-york', covering the five boroughs plus the immediate metro (within 30 km of Manhattan). |
| cuisine | string | – | e.g. 'Italian', 'ramen' |
| include_closed | boolean | – | Include known-closed venues (default false) |
| lat | number | – | Latitude for proximity search. Must be given together with lng; radius_km defaults to 5 km when omitted. A location outside the NYC coverage area is rejected with an error. |
| limit | integer | – | Max results (default 10) |
| lng | number | – | Longitude for proximity search. Must be given together with lat; radius_km defaults to 5 km when omitted. |
| min_rating | number | – | Minimum Infatuation rating |
| neighborhood | string | – | e.g. 'West Village', or a borough like 'Brooklyn' |
| occasion | string | – | Occasion tag. Allowed: 'Date Nights', 'Happy Hours', 'Pre-Theater', 'See & Be Seen', 'Serious Takeout Operation', 'Unique Dining Experiences', 'Wasting Your Time & Money'. Hyphens, spaces and undersc… |
| price_tier | integer | – | 1 ($) to 4 ($$$$) |
| radius_km | number | – | Search radius in kilometres (default 5 when lat/lng are given without it). Requires lat and lng. |
No output schema declared.
No examples provided.
How do I install the NYCfoodie MCP server?
NYCfoodie is a hosted endpoint at https://nycfoodie-production.up.railway.app/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 · nycfoodie-production.up.railway.app
claude mcp add --transport http tireniajilore-nycfoodie 'https://nycfoodie-production.up.railway.app/mcp'
What is the NYCfoodie MCP server?
NYCfoodie is an MCP server listed in the public MCP registry as io.github.tireniajilore/nycfoodie. Editorial NYC restaurant recommendations for AI agents: search, compare, guides, ratings. This page covers its hosted endpoint (https://nycfoodie-production.up.railway.app/mcp).
Is the NYCfoodie MCP server safe to use?
NYCfoodie scores 77 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 NYCfoodie MCP server expose?
NYCfoodie exposes 8 tools: search_restaurants, get_restaurant, compare_restaurants, find_guides, find_similar, and 3 more. Their descriptions and schemas cost roughly 1,941 tokens of context every time the server is loaded.
Does the NYCfoodie MCP server require authentication?
No. We connected to NYCfoodie without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the NYCfoodie MCP server still maintained?
NYCfoodie is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the NYCfoodie MCP server?
VerifyMCP ran 12 checks on NYCfoodie, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about NYCfoodie: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.