atx/registry

portlandmaps-mcp.vercel.app/mcp/v2

https://portlandmaps-mcp.vercel.app/mcp/v2

61
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 1d ago

Why this score

tls_present_and_valid+4
mcp_capabilities_discoverable+4
reachable+2
hsts_enabled+1

Findings (1)

infoCORS allows any origin
cors.wildcard_origin @ 1.0.0

Evidence (8)

TypeObservedSHA-256
dns_resolution_observation1d ago5db6581ce036c893…
http_response_observation1d ago3d882923b2ed9f75…
availability_observation1d agod719c8664ff04db6…
hosting_provider_observation1d ago07b610f7cd67ffa2…
tls_certificate_observation1d agoc56037c91c742c74…
oauth_metadata_observation1d agoe64409606fa4eccc…
mcp_protocol_observation1d ago471f906c71fcb633…
mcp_capability_observation1d agof733f5a9b6d5abed…

Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.

Operate this service?

Prove control of portlandmaps-mcp.vercel.app/mcp/v2 to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.

Claim this profile →