AI-native restaurant discovery: verified/menu-indexed/discovered tiers + signed allergy-safety data.
Connect Remote server
claude mcp add --transport http foodnear-me https://foodnear.me/mcp{
"mcpServers": {
"foodnear-me": {
"url": "https://foodnear.me/mcp"
}
}
}{
"servers": {
"foodnear-me": {
"type": "http",
"url": "https://foodnear.me/mcp"
}
}
}Settings > Connectors > Add custom connector
URL: https://foodnear.me/mcpTools 10 found in our last check
search_restaurantsCall 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…
get_restaurantCall 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 plu…
get_menuCall 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, d…
get_ado_score_breakdownCall 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 compl…
get_safety_attestationCall 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 e…
validate_menu_protocolCall 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…
explore_area_for_dietCall 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}` (…
compare_restaurants_for_dietCall 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 supporte…
find_restaurants_along_routeCall 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 encode…
find_safe_places_near_meCall 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 `…
Details
| Endpoint | https://foodnear.me/mcp (Streamable HTTP) |
| First published | 18 Jul 2026 |
| Last updated | 18 Jul 2026 |
| Registry name | me.foodnear/foodnear-me |
More search and web servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.