_ registry / mcp + a2a streamable-http · checked 2h ago

indiarestros

https://indiarestros.com

Registry code: 97ceb0c11935645e

api record

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,

endpoint
https://indiarestros.com/mcp
door code
a26c36c8b1f5e055
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is indiarestros live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is indiarestros free to use?
Yes — the hub reached it with no key and no payment.
What tools does indiarestros have?
8 tools: get_restaurant, list_places, get_place, report_correction, get_menu, about_dataset, search_dishes, search_restaurants.
Is indiarestros safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
590ms

last good check

priced tools
0

of 8 tools

_ answered our checks, 90 days 2 checks · signed record
  • unknown → live
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 8 tools
2 open 6 never probed 2 of 8 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • search_dishes open 2h ago

    Find specific dishes on restaurant menus across India: item name, price in INR, veg/non-veg, menu section, and the restaurant (name, area, url). E.g. q "paneer tikka" city "bengaluru" max_price 300 veg true, or "masala dosa in indiranagar". Covers restaurants whose menus we hold (growing daily); if nothing is found, fall back to search_restaurants with the dish words.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "q": {
      "type": "string",
      "maxLength": 200,
      "description": "Dish words; \"biryani in kondapur\" also works"
    },
    "lat": {
      "type": "number",
      "maximum": 37.5,
      "minimum": 6
    },
    "lon": {
      "type": "number",
      "maximum": 98.5,
      "minimum": 67
    },
    "veg": {
      "type": "boolean",
      "description": "true = vegetarian items only"
    },
    "city": {
      "type": "string",
      "maxLength": 60
    },
    "limit": {
      "type": "integer",
      "maximum": 60,
      "minimum": 1
    },
    "offset": {
      "type": "integer",
      "maximum": 1000,
      "minimum": 0
    },
    "locality": {
      "type": "string",
      "maxLength": 80
    },
    "radius_m": {
      "type": "integer",
      "maximum": 25000,
      "minimum": 100
    },
    "max_price": {
      "type": "integer",
      "maximum": 100000,
      "minimum": 1,
      "description": "INR"
    }
  },
  "additionalProperties": false
}
    arguments 55 lines
  • search_restaurants open 2h ago

    Find restaurants, cafes, dhabas, bakeries, bars and sweet shops by words and place. Returns id, name, kind, cuisines, locality, city, url and whether a phone number is on file.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "q": {
      "type": "string",
      "maxLength": 200,
      "description": "Name, dish or cuisine words. \"biryani in kondapur\" also works."
    },
    "lat": {
      "type": "number",
      "maximum": 37.5,
      "minimum": 6
    },
    "lon": {
      "type": "number",
      "maximum": 98.5,
      "minimum": 67
    },
    "city": {
      "type": "string",
      "maxLength": 60,
      "description": "City slug, e.g. bengaluru, mumbai, delhi, hyderabad, chennai, pune, kolkata"
    },
    "diet": {
      "enum": [
        "pure-veg",
        "halal"
      ],
      "type": "string"
    },
    "kind": {
      "enum": [
        "restaurant",
        "cafe",
        "bakery",
        "fast-food",
        "bar",
        "sweets",
        "dhaba",
        "food-court"
      ],
      "type": "string"
    },
    "limit": {
      "type": "integer",
      "maximum": 50,
      "minimum": 1
    },
    "offset": {
      "type": "integer",
      "maximum": 1000,
      "minimum": 0
    },
    "cuisine": {
      "type": "string",
      "maxLength": 40,
      "description": "Cuisine slug: north-indian, south-indian, biryani, chinese, pizza, cafe, desserts, street-food, ..."
    },
    "locality": {
      "type": "string",
      "maxLength": 80,
      "description": "Area slug within the city, e.g. indiranagar, koramangala, bandra-west"
    },
    "radius_m": {
      "type": "integer",
      "maximum": 25000,
      "minimum": 100,
      "description": "With lat/lon, default 3000"
    }
  },
  "additionalProperties": false
}
    arguments 73 lines
  • get_restaurant unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "maxLength": 14,
      "minLength": 10
    }
  },
  "additionalProperties": false
}
    arguments 15 lines
  • list_places unknown never probed

    Browse the place hierarchy with restaurant counts. type=state (all), type=city with parent=state:<slug>, type=locality with parent=city:<slug>.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "type"
  ],
  "properties": {
    "type": {
      "enum": [
        "state",
        "city",
        "locality"
      ],
      "type": "string"
    },
    "limit": {
      "type": "integer",
      "maximum": 500,
      "minimum": 1
    },
    "parent": {
      "type": "string",
      "maxLength": 80
    }
  },
  "additionalProperties": false
}
    arguments 27 lines
  • get_place unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "maxLength": 120,
      "minLength": 5
    }
  },
  "additionalProperties": false
}
    arguments 15 lines
  • report_correction unknown never probed

    Tell IndiaRestros that something is wrong: a dead phone number, new timings, a closure, a move. Checked before it goes live. Ask the user before sending.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "id",
    "field",
    "value"
  ],
  "properties": {
    "id": {
      "type": "string",
      "maxLength": 14,
      "minLength": 10
    },
    "field": {
      "enum": [
        "phone",
        "hours",
        "closed",
        "moved",
        "name",
        "website",
        "menu",
        "other"
      ],
      "type": "string"
    },
    "value": {
      "type": "string",
      "maxLength": 600,
      "minLength": 2,
      "description": "The correct value or what happened"
    },
    "evidence_url": {
      "type": "string",
      "format": "uri"
    }
  },
  "additionalProperties": false
}
    arguments 40 lines
  • get_menu unknown 2h ago

    Menu sections and items with prices in INR and veg/non-veg marks, with the menu source and date. Null when no menu is on file.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "maxLength": 14,
      "minLength": 10
    }
  },
  "additionalProperties": false
}
    arguments 15 lines
  • about_dataset unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
_ try it over mcp through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 97ceb0c11935645e.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/97ceb0c11935645e/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/97ceb0c11935645e/badge.svg)](https://brick.blue/agent/97ceb0c11935645e?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we knowoff the mcp door
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.