# io.github.CloudCorpRecords/streetmap-port (npm · @reneturcios/streetmap-port)

Geocode, reverse geocode and find nearby places with the public OpenStreetMap APIs.

- Trust score: 65/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `@reneturcios/streetmap-port`: 65/100 (this document), [markdown](https://verifymcp.io/servers/cloudcorprecords-streetmap-port/reneturcios-streetmap-port.md), [page](https://verifymcp.io/servers/cloudcorprecords-streetmap-port/reneturcios-streetmap-port)
- oci · `ghcr.io/cloudcorprecords/streetmap-port`: 43/100, [markdown](https://verifymcp.io/servers/cloudcorprecords-streetmap-port/ghcr-io-cloudcorprecords-streetmap-port.md), [page](https://verifymcp.io/servers/cloudcorprecords-streetmap-port/ghcr-io-cloudcorprecords-streetmap-port)

## Channel facts

- Registry: `npm`
- Package: `@reneturcios/streetmap-port`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 81/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available.
  - No install/post-install scripts declared.
  - 30 of 93 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 5 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 606 tokens (~101/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**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.

## Install

### 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.

### Claude

```bash
claude mcp add cloudcorprecords-streetmap-port -- npx -y @reneturcios/streetmap-port
```

### Cursor

```json
{
  "mcpServers": {
    "cloudcorprecords-streetmap-port": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/streetmap-port"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cloudcorprecords-streetmap-port": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/streetmap-port"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add cloudcorprecords-streetmap-port -- npx -y @reneturcios/streetmap-port
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cloudcorprecords-streetmap-port": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@reneturcios/streetmap-port"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add cloudcorprecords-streetmap-port --command npx --arg -y --arg @reneturcios/streetmap-port
```

### Hermes

```yaml
mcp_servers:
  cloudcorprecords-streetmap-port:
    command: "npx"
    args: ["-y", "@reneturcios/streetmap-port"]
```

### Netclaw

```json
{
  "McpServers": {
    "cloudcorprecords-streetmap-port": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@reneturcios/streetmap-port"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add cloudcorprecords-streetmap-port -t stdio -c npx -a -y @reneturcios/streetmap-port
```

### Other

```json
{
  "mcpServers": {
    "cloudcorprecords-streetmap-port": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/streetmap-port"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-31 (score 65)

First indexed and scored.

## MCP tools (6)

### `geocode_address` (~78 tokens)

Geocode a free-form address or place name to coordinates via the OSM Nominatim API

Input parameters:

- `limit` (number): Optional maximum number of geocoding results to return; defaults to 5 and is clamped to 1-50.
- `query` (string, required): Free-form address or place name to geocode to coordinates.

### `reverse_geocode` (~78 tokens)

Reverse geocode coordinates to the nearest address via the OSM Nominatim API

Input parameters:

- `latitude` (number, required): Latitude in decimal degrees, from -90 to 90, of the point to reverse geocode.
- `longitude` (number, required): Longitude in decimal degrees, from -180 to 180, of the point to reverse geocode.

### `search_places` (~70 tokens)

Search for places by name via the OSM Nominatim API

Input parameters:

- `limit` (number): Optional maximum number of place results to return; defaults to 10 and is clamped to 1-50.
- `query` (string, required): Place name or search text to look up via Nominatim.

### `find_nearby` (~172 tokens)

Find places of a category near coordinates via the OSM Overpass API

Input parameters:

- `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, required): 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, required): 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.

### `get_place_details` (~82 tokens)

Get details of one OSM object (node, way or relation) via the Nominatim lookup API

Input parameters:

- `osm_id` (number, required): Numeric OpenStreetMap identifier of the object to look up; must be non-negative.
- `osm_type` (string, required): Type of OpenStreetMap object to look up: 'node', 'way', or 'relation'.

### `distance_between` (~126 tokens)

Compute the great-circle distance in kilometres between two coordinate pairs (local, no API call)

Input parameters:

- `from_latitude` (number, required): Latitude in decimal degrees, from -90 to 90, of the starting point.
- `from_longitude` (number, required): Longitude in decimal degrees, from -180 to 180, of the starting point.
- `to_latitude` (number, required): Latitude in decimal degrees, from -90 to 90, of the destination point.
- `to_longitude` (number, required): Longitude in decimal degrees, from -180 to 180, of the destination point.

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/cloudcorprecords-streetmap-port/reneturcios-streetmap-port#diagnostics

## Score history

- 2026-11-05: 65
- 2026-11-04: 65
- 2026-11-03: 65
- 2026-11-02: 65
- 2026-11-01: 65
- 2026-10-31: 65

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/@reneturcios/streetmap-port
- Socket report: https://socket.dev/npm/package/@reneturcios/streetmap-port
- Repository: https://github.com/CloudCorpRecords/streetmap-port
- Changelog RSS feed: https://verifymcp.io/servers/cloudcorprecords-streetmap-port/reneturcios-streetmap-port.xml
- Changelog JSON feed: https://verifymcp.io/servers/cloudcorprecords-streetmap-port/reneturcios-streetmap-port.json
- HTML version of this page: https://verifymcp.io/servers/cloudcorprecords-streetmap-port/reneturcios-streetmap-port