atx/registry

mcp.nslookup.io

https://mcp.nslookup.io/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 ago0b09e4f8850fb5f4…
http_response_observation2d agob0eb71d44a68ebf4…
availability_observation2d agob082a7f47ea3b739…
hosting_provider_observation2d agoe7292135d1d3f6bd…
tls_certificate_observation2d agoc464c15c698cf780…
oauth_metadata_observation2d agoe87fd9aa5c32d116…
mcp_protocol_observation2d ago287b01e661605c20…
mcp_capability_observation2d agocc9b312e2655c7b3…

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

Operate this service?

Prove control of mcp.nslookup.io to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.

Claim this profile →