atx/registry

api.vruum.ai

https://api.vruum.ai/mcp

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

Why this score

oauth_metadata_present+14
mcp_requires_authentication+10
tls_present_and_valid+4
headers.missing_hsts-3
reachable+2

Findings (1)

lowNo Strict-Transport-Security header
headers.missing_hsts @ 1.0.0

Evidence (7)

TypeObservedSHA-256
dns_resolution_observation2d agoaa9cefb0f4ee8891…
http_response_observation2d ago2765f0b8e53d6302…
availability_observation2d ago6d12a1b42354b06e…
hosting_provider_observation2d agof6ca63562d443d49…
tls_certificate_observation2d ago10a798d078c363df…
oauth_metadata_observation2d ago1d304a9bf687dd6a…
mcp_protocol_observation2d ago5f4c66c82509bed4…

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

Operate this service?

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

Claim this profile →