me.foodnear/foodnear-me · v1.1.0 · agents-and-memory
Food Near Me is healthy: it completed an MCP handshake in 1218 ms and exposes 9 tools.
AI-native restaurant discovery: verified/menu-indexed/discovered tiers + signed allergy-safety data.
Endpoint: https://foodnear.me/mcp (streamable-http)
Repository · Website · JSON · Add to my inventory
| Users (last 30 days) | 0 |
| Handshake | Healthy |
| Auth needed | None |
| Tool count | 9 |
| Latency | 1218 ms |
| Last checked (UTC) | 2026-10-16T19:00:50.222Z |
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-10-16T19:00:50.222Z | Healthy | 1218 | |
| 2026-10-15T12:35:15.333Z | Healthy | 1291 |
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 i |
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 exten |
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, cu |
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 acc |
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 `safety_tier` |
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 surface |
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 o |
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. Optio |
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 provide |