atx/registry

dns-lookup-mcp.mcpize.run

https://dns-lookup-mcp.mcpize.run/mcp

75
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 2d ago

Why this score

oauth_metadata_present+14
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_observation2d ago3b37b318df9516b2…
http_response_observation2d ago1a8e70a998a68456…
availability_observation2d ago541c35e482f6299f…
hosting_provider_observation2d agoe7292135d1d3f6bd…
tls_certificate_observation2d agocc4618390022e7df…
oauth_metadata_observation2d ago90c53bcc4d69c5bb…
mcp_protocol_observation2d ago8f319170bf0b5e30…
mcp_capability_observation2d ago391964ff5d37c662…

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

Operate this service?

Prove control of dns-lookup-mcp.mcpize.run to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.

Claim this profile →