Search arXiv papers, download full text, semantic search, citation graphs, and alerts via MCP.
Spatial India is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
District-level open data for India — Census, NFHS-5, NCRB, RBI and more, joined onto one geography.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http spatial-india-mcp https://api.spatialindia.com/mcp
# 2 — ask your agent for something these tools do
# find_indicator, get_district, compare_districts and 3 more
Spatial India costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http spatial-india-mcp https://api.spatialindia.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
6 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | 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. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | District name, an alternative spelling, or an objectid. |
| state | string | no | State name. Supply this only to disambiguate a repeated district name. |
| indicators | array | no | 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. |
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".
| Parameter | Type | Required | Notes |
|---|---|---|---|
| districts | array | yes | District names, "Name, State" where a name repeats, or objectids. |
| indicators | array | yes | Indicator ids from find_indicator. At most 5. |
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 present
| Parameter | Type | Required | Notes |
|---|---|---|---|
| indicator | string | yes | One indicator id from find_indicator. |
| scope | string | no | A state name to rank within. Omit to rank every district of India. |
| order | string | no | desc = highest value first. Defaults to desc. |
| limit | integer | no | How many districts to return. Defaults to 20. |
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 chec
| Parameter | Type | Required | Notes |
|---|---|---|---|
| indicator | string | no | An indicator id. Omit for the dataset-wide vintage, sources and citation. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| indicators | array | yes | One or two indicator ids. A third is dropped. |
| state | string | no | A state name to zoom the map to. |
| districts | array | no | District names or objectids to pin. One district also opens its profile. |
| view | string | no | Open the scatter plot or the ranking panel alongside the map. |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Spatial India or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Spatial India can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.