atx/registry

veritap.dev

https://veritap.dev/mcp

49
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 2d 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 1 whose name suggests state change (confirm_before_purchase) — 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_observation2d ago0b1b2828ae85bb1d…
http_response_observation2d agod7f3d735445e1e5d…
availability_observation2d ago588d157f5739f454…
hosting_provider_observation2d agoe7292135d1d3f6bd…
tls_certificate_observation2d ago2d39cc1852d88682…
oauth_metadata_observation2d ago1a70caeaf28e5abb…
mcp_protocol_observation2d agobcacdf7238f060af…
mcp_capability_observation2d ago823f7c13b1e152da…

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

Operate this service?

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

Claim this profile →