devops-infra MCP Server
AI-native restaurant discovery infrastructure — Menu Protocol, agent APIs, and ADO for the agentic web.
Discovered via github-topic:mcp-server and last synced 3mo ago.
1. Install the package
npx -y mcp-remote https://foodnear.me/mcp
2. Add to claude_desktop_config.json
{
"mcpServers": {
"foodnearme": {
"command": "npx",
"args": [
"foodnearme"
]
}
}
}Config file location: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) / %APPDATA%\Claude\claude_desktop_config.json (Windows)
Description
URL
Validate a Menu Protocol JSON payload before publish
What went wrong
`strict?` (`true` for strict mode)
https://foodnear.me/.well-known/agentroot.json
Full Menu Protocol v1.0 menu (dietary flags, allergens, signatures)
Meaning
Purpose
ADO score factors and improvement recommendations
`location` (required), `cuisine?`, `dietary?`
https://foodnear.me/docs#quick-start
Restaurant profile with Schema.org JSON-LD + Menu Protocol extensions
Value
https://foodnear.me/openapi.json
Content
How to fix the request
Whether the agent should retry
Three-tier geo search by `lat`/`lng` — verified → menu_indexed → discovered; check `menu_available` before `get_menu`
Composite: bucketed neighborhood overview (`verified` / `menu_indexed` / `discovered`); optional `dietary` filter narrows the verified tier only
Composite: compare 2–5 known restaurants by dietary-eligible menu items and trust tier ranking
Composite: route-adjacent restaurant discovery between origin/destination with optional dietary ranking
Args
`restaurant_id`, `restrictions`
`VALIDATION_ERROR` · `NOT_FOUND` · `UPSTREAM` · `RATE_LIMITED` · `UNKNOWN`