spatial-india
Registry code: 95425f95a6598633
District-level open data for India, from the Census, NFHS-5, NCRB, RBI, the Agricultural Census and others. Indicator ids are not guessable — start with find_indicator. Every value carries its source, vintage, caveat and a per-district estimated flag; quote them rather than the bare number, and end an answer with build_map_link.
- endpoint
- https://api.spatialindia.com/mcp
- 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 spatial-india live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is spatial-india free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does spatial-india have?
- 6 tools: get_district, rank_districts, find_indicator, compare_districts, build_map_link, get_methodology.
- Is spatial-india 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.
90 days 100%· all time 100%
last good check
of 6 tools
- unknown → live
- used for
- look up district indicators in india
- compare indian districts on census data
- rank districts by an indicator
- find indicator ids by subject
- get methodology and source for a figure
- takes → gives
- text → data
- tools
- 6 reads
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.
through this hub
successful
what callers paid
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.
get_methodology reads open 42d ago
Use whenever the answer will state a number to a user, and always when asked how a figure was produced, how old it is, or whether it can be trusted. Returns the source, vintage, definition, caveat, estimation method, licence attribution and the citation string for one indicator, or for the dataset as a whole when no indicator is given. Do not describe a number as measured or estimated without checking here — each district carries its own `estimated` flag.
{ "type": "object", "properties": { "indicator": { "type": "string", "description": "An indicator id. Omit for the dataset-wide vintage, sources and citation." } }, "additionalProperties": false }arguments 10 linesget_district reads unknown never probed
Use when the question is about one named place — "tell me about Bilaspur", "what is Pune's literacy rate". Resolves an Indian district name, including common alternative spellings, to its objectid and returns its values. Four district names are shared by two states, so if the name is ambiguous this returns every match with its state and no data: ask the user which one, then call again with `state`.
{ "type": "object", "required": [ "name" ], "properties": { "name": { "type": "string", "description": "District name, an alternative spelling, or an objectid." }, "state": { "type": "string", "description": "State name. Supply this only to disambiguate a repeated district name." }, "indicators": { "type": "array", "items": { "type": "string" }, "description": "Indicator ids from find_indicator. Omit to get the district's full profile — every published indicator in one call, which is usually what you want." } }, "additionalProperties": false }arguments 24 linesrank_districts reads unknown never probed
Use for best/worst/highest/lowest questions over many districts — "worst 20 districts for child stunting in Uttar Pradesh". Check the indicator's `polarity` in the result before calling a tail "worst": for a higher-worse indicator the worst districts are `order: "desc"`, for higher-better they are `order: "asc"`. Districts the source never covered sort last in both directions and are never presented as an extreme.
{ "type": "object", "required": [ "indicator" ], "properties": { "limit": { "type": "integer", "maximum": 100, "minimum": 1, "description": "How many districts to return. Defaults to 20." }, "order": { "enum": [ "asc", "desc" ], "type": "string", "description": "desc = highest value first. Defaults to desc." }, "scope": { "type": "string", "description": "A state name to rank within. Omit to rank every district of India." }, "indicator": { "type": "string", "description": "One indicator id from find_indicator." } }, "additionalProperties": false }arguments 31 linesfind_indicator reads unknown never probed
Use FIRST, before any other tool, whenever a question names a subject rather than an indicator id — "stunting", "land inequality", "bank credit". Returns matching indicator ids with their unit, source, vintage, caveat and district coverage. Every other tool needs an id from here; ids are not guessable and inventing one fails.
{ "type": "object", "required": [ "query" ], "properties": { "query": { "type": "string", "description": "Plain words describing the subject. Every word must appear somewhere in the indicator — prefer two or three words (\"child stunting\", \"land inequality\") over a sentence." } }, "additionalProperties": false }arguments 13 linescompare_districts reads unknown never probed
Use when the question names two or more places and asks how they differ — "compare Pune and Nagpur on literacy and bank credit". One call, not one get_district per district. Write an ambiguous name as "Bilaspur, Chhattisgarh".
{ "type": "object", "required": [ "districts", "indicators" ], "properties": { "districts": { "type": "array", "items": { "type": "string" }, "minItems": 2, "description": "District names, \"Name, State\" where a name repeats, or objectids." }, "indicators": { "type": "array", "items": { "type": "string" }, "minItems": 1, "description": "Indicator ids from find_indicator. At most 5." } }, "additionalProperties": false }arguments 26 linesbuild_map_link reads unknown never probed
Use to end an answer with a link the user can open — after any ranking, comparison or district lookup, and whenever they ask to see, map or visualise something. Returns a spatialindia.com/app URL showing exactly those indicators. One indicator draws a choropleth, two draw a bivariate map; a third cannot be expressed in a link and is reported back as dropped.
{ "type": "object", "required": [ "indicators" ], "properties": { "view": { "enum": [ "scatter", "ranking" ], "type": "string", "description": "Open the scatter plot or the ranking panel alongside the map." }, "state": { "type": "string", "description": "A state name to zoom the map to." }, "districts": { "type": "array", "items": { "type": "string" }, "description": "District names or objectids to pin. One district also opens its profile." }, "indicators": { "type": "array", "items": { "type": "string" }, "minItems": 1, "description": "One or two indicator ids. A third is dropped." } }, "additionalProperties": false }arguments 36 lines
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id95425f95a6598633.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/95425f95a6598633/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/95425f95a6598633?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.