MyStreetData USA
REMOTE · MYSTREETDATA.COM
Read-only search and contextual metrics for 1.33M street records across 8 US states.
Available components
Last scanned (20 hours ago)
Scores higher than 57% of remote servers
Reachable. Last reached 18 Oct 2026.
Category Maps and Location
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. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability60
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 419 tokens (~83/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 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
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.
- 17 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 16 Oct 26 66
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 18 Oct 2026 · Probed https://mystreetdata.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mystreetdata.com | CN=YE1,O=Let's Encrypt,C=US | 23 Sept 2026 | 22 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 59fd991818789806c38e2b89944a65b1d6d |
| SANs: *.mystreetdata.com, mystreetdata.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mystreetdata.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| mystreetdata.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| content-security-policy | default-src 'none'; style-src 'self'; frame-ancestors 'none'; base-uri 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mystreetdata.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://mystreetdata.com/api/mcp | HTTPS enforced | 301 | https://mystreetdata.com/api/mcp |
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 →
mystreetdata_compare_streets Compare street context ~60
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.
| Name | Type | Req | Description |
|---|---|---|---|
| dimensions | array | – | – |
| street_ids | array | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| calculated_at | string | yes | – |
| data_version | string | yes | – |
| error | object | – | – |
| limitations | array | yes | – |
| responded_at | string | yes | – |
| result | object | – | – |
| schema_version | string | yes | – |
| sources | array | yes | – |
| status | string | yes | – |
No examples provided.
mystreetdata_get_coverage MyStreetData coverage ~63
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.
| Name | Type | Req | Description |
|---|---|---|---|
| area_id | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| calculated_at | string | yes | – |
| data_version | string | yes | – |
| error | object | – | – |
| limitations | array | yes | – |
| responded_at | string | yes | – |
| result | object | – | – |
| schema_version | string | yes | – |
| sources | array | yes | – |
| status | string | yes | – |
No examples provided.
mystreetdata_get_street_context Street context ~65
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.
| Name | Type | Req | Description |
|---|---|---|---|
| dimensions | array | – | – |
| street_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| calculated_at | string | yes | – |
| data_version | string | yes | – |
| error | object | – | – |
| limitations | array | yes | – |
| responded_at | string | yes | – |
| result | object | – | – |
| schema_version | string | yes | – |
| sources | array | yes | – |
| status | string | yes | – |
No examples provided.
mystreetdata_search_areas Find a site area ~69
Find a city, county or metro grouping by name; select the state-qualified area_id. Site areas are not guaranteed municipal boundaries. Prefix search.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | – |
| limit | integer | – | – |
| query | string | yes | – |
| state | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| calculated_at | string | yes | – |
| data_version | string | yes | – |
| error | object | – | – |
| limitations | array | yes | – |
| responded_at | string | yes | – |
| result | object | – | – |
| schema_version | string | yes | – |
| sources | array | yes | – |
| status | string | yes | – |
No examples provided.
mystreetdata_search_streets Find a street ~79
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.
| Name | Type | Req | Description |
|---|---|---|---|
| area_id | string | yes | – |
| cursor | string | – | – |
| limit | integer | – | – |
| query | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| calculated_at | string | yes | – |
| data_version | string | yes | – |
| error | object | – | – |
| limitations | array | yes | – |
| responded_at | string | yes | – |
| result | object | – | – |
| schema_version | string | yes | – |
| sources | array | yes | – |
| status | string | yes | – |
No examples provided.
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.
remote · mystreetdata.com
claude mcp add --transport http habanacasta88-mystreetdata 'https://mystreetdata.com/api/mcp'
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.