publicdata.auVerified
Search, filter, count and sum Australian government open data, with every version kept.
GovernmentData access / search
- Passed: Handshake
- Passed: Tools listed
- Passed: Updated recently
Median latency 143 ms · Last checked
Explore
Evidence for your next connection.
Independent measurements of remote MCP servers. Every observation has a timestamp.
Read-only probesMCP server · Data access / search
District-level open data for India — Census, NFHS-5, NCRB, RBI and more, joined onto one geography.
1 failed · 8 not measured
Median of successful probes over 7 days
Share of countable probes over 30 days, including daily rollups. Auth challenges are excluded.
Tool definitions returned by this server
Independent monitoring
Responded
The server completed its last measured handshake. This is an observation, not a guarantee.
Last checked| Test area | Passed | Failed | Unmeasured |
|---|---|---|---|
ConnectionCan a client connect and discover tools? | 5 | 0 | 0 |
Reliability & speedDoes it respond consistently and quickly? | 0 | 0 | 4 |
Access & authenticationWhat is required to use this server? | 1 | 0 | 2 |
Tool qualityAre the tool definitions usable by an agent? | 4 | 0 | 0 |
Publisher identityCan the publisher be traced to its source? | 3 | 1 | 2 |
Unmeasured means there is not enough evidence to decide. How these checks work
Start using Spatial India
Choose your client, copy the configuration, then enable the server in your client’s MCP settings.
Run this command in your terminal, then restart Claude Code.
Claude Code
claude mcp add --transport http spatial-india https://api.spatialindia.com/mcpCapabilities
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.
DiscoveredUse 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".
DiscoveredUse 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.
DiscoveredUse 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`.
DiscoveredUse 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.
DiscoveredUse 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.
DiscoveredRecent measurements
| Checked | Result | Response | Tools |
|---|---|---|---|
| Connected | 71 ms | 6 |