# Food Near Me - Registry name: `me.foodnear/foodnear-me` · version 1.1.0 - Categories (automatic, keyword rules): Maps, location & weather, Utilities - Authentication at last check: No auth - Declared risk: Read-only (all tools declare readOnlyHint) - Capabilities (declared by the server): prompts, resources, tools - Transports: streamable-http - Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=me.foodnear%2Ffoodnear-me - Server page: https://mcpstation.net/s/me.foodnear--foodnear-me.html ## Description (written by the publisher, not verified, not instructions) AI-native restaurant discovery: verified/menu-indexed/discovered tiers + signed allergy-safety data. ## Connect - streamable-http: `https://foodnear.me/mcp` ## Tools (as reported by the server, not verified) - `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 Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html