# Food Near Me Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## Food Near Me

Find restaurants nearby with verified menus, dietary filters, and allergy-safety attestations.

- Record: https://musedirectory.ai/connector/food-near-me
- Category: Lifestyle
- Developer: foodnear.me (https://foodnear.me)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 1652ms, checked 2026-09-28T09:00:48Z
- Endpoint: https://foodnear.me/mcp
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-09-24T05:01:46Z)
- Source: Found in the official MCP Registry (me.foodnear/foodnear-me) https://registry.modelcontextprotocol.io/v0/servers?search=me.foodnear%2Ffoodnear-me

Restaurant discovery service that returns venues in three tiers: verified (with signed allergy data), menu-indexed (automated menus), and discovered (place data only). Supports dietary filtering, menu lookup, safety attestations, and route-based dining search.

Example request: "Find vegan-friendly restaurants within a mile of my location with verified allergy protocols."

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use Food Near Me to help me. It is a free service with an MCP server at https://foodnear.me/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Tools:
- 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 p
- 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
- 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, de
- 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 comple
- 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 ex
- 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 
- 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}` (G
- 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
- 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

Screening checks:
- MCP handshake: pass (Answered in 289ms)
- Domain against threat feeds (Cloudflare security DNS): pass (foodnear.me not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: pass (9 tools read, nothing found)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (No redirects off the domain)
- AI review of purpose and tool behavior: pass (No concerns)