# MyStreetData USA (remote · mystreetdata.com)

Read-only search and contextual metrics for 1.33M street records across 8 US states.

- Trust score: 67/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-18

## Components

- remote · `mystreetdata.com`: 67/100 (this document), [markdown](https://verifymcp.io/servers/habanacasta88-mystreetdata/api-mcp.md), [page](https://verifymcp.io/servers/habanacasta88-mystreetdata/api-mcp)

## Channel facts

- Endpoint: `https://mystreetdata.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-10-18.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 60/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 419 tokens (~83/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 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.

## Install

### How do I install the MyStreetData USA MCP server?

MyStreetData USA is a hosted endpoint at https://mystreetdata.com/api/mcp, so there is nothing to install locally. 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 --transport http habanacasta88-mystreetdata 'https://mystreetdata.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "habanacasta88-mystreetdata": {
      "url": "https://mystreetdata.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "habanacasta88-mystreetdata": {
      "type": "http",
      "url": "https://mystreetdata.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.habanacasta88-mystreetdata]
url = "https://mystreetdata.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "habanacasta88-mystreetdata": {
      "type": "remote",
      "url": "https://mystreetdata.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add habanacasta88-mystreetdata --url 'https://mystreetdata.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  habanacasta88-mystreetdata:
    url: "https://mystreetdata.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "habanacasta88-mystreetdata": {
      "Transport": "http",
      "Url": "https://mystreetdata.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add habanacasta88-mystreetdata -t streamable-http -u 'https://mystreetdata.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "habanacasta88-mystreetdata": {
      "type": "http",
      "url": "https://mystreetdata.com/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-17 (score 67, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-16 (score 66)

First indexed and scored.

## MCP tools (5)

### `mystreetdata_get_coverage` (~63 tokens)

MyStreetData coverage

Dataset version, included states and site-area coverage. This is the site catalogue, not all United States streets. Publication verification means an origin HTML file existed at snapshot time; not a claim of indexing or current freshness.

Input parameters:

- `area_id` (string)

Output parameters:

- `calculated_at` (string)
- `data_version` (string)
- `error` (object)
- `limitations` (array)
- `responded_at` (string)
- `result` (object)
- `schema_version` (string)
- `sources` (array)
- `status` (string)

### `mystreetdata_search_areas` (~69 tokens)

Find a site area

Find a city, county or metro grouping by name; select the state-qualified area_id. Site areas are not guaranteed municipal boundaries. Prefix search.

Input parameters:

- `cursor` (string)
- `limit` (integer)
- `query` (string, required)
- `state` (string)

Output parameters:

- `calculated_at` (string)
- `data_version` (string)
- `error` (object)
- `limitations` (array)
- `responded_at` (string)
- `result` (object)
- `schema_version` (string)
- `sources` (array)
- `status` (string)

### `mystreetdata_search_streets` (~79 tokens)

Find a street

Find streets by name prefix in one state-qualified site area. Distinguishes ZIPs and persistent IDs. Use search_areas first. Never treats a supplied URL as a fetch target.

Input parameters:

- `area_id` (string, required)
- `cursor` (string)
- `limit` (integer)
- `query` (string, required)

Output parameters:

- `calculated_at` (string)
- `data_version` (string)
- `error` (object)
- `limitations` (array)
- `responded_at` (string)
- `result` (object)
- `schema_version` (string)
- `sources` (array)
- `status` (string)

### `mystreetdata_get_street_context` (~65 tokens)

Street context

EPA block-group walkability and observed SNAP retailers/EV station counts near the street centroid, with period, scale and missing-data status. Not a home, safety or live availability assessment.

Input parameters:

- `dimensions` (array)
- `street_id` (string, required)

Output parameters:

- `calculated_at` (string)
- `data_version` (string)
- `error` (object)
- `limitations` (array)
- `responded_at` (string)
- `result` (object)
- `schema_version` (string)
- `sources` (array)
- `status` (string)

### `mystreetdata_compare_streets` (~60 tokens)

Compare street context

Side-by-side contextual measurements for 2–5 distinct IDs. No overall score, ranking or recommendation. Interpret each source period, scale and missing value separately.

Input parameters:

- `dimensions` (array)
- `street_ids` (array, required)

Output parameters:

- `calculated_at` (string)
- `data_version` (string)
- `error` (object)
- `limitations` (array)
- `responded_at` (string)
- `result` (object)
- `schema_version` (string)
- `sources` (array)
- `status` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/habanacasta88-mystreetdata/api-mcp#diagnostics

## Score history

- 2026-10-18: 67
- 2026-10-17: 67
- 2026-10-16: 66

## Common questions

### What is the MyStreetData USA MCP server?

MyStreetData USA is an MCP server listed in the public MCP registry as io.github.Habanacasta88/mystreetdata. Read-only search and contextual metrics for 1.33M street records across 8 US states. This page covers its hosted endpoint (https://mystreetdata.com/api/mcp).

### Is the MyStreetData USA MCP server safe to use?

MyStreetData USA scores 67 out of 100 on VerifyMCP. 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 MyStreetData USA MCP server expose?

MyStreetData USA exposes 5 tools: mystreetdata_get_coverage, mystreetdata_search_areas, mystreetdata_search_streets, mystreetdata_get_street_context, mystreetdata_compare_streets. Their descriptions and schemas cost roughly 336 tokens of context every time the server is loaded.

### Does the MyStreetData USA MCP server require authentication?

No. We connected to MyStreetData USA without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the MyStreetData USA MCP server still maintained?

MyStreetData USA is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mystreetdata.com/api/mcp
- Website: https://mystreetdata.com/mcp/
- Changelog RSS feed: https://verifymcp.io/servers/habanacasta88-mystreetdata/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/habanacasta88-mystreetdata/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/habanacasta88-mystreetdata/api-mcp