bots.st/food-near-me
Food Near Me
Find nearby verified restaurants and diet-safe options
2102 ms
answered our call
- State
- Answered
- Protocol
- MCP 2024-11-05
- Tools listed
- 10
- Answered
- 3 of the last 3 calls
How to reach it
- MCP, HTTP
https://foodnear.me/mcp
What it can do
| Tool | What it says it does |
|---|---|
compare_restaurants_for_diet | Call this tool when the user wants a side-by-side dietary comparison for 2 to 5 specific restaurants already identified in FNM results. Input Requirements (CRITICAL): `restaurant_ids` MUST be UUIDs copied from prior FNM responses, and `dietary` MUST include at least one supported dietary flag… |
explore_area_for_diet | Call this tool when the user wants a neighborhood overview that surfaces trust tiers explicitly — for example, "what's good for vegan eaters within a mile of this location" or "survey the area around X". Input Requirements (CRITICAL): `location` MUST be `{latitude, longitude}` (Google-style nested… |
find_restaurants_along_route | Call this tool when the user wants route-adjacent dining options between two known coordinates and may care about dietary fit. Input Requirements (CRITICAL): both `origin` and `destination` MUST be `{latitude, longitude}` objects; optional `route_polyline` MUST be a valid encoded polyline if… |
find_safe_places_near_me | Call this tool when the user needs a place that is safe for a specific allergy or diet near a location — for example "where can my celiac kid eat near Brickell tonight". Input Requirements (CRITICAL): `location` MUST be `{latitude, longitude}`; `needs` MUST list one or more of `gluten_free`… |
get_ado_score_breakdown | Call this tool when a restaurant owner, operator, or agent wants to understand why a restaurant is more or less agent-ready. Input Requirements (CRITICAL): `restaurant_id` MUST be a UUID copied from a FNM result. Shows ADO (Agent Discovery Optimization) scoring across menu completeness, location… |
get_menu | Call this tool only when a `search_restaurants` or `get_restaurant` response has `menu_available: true`. Input Requirements (CRITICAL): `restaurant_id` MUST be a UUID copied from a prior FNM result. Returns the full menu in Menu Protocol v1.0 format with item dietary booleans, declared allergens… |
get_restaurant | Call this tool after `search_restaurants` when you need a detailed restaurant profile for a returned `id`. Input Requirements (CRITICAL): `restaurant_id` MUST be a UUID copied from a `search_restaurants` result; do not invent IDs. Returns Schema.org/Restaurant JSON-LD markup plus Menu Protocol… |
get_safety_attestation | Call this tool when you need a citable, tamper-evident allergy-safety statement for ONE restaurant — for example before telling a user a place is safe for a severe allergy. Input Requirements (CRITICAL): `restaurant_id` MUST be a UUID copied from a prior FNM result. Returns an explicit… |
search_restaurants | Call this tool when the user wants restaurant or food discovery near a known location and may need menu trust signals. Input Requirements (CRITICAL): provide either flat `lat`/`lng` or Google-style `locationBias.circle.center.latitude`/`longitude`; if the user gave only a vague place name, resolve… |
validate_menu_protocol | Call this tool when validating a draft or exported Menu Protocol payload before submission or integration. Input Requirements (CRITICAL): provide a JSON object in `payload`; set `strict: true` when checking formal spec compliance, and leave strict false for exploratory debugging that should… |
In its maker's words
AI-native restaurant discovery: verified/menu-indexed/discovered tiers + signed allergy-safety data.
- Website
- foodnear.me
- Source
- github.com/food-near-me/platform
- Publisher
- foodnear.me
- Listed from
- the official MCP Registry as
me.foodnear/foodnear-me - Version
- 1.1.0, updated 18 Jul 2026
- Kinds of work
- Travel, maps and weather, Law, tax and government, Health and science
The domain it lives on
- foodnear.me
- registered 14 Apr 2018 (8 years ago), at NameCheap, Inc., its home page is a working site
From our own crawl of domain names: registry records and the home page as our crawler last saw it.
Every call we made
| When | What happened | Time |
|---|---|---|
| Answered | 2102 ms | |
| Answered | 2205 ms | |
| Answered | 933 ms |
Next door
Is this your bot? Claim its address to add a verified badge and keep the listing current.