io.github.iamvibhorsingh/bbox-mcp-server
NPM · BBOX-MCP-SERVER · SCANNED SEP 20
Geospatial toolkit for AI: spatial queries, coord conversion, H3, OSM search, map verification links
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 100 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- 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 44 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability62
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1397 tokens (~232/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 Management93
- Stability observed for 28 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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "search_overpass" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 6 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.iamvibhorsingh/bbox-mcp-server server?
io.github.iamvibhorsingh/bbox-mcp-server runs locally as an npm package, launched with npx -y bbox-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · bbox-mcp-server
claude mcp add iamvibhorsingh-bbox-mcp-server -- npx -y bbox-mcp-server
{
"mcpServers": {
"iamvibhorsingh-bbox-mcp-server": {
"command": "npx",
"args": [
"-y",
"bbox-mcp-server"
]
}
}
} {
"servers": {
"iamvibhorsingh-bbox-mcp-server": {
"command": "npx",
"args": [
"-y",
"bbox-mcp-server"
]
}
}
} codex mcp add iamvibhorsingh-bbox-mcp-server -- npx -y bbox-mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"iamvibhorsingh-bbox-mcp-server": {
"type": "local",
"command": [
"npx",
"-y",
"bbox-mcp-server"
],
"enabled": true
}
}
} openclaw mcp add iamvibhorsingh-bbox-mcp-server --command npx --arg -y --arg bbox-mcp-server
mcp_servers:
iamvibhorsingh-bbox-mcp-server:
command: "npx"
args: ["-y", "bbox-mcp-server"] {
"McpServers": {
"iamvibhorsingh-bbox-mcp-server": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"bbox-mcp-server"
]
}
}
} assistant mcp add iamvibhorsingh-bbox-mcp-server -t stdio -c npx -a -y bbox-mcp-server
{
"mcpServers": {
"iamvibhorsingh-bbox-mcp-server": {
"command": "npx",
"args": [
"-y",
"bbox-mcp-server"
]
}
}
} 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.
- 19 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.
- 17 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.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
- Security disclosure: unverified → fail ▼ functional
- 11 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
- 10 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.
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 20 Sept 2026 · Analysed npm/bbox-mcp-server@1.2.6
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 100 packages
| Packages resolved | 100 |
|---|---|
| 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 →
aggregate_overpass_h3 ~122
Executes an Overpass query and bins the results into H3 hexagons at a specified resolution to analyze spatial density.
| Name | Type | Req | Description |
|---|---|---|---|
| bbox | string | – | The bounding box geometry to parse. |
| location | string | – | A text location to search for (e.g. 'Seattle'). |
| query | string | yes | The Overpass QL core query (e.g. `nwr["amenity"="cafe"]`). |
| resolution | number | yes | The H3 resolution level (0-15) for binning. Default is 8. |
No output schema declared.
No examples provided.
generate_share_url ~88
Generates a URL that links to the visual Bounding Box tool to display these coordinates on a map. Supports WKT, GeoJSON, ogrinfo extent, and raw coordinate strings as input.
| Name | Type | Req | Description |
|---|---|---|---|
| bbox | string | yes | The geometry to parse. Can be a raw bounding box string ('lat1,lng1,lat2,lng2'), WKT, GeoJSON, or ogrinfo extent. |
No output schema declared.
No examples provided.
get_bounds ~371
Get converted coordinates for a bounding box or text location search. Supports parsing WKT, GeoJSON, ogrinfo extent, and raw coordinate strings. If MAPBOX_ACCESS_TOKEN is not set, you MUST provide explicit coordinates via 'bbox'.
| Name | Type | Req | Description |
|---|---|---|---|
| bbox | string | – | The geometry to parse. Can be a raw bounding box string ('lat1,lng1,lat2,lng2'), a WKT polygon/linestring/point, a GeoJSON payload, or an `ogrinfo` extent block. The Minimum Bounding Rectangle (MBR)… |
| coord_order | string | – | Toggle between 'lng,lat' (default) and 'lat,lng' coordinate ordering in the formatted output. Useful for APIs that expect swapped coordinate orders. |
| epsg | string | – | The projected EPSG code (e.g. '3857'). Defaults to '4326' (WGS84). Over 3,900 bundled projections; unknown codes are auto-fetched from epsg.io. |
| format | string | – | Format of the output. Options: wkt, geojson-bbox, leaflet, overpass, ogc-bbox, kml, geojson-polygon, csv, stac-bbox. Default: csv. |
| location | string | – | A text location to search for (e.g. 'New York City'). Requires MAPBOX_ACCESS_TOKEN env var. Either 'location' or 'bbox' MUST be provided. |
| precision | number | – | The number of decimal places to output coordinate strings as (defaults to 6). |
| zoom | number | – | The map zoom level (0-22) used to calculate the map tile coordinates for the centroid. Defaults to 15. |
No output schema declared.
No examples provided.
get_h3_indices ~221
Get Uber H3 cell indices for a bounding box area at a target resolution. Input supports WKT, GeoJSON, ogrinfo extent, and raw coordinate strings.
| Name | Type | Req | Description |
|---|---|---|---|
| bbox | string | – | The geometry to parse. Can be a raw bounding box string ('lat1,lng1,lat2,lng2'), WKT, GeoJSON, or ogrinfo extent. Either 'location' or 'bbox' MUST be provided. |
| compact | boolean | – | Whether to return a compacted list of cells (mixing resolutions) to minimize response size. Defaults to false. |
| location | string | – | A text location to search for (e.g. 'San Francisco'). Requires MAPBOX_ACCESS_TOKEN env var. Either 'location' or 'bbox' MUST be provided. |
| resolution | number | yes | The H3 resolution level, from 0 to 15. (e.g. 7) |
| return_geometry | boolean | – | If true, return GeoJSON FeatureCollection with hex boundary polygons in addition to cell IDs. Defaults to false. |
No output schema declared.
No examples provided.
list_osm_tags ~71
Discovery tool to look up the correct OpenStreetMap tags for a given category. Helps prevent hallucinating incorrect tags before writing an Overpass query.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | Broad category to look up (e.g. 'food', 'health', 'transport', 'leisure', 'retail'). |
No output schema declared.
No examples provided.
search_overpass ~524
Execute an Overpass QL query to find POIs, roads, or other OSM features within a bounding box or radius. The server wraps your query in the appropriate spatial filter and returns structured JSON with a map link. SEARCH MODES: - Bounding box (default): searches a rectangular area. Use for region/area queries ('hospitals in Manhattan', 'parks in downtown Seattle'). - Circle: searches within an exact radius. Use ONLY when the user specifies an explicit distance ('within 2km of JFK', '500 metres from the Eiffel Tower', '1 mile from Times Square'). Omit radius_meters for vague terms like 'near' or 'close to'. COMMON TAG EXAMPLES: - Restaurants: `nwr["amenity"="restaurant"]` - Pizza: `nwr["amenity"="fast_food"]["cuisine"="pizza"]` - Supermarkets: `nwr["shop"="supermarket"]` - Parks: `nwr["leisure"="park"]` - Hospitals: `nwr["amenity"="hospital"]` - Schools: `nwr["amenity"="school"]` - Parking: `nwr["amenity"="parking"]` - Highways/Roads: `way["highway"]`
| Name | Type | Req | Description |
|---|---|---|---|
| bbox | string | – | The geometry to parse. Can be a raw bounding box string ('lat1,lng1,lat2,lng2'), WKT, GeoJSON, or ogrinfo extent. Either 'location' or 'bbox' MUST be provided. |
| limit | number | – | Maximum number of elements to return. Default is 100. Increase if you need more results. |
| location | string | – | A text location to search for (e.g. 'San Francisco', 'JFK Airport'). Requires MAPBOX_ACCESS_TOKEN env var. Either 'location' or 'bbox' MUST be provided. |
| query | string | yes | The Overpass QL core query. Example: `node["amenity"="cafe"]` or `nwr["leisure"="park"]`. DO NOT include spatial filters, bounding box, or output directives — the server handles those automatically. |
| radius_meters | number | – | Search radius in metres. Enables circle mode — use ONLY when the user specifies an explicit distance (e.g. '2km' → 2000, '500 metres' → 500, '1 mile' → 1609). Omit entirely for area/region queries or… |
No output schema declared.
No examples provided.
What is the io.github.iamvibhorsingh/bbox-mcp-server server?
io.github.iamvibhorsingh/bbox-mcp-server is listed in the public MCP registry as io.github.iamvibhorsingh/bbox-mcp-server. Geospatial toolkit for AI: spatial queries, coord conversion, H3, OSM search, map verification links. This page covers its npm package (bbox-mcp-server).
Is the io.github.iamvibhorsingh/bbox-mcp-server server safe to use?
io.github.iamvibhorsingh/bbox-mcp-server scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 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.iamvibhorsingh/bbox-mcp-server server expose?
io.github.iamvibhorsingh/bbox-mcp-server exposes 6 tools: get_bounds, get_h3_indices, generate_share_url, search_overpass, list_osm_tags, aggregate_overpass_h3. Their descriptions and schemas cost roughly 1,397 tokens of context every time the server is loaded.
Is the io.github.iamvibhorsingh/bbox-mcp-server server still maintained?
io.github.iamvibhorsingh/bbox-mcp-server is still listed as active in the MCP registry. We last reached this channel on 20 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.iamvibhorsingh/bbox-mcp-server server under?
io.github.iamvibhorsingh/bbox-mcp-server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.