← Registry

General Tools

indiarestros.com

Provides general-purpose tools through the Model Context Protocol.

1 endpoint8 known toolsFirst detected October 11, 2026Last detected October 11, 2026

ENDPOINT 1

https://indiarestros.com/mcp

No auth detected

MCP server metadata

Name
indiarestros
Version
1.0.0
Capabilities
tools.listChanged
Server instructions

IndiaRestros (https://indiarestros.com) is India's open restaurant graph: restaurants, cafes, dhabas, bakeries, bars and sweet shops across every state, each with a permanent id IRR-XXXXXXXXXX. Use it to find places to eat, read their phone numbers, timings, cuisines and menus, and to send a correction when something is wrong. How to use it well: - search_restaurants takes free words (name, dish, cuisine) plus a place. Give city as a slug (bengaluru, mumbai, delhi, new-delhi is delhi) and optionally locality (indiranagar, kondapur), or lat/lon with radius_m for "near me". "biryani in kondapur" also works as q alone. - Every field carries its source (src: osm = OpenStreetMap, overture = Overture Maps, owner = the restaurant itself, google/zomato/... = public listings) and the record has scores.confidence (0-1). Say where a fact came from when it matters, e.g. "the phone number is from OpenStreetMap; it may be out of date". - Results are sorted by relevance or distance and then by how well each place is documented. Never by payment: no restaurant can buy a position. - Ratings: ratings.foodie are IndiaRestros foodie ratings only; ratings.external are other sites' numbers, labelled. - Users contact restaurants directly by phone/WhatsApp/website. IndiaRestros takes no commission. - Always cite the restaurant's url.

Known tools 8

search_restaurants

Find restaurants, cafes, dhabas, bakeries, bars and sweet shops by words and place.

Inferred read-only
get_restaurant

Full record by id (IRR-XXXXXXXXXX or the 10-char code at the end of its url): address, geo, phones, website, timings (raw + parsed, open_now in IST), cuisines, diet, ratings, menu summary, sources and confidence.

Inferred read-only
search_dishes

Find specific dishes on restaurant menus across India: item name, price in INR, veg/non-veg, menu section, and the restaurant (name, area, url).

Inferred read-only
get_menu

Menu sections and items with prices in INR and veg/non-veg marks, with the menu source and date.

Inferred read-only
list_places

Browse the place hierarchy with restaurant counts.

Inferred read-only
get_place

A city (city:<slug>) or area (loc:<city>:<area>) with counts by kind and cuisine and its areas.

Inferred read-only
report_correction

Tell IndiaRestros that something is wrong: a dead phone number, new timings, a closure, a move.

Inferred read-only
about_dataset

Counts, sources, top cities, how ranking works and how to read confidence.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.indiarestros]
url = "https://indiarestros.com/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "indiarestros": {
      "type": "http",
      "url": "https://indiarestros.com/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: indiarestros
Remote MCP URL: https://indiarestros.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "indiarestros": {
      "url": "https://indiarestros.com/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "indiarestros": {
      "type": "http",
      "url": "https://indiarestros.com/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "indiarestros",
  "transport": "streamable-http",
  "url": "https://indiarestros.com/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.