atx/registry

mcp.elicitly.ai

https://mcp.elicitly.ai/mcp

81
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 1d ago

Why this score

oauth_metadata_present+14
mcp_requires_authentication+10
tls_present_and_valid+4
reachable+2
hsts_enabled+1

Findings (0)

No findings from the current evidence set.

Evidence (7)

TypeObservedSHA-256
dns_resolution_observation1d ago0b7e295f122fd6fa…
http_response_observation1d ago9cc74d0bd00c3464…
availability_observation1d agoe448c091b029f883…
hosting_provider_observation1d agoe7292135d1d3f6bd…
tls_certificate_observation1d agoc9dcb5fac1f3fd92…
oauth_metadata_observation1d agod8bc237574eb6de3…
mcp_protocol_observation1d ago5f4c66c82509bed4…

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

Operate this service?

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

Claim this profile →