# Foodnear Me MCP server

Source: https://glimind.com/server/mcp-registry%2Fme.foodnear%2Ffoodnear-me
Registry id: `mcp-registry/me.foodnear/foodnear-me`
Status: live (checked 2026-10-27T03:00:00.635Z)

## Verdict

Foodnear Me MCP server answered 100% of Glimind's liveness checks over 30 days, better than 42% of MCP servers, with 990 ms median handshake and 0 outages in 90 days. Its agent-readiness grade is A (90/100) across 9 tools, costing an agent about 5,113 tokens to load. Checked every few minutes; no tool is ever called.

## Measurements (30 days)

| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 100% | 42% of MCP servers |
| Median handshake latency | 990 ms | 21% of MCP servers |
| p95 handshake latency | 3148 ms | — |
| Checks in 30 days | 4,910 | — |
| Outages, 90 days | 0 | — |
| Median recovery | — | — |
| Agent-readiness score | 90/100 (A) | 69% of MCP servers |
| Tools | 9 | — |
| Tool-list size for an agent | ~5,113 tokens | 38% of MCP servers |
| Days observed | 29 | — |

## Install

```json
{
  "mcpServers": {
    "foodnear-me-mcp-server": {
      "type": "http",
      "url": "https://foodnear.me/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http foodnear-me-mcp-server https://foodnear.me/mcp
```

## Tools (9)

- `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 (CRIT
- `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 th
- `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): bo
- `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): `res
- `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 
- `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 b
- `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 sev
- `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 ei
- `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 

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.