atx/registry

lumify.ai

https://lumify.ai/mcp

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

Why this score

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

Findings (2)

lowNo Strict-Transport-Security header
headers.missing_hsts @ 1.0.0
lowInput schema changed without a name change: list_ev, list_forecasts
mcp.tool_schema_changed @ 1.0.0

Evidence (9)

TypeObservedSHA-256
dns_resolution_observation1d ago3b2c9e360b65eb8c…
http_response_observation1d agod002c03c7957c990…
availability_observation1d ago23b7cb51fb221de2…
hosting_provider_observation1d agoe7292135d1d3f6bd…
tls_certificate_observation1d agob128f410855d98c3…
oauth_metadata_observation1d ago3445d9b3ef5af676…
mcp_protocol_observation1d ago678e4d5d0014869b…
mcp_capability_observation1d ago956addfaced427f0…
mcp_capability_drift1d agod90a153134dbc828…

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

Operate this service?

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

Claim this profile →