Spatial India
REMOTE · API.SPATIALINDIA.COM · SCANNED OCT 1
District-level open data for India — Census, NFHS-5, NCRB, RBI and more, joined onto one geography.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 924 tokens (~154/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the Spatial India MCP server?
Spatial India is a hosted endpoint at https://api.spatialindia.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.spatialindia.com
claude mcp add --transport http com-spatialindia-spatial-india 'https://api.spatialindia.com/mcp'
{
"mcpServers": {
"com-spatialindia-spatial-india": {
"url": "https://api.spatialindia.com/mcp"
}
}
} {
"servers": {
"com-spatialindia-spatial-india": {
"type": "http",
"url": "https://api.spatialindia.com/mcp"
}
}
} [mcp_servers.com-spatialindia-spatial-india] url = "https://api.spatialindia.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-spatialindia-spatial-india": {
"type": "remote",
"url": "https://api.spatialindia.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-spatialindia-spatial-india --url 'https://api.spatialindia.com/mcp' --transport streamable-http
mcp_servers:
com-spatialindia-spatial-india:
url: "https://api.spatialindia.com/mcp" {
"McpServers": {
"com-spatialindia-spatial-india": {
"Transport": "http",
"Url": "https://api.spatialindia.com/mcp"
}
}
} assistant mcp add com-spatialindia-spatial-india -t streamable-http -u 'https://api.spatialindia.com/mcp'
{
"mcpServers": {
"com-spatialindia-spatial-india": {
"type": "http",
"url": "https://api.spatialindia.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 29 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 +7
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 1 Oct 2026 · Probed https://api.spatialindia.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=spatialindia.com | CN=WE1,O=Google Trust Services,C=US | 9 Aug 2026 | 8 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | e8cc8dca29a2c4e1135e728dd612e0bd |
| SANs: spatialindia.com, *.spatialindia.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.spatialindia.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| spatialindia.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.spatialindia.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.spatialindia.com/mcp | HTTPS enforced | 301 | https://api.spatialindia.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
build_map_link Build a map link ~157
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.
| Name | Type | Req | Description |
|---|---|---|---|
| districts | array | – | District names or objectids to pin. One district also opens its profile. |
| indicators | array | yes | One or two indicator ids. A third is dropped. |
| state | string | – | A state name to zoom the map to. |
| view | string | – | Open the scatter plot or the ranking panel alongside the map. |
No output schema declared.
No examples provided.
compare_districts Compare districts ~103
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".
| Name | Type | Req | Description |
|---|---|---|---|
| districts | array | yes | District names, "Name, State" where a name repeats, or objectids. |
| indicators | array | yes | Indicator ids from find_indicator. At most 5. |
No output schema declared.
No examples provided.
find_indicator Find an indicator ~117
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
get_district Get one district ~171
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`.
| Name | Type | Req | Description |
|---|---|---|---|
| indicators | array | – | 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. |
| name | string | yes | District name, an alternative spelling, or an objectid. |
| state | string | – | State name. Supply this only to disambiguate a repeated district name. |
No output schema declared.
No examples provided.
get_methodology Get methodology and citation ~125
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.
| Name | Type | Req | Description |
|---|---|---|---|
| indicator | string | – | An indicator id. Omit for the dataset-wide vintage, sources and citation. |
No output schema declared.
No examples provided.
rank_districts Rank districts ~174
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.
| Name | Type | Req | Description |
|---|---|---|---|
| indicator | string | yes | One indicator id from find_indicator. |
| limit | integer | – | How many districts to return. Defaults to 20. |
| order | string | – | desc = highest value first. Defaults to desc. |
| scope | string | – | A state name to rank within. Omit to rank every district of India. |
No output schema declared.
No examples provided.
What is the Spatial India MCP server?
Spatial India is an MCP server listed in the public MCP registry as com.spatialindia/spatial-india. District-level open data for India, Census, NFHS-5, NCRB, RBI and more, joined onto one geography. This page covers its hosted endpoint (https://api.spatialindia.com/mcp).
Is the Spatial India MCP server safe to use?
Spatial India scores 82 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Spatial India MCP server expose?
Spatial India exposes 6 tools: find_indicator, get_district, compare_districts, rank_districts, get_methodology, build_map_link. Their descriptions and schemas cost roughly 847 tokens of context every time the server is loaded.
Does the Spatial India MCP server require authentication?
No. We connected to Spatial India without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Spatial India MCP server still maintained?
Spatial India is still listed as active in the MCP registry. We last reached this channel on 1 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.