io.github.iamvibhorsingh/bbox-mcp-server
NPM · BBOX-MCP-SERVER · SCANNED AUG 3
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 →
Supply Chain Security88
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (99 of 103), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (99 of 103), so this covers what we could see, not the whole tree. 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 84 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability57
- 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · bbox-mcp-server
claude mcp add iamvibhorsingh-bbox-mcp-server -- npx -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": {
"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.
- 2 Aug 26 +44
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Maintenance: unverified → pass ▲ functional
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → good ▲ functional
- Licence: MIT functional
- 31 Jul 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
- 30 Jul 26 −18
- Malware scan: pass → unverified ▼ security
- 27 Jul 26 43
First indexed and scored.
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 3 Aug 2026 · Analysed npm/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 99 packages
99 packages in the resolved dependency tree · 94 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
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.