io.github.CloudCorpRecords/streetmap-port
NPM · @RENETURCIOS/STREETMAP-PORT · 2 COMPONENTS
Geocode, reverse geocode and find nearby places with the public OpenStreetMap APIs.
Available components
Last scanned (3 hours ago)
Scores higher than 32% of npm servers
Category Maps and Location
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 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 5 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 606 tokens (~101/item across 6 items; 6 tools + 0 resources), lean.Pass
- 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
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 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
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.
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.
- 31 Oct 26 65
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 5 Nov 2026 · Analysed npm/@reneturcios/streetmap-port@0.1.0
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 →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| 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 →
distance_between ~126
Compute the great-circle distance in kilometres between two coordinate pairs (local, no API call)
| Name | Type | Req | Description |
|---|---|---|---|
| from_latitude | number | yes | Latitude in decimal degrees, from -90 to 90, of the starting point. |
| from_longitude | number | yes | Longitude in decimal degrees, from -180 to 180, of the starting point. |
| to_latitude | number | yes | Latitude in decimal degrees, from -90 to 90, of the destination point. |
| to_longitude | number | yes | Longitude in decimal degrees, from -180 to 180, of the destination point. |
No output schema declared.
No examples provided.
find_nearby ~172
Find places of a category near coordinates via the OSM Overpass API
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional bare OpenStreetMap tag key (letters and underscores only, for example 'amenity') whose tagged nodes to find nearby; defaults to 'amenity'. |
| latitude | number | yes | Latitude in decimal degrees, from -90 to 90, of the centre point to search around. |
| limit | number | – | Optional maximum number of nearby places to return; defaults to 20 and is clamped to 1-100. |
| longitude | number | yes | Longitude in decimal degrees, from -180 to 180, of the centre point to search around. |
| radius | number | – | Optional search radius in metres around the coordinates; defaults to 1000 and must be greater than 0. |
No output schema declared.
No examples provided.
geocode_address ~78
Geocode a free-form address or place name to coordinates via the OSM Nominatim API
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Optional maximum number of geocoding results to return; defaults to 5 and is clamped to 1-50. |
| query | string | yes | Free-form address or place name to geocode to coordinates. |
No output schema declared.
No examples provided.
get_place_details ~82
Get details of one OSM object (node, way or relation) via the Nominatim lookup API
| Name | Type | Req | Description |
|---|---|---|---|
| osm_id | number | yes | Numeric OpenStreetMap identifier of the object to look up; must be non-negative. |
| osm_type | string | yes | Type of OpenStreetMap object to look up: 'node', 'way', or 'relation'. |
No output schema declared.
No examples provided.
reverse_geocode ~78
Reverse geocode coordinates to the nearest address via the OSM Nominatim API
| Name | Type | Req | Description |
|---|---|---|---|
| latitude | number | yes | Latitude in decimal degrees, from -90 to 90, of the point to reverse geocode. |
| longitude | number | yes | Longitude in decimal degrees, from -180 to 180, of the point to reverse geocode. |
No output schema declared.
No examples provided.
search_places ~70
Search for places by name via the OSM Nominatim API
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Optional maximum number of place results to return; defaults to 10 and is clamped to 1-50. |
| query | string | yes | Place name or search text to look up via Nominatim. |
No output schema declared.
No examples provided.
How do I install the io.github.CloudCorpRecords/streetmap-port MCP server?
io.github.CloudCorpRecords/streetmap-port runs locally as an npm package, launched with npx -y @reneturcios/streetmap-port. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @reneturcios/streetmap-port
claude mcp add cloudcorprecords-streetmap-port -- npx -y @reneturcios/streetmap-port
What is the io.github.CloudCorpRecords/streetmap-port MCP server?
io.github.CloudCorpRecords/streetmap-port is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/streetmap-port. Geocode, reverse geocode and find nearby places with the public OpenStreetMap APIs. This page covers its npm package (@reneturcios/streetmap-port).
Is the io.github.CloudCorpRecords/streetmap-port MCP server safe to use?
io.github.CloudCorpRecords/streetmap-port scores 65 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 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.CloudCorpRecords/streetmap-port MCP server expose?
io.github.CloudCorpRecords/streetmap-port exposes 6 tools: geocode_address, reverse_geocode, search_places, find_nearby, get_place_details, distance_between. Their descriptions and schemas cost roughly 606 tokens of context every time the server is loaded.
Is the io.github.CloudCorpRecords/streetmap-port MCP server still maintained?
io.github.CloudCorpRecords/streetmap-port is still listed as active in the MCP registry. We last reached this channel on 5 November 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.CloudCorpRecords/streetmap-port MCP server under?
io.github.CloudCorpRecords/streetmap-port declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.