atx/registry

lvlltd.com/api

https://lvlltd.com/api/mcp

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

Why this score

oauth_metadata_present+14
mcp.unauthenticated_consequential_tools-8
tls_present_and_valid+4
mcp_capabilities_discoverable+4
reachable+2
hsts_enabled+1

Findings (2)

mediumCapabilities are listable without authentication, including 7 whose names suggest state change (a2a_message_send, a2a_tasks_cancel, long_running_cancel, …) — inferred from tool names, not confirmed
mcp.unauthenticated_consequential_tools @ 1.0.0
infoCORS allows any origin
cors.wildcard_origin @ 1.0.0

Evidence (8)

TypeObservedSHA-256
dns_resolution_observation1d agoe782608b041bf4a7…
http_response_observation1d agoace6c8fa6cc77e34…
availability_observation1d ago9b92f6a52c9786c4…
hosting_provider_observation1d agoe7292135d1d3f6bd…
tls_certificate_observation1d agoe5f0fc541ab6685a…
oauth_metadata_observation1d ago3ba2f3bd605797e0…
mcp_protocol_observation1d agodd8dab30808860ff…
mcp_capability_observation1d ago8c5f5891bd87eb07…

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

Operate this service?

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

Claim this profile →