atx/registry

locker.veritap.dev

https://locker.veritap.dev/mcp

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

Why this score

mcp.unauthenticated_consequential_tools-8
tls_present_and_valid+4
mcp_capabilities_discoverable+4
headers.missing_hsts-3
reachable+2

Findings (3)

mediumCapabilities are listable without authentication, including 2 whose names suggest state change (locker_invite, locker_send) — inferred from tool names, not confirmed
mcp.unauthenticated_consequential_tools @ 1.0.0
lowNo Strict-Transport-Security header
headers.missing_hsts @ 1.0.0
infoCORS allows any origin
cors.wildcard_origin @ 1.0.0

Evidence (8)

TypeObservedSHA-256
dns_resolution_observation1d ago8faf7d91188e609c…
http_response_observation1d agoc8ca889a51923bb5…
availability_observation1d agoc1d1abd175580b55…
hosting_provider_observation1d agoe7292135d1d3f6bd…
tls_certificate_observation1d agoe72dc2a98e97eae1…
oauth_metadata_observation1d ago63b0a6e72660d3ec…
mcp_protocol_observation1d ago7a48b513136dd9b2…
mcp_capability_observation1d agoe78d97cc1d63b10e…

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

Operate this service?

Prove control of locker.veritap.dev to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.

Claim this profile →