io.github.urbanmorph/bharatlas-mcp
NPM · BHARATLAS-MCP · SCANNED SEP 25
Query India's open geo data. Locate, filter, nearby search across layers.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 35 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2076 tokens (~259/item across 8 items; 8 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 Management83
- Stability observed for 25 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.urbanmorph/bharatlas-mcp server?
io.github.urbanmorph/bharatlas-mcp runs locally as an npm package, launched with npx -y bharatlas-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · bharatlas-mcp
claude mcp add urbanmorph-bharatlas-mcp -- npx -y bharatlas-mcp
{
"mcpServers": {
"urbanmorph-bharatlas-mcp": {
"command": "npx",
"args": [
"-y",
"bharatlas-mcp"
]
}
}
} {
"servers": {
"urbanmorph-bharatlas-mcp": {
"command": "npx",
"args": [
"-y",
"bharatlas-mcp"
]
}
}
} codex mcp add urbanmorph-bharatlas-mcp -- npx -y bharatlas-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"urbanmorph-bharatlas-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"bharatlas-mcp"
],
"enabled": true
}
}
} openclaw mcp add urbanmorph-bharatlas-mcp --command npx --arg -y --arg bharatlas-mcp
mcp_servers:
urbanmorph-bharatlas-mcp:
command: "npx"
args: ["-y", "bharatlas-mcp"] {
"McpServers": {
"urbanmorph-bharatlas-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"bharatlas-mcp"
]
}
}
} assistant mcp add urbanmorph-bharatlas-mcp -t stdio -c npx -a -y bharatlas-mcp
{
"mcpServers": {
"urbanmorph-bharatlas-mcp": {
"command": "npx",
"args": [
"-y",
"bharatlas-mcp"
]
}
}
} 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.
- 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
- 24 Sept 26 −3
- Stability: pass → 0.80 functional
- 23 Sept 26 +1
- Stability: 0.97 → pass security
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 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 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 +1
- Stability: 0.97 → pass security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 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 25 Sept 2026 · Analysed npm/bharatlas-mcp@1.0.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
get_layer_detail ~56
Get full metadata for a single layer: download URLs (parquet, pmtiles, geojson, kml, shapefile), attribution, license, feature count, and level metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| layer_id | string | yes | Layer ID |
No output schema declared.
No examples provided.
get_layer_schema ~73
Get column names, types, and sample values for a layer. Use BEFORE querying to discover what columns exist and what values they contain. Essential for knowing the right column names for filters.
| Name | Type | Req | Description |
|---|---|---|---|
| layer_id | string | yes | Layer ID (e.g. lgd_states, airports, soi_forests, wards_chennai) |
No output schema declared.
No examples provided.
list_categories ~16
List all data categories with layer counts.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_layers ~204
List available geo layers. Use to discover what data bharatlas has. Returns layer IDs, names, row counts, categories, and download formats. Filter by category (boundaries, city-wards, environment, water, agriculture, transport, etc.), admin level (state, district, block, village, etc.), source, or text search.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Filter by category: boundaries, city-wards, people, environment, water, agriculture, transport, infrastructure, health-edu |
| level | string | – | Filter by admin level: state, district, subdistrict, block, village, etc. |
| limit | number | – | Max results (default 20) |
| offset | number | – | Skip N results for pagination |
| q | string | – | Text search across layer IDs, sources, and descriptions |
| source | string | – | Filter by data source: LGD, SOI, Bhuvan, OpenCity, DataMeet, etc. |
No output schema declared.
No examples provided.
list_submissions ~90
List community-submitted geo layers. These are user-contributed datasets under open licenses. Filter by category or search by name.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Filter by category |
| limit | number | – | Max results (default 20) |
| offset | number | – | Pagination offset |
| q | string | – | Search name and description |
| sort | string | – | Sort order (default: recent) |
No output schema declared.
No examples provided.
locate ~129
Given a latitude/longitude, find which administrative boundaries, zones, and regions contain that point. Returns state, district, subdistrict, block, parliament/assembly constituency, pincode, seismic zone, high court jurisdiction, and more. The 'where am I?' tool. Also accepts specific layer IDs to check.
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | yes | Latitude (6 to 38, India bounding box) |
| layers | array | – | Specific layer IDs to check (default: 12 essential layers covering all admin levels + zones) |
| lng | number | yes | Longitude (68 to 98, India bounding box) |
No output schema declared.
No examples provided.
nearby ~167
Find features from a layer that are near a given point. Samples a grid of points around the center and checks which hit the target layer via locate. Generic: works for any layer type (polygons, points, lines) without needing coordinate columns. Example: 'reservoirs near Bengaluru' -> layer_id: 'wris_reservoirs', lat: 12.97, lng: 77.59, radius_km: 50.
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | yes | Center point latitude |
| layer_id | string | yes | Layer to search for nearby features |
| limit | number | – | Max results (default 20) |
| lng | number | yes | Center point longitude |
| radius_km | number | – | Search radius in kilometres (default 25, max 200) |
No output schema declared.
No examples provided.
query_layer ~225
Query a layer's data with filters and grouping. Reads the parquet file at runtime. Supports: select specific columns, filter by column values, group by a column to get counts. Use get_layer_schema first to discover column names. Examples: 'airports in Karnataka' -> where: {state: 'KA'}, 'forest types' -> group_by: 'type', 'health facilities in Bihar' -> where: {state: 'BIHAR'}, select: ['name', 'type'].
| Name | Type | Req | Description |
|---|---|---|---|
| group_by | string | – | Column to group by. Returns {value: count} instead of rows. |
| include_centroid | boolean | – | Include _lat/_lng centroid coordinates (defaults to true). Set false to exclude. |
| layer_id | string | yes | Layer ID to query |
| limit | number | – | Max rows (default 100, max 1000) |
| select | array | – | Column names to return. Omit for all non-geometry columns. |
| where | object | – | Filter conditions as {column: value} pairs. Case-insensitive matching. |
No output schema declared.
No examples provided.
What is the io.github.urbanmorph/bharatlas-mcp server?
io.github.urbanmorph/bharatlas-mcp is listed in the public MCP registry as io.github.urbanmorph/bharatlas-mcp. Query India's open geo data. Locate, filter, nearby search across layers. This page covers its npm package (bharatlas-mcp).
Is the io.github.urbanmorph/bharatlas-mcp server safe to use?
io.github.urbanmorph/bharatlas-mcp scores 75 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 2026. It declares no install or post-install scripts. 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 io.github.urbanmorph/bharatlas-mcp server expose?
io.github.urbanmorph/bharatlas-mcp exposes 8 tools: list_layers, get_layer_schema, query_layer, locate, nearby, and 3 more. Their descriptions and schemas cost roughly 960 tokens of context every time the server is loaded.
Is the io.github.urbanmorph/bharatlas-mcp server still maintained?
io.github.urbanmorph/bharatlas-mcp is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.urbanmorph/bharatlas-mcp server under?
io.github.urbanmorph/bharatlas-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.