atx/registry

x711.io

https://x711.io/mcp

53
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 6d ago

Why this score

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 6 whose names suggest state change (x711_email_send, x711_hive_write, x711_ping_shield_subscribe, …) — 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_observation6d agod4808cbce8e16cd2…
http_response_observation6d ago0ff18a69f84d8b3e…
availability_observation6d ago2db2ac13a86bfd1a…
hosting_provider_observation6d ago958411567b2d9bdc…
tls_certificate_observation6d ago4f79c266db3e0ae7…
oauth_metadata_observation6d agoca9f40d77c4333c0…
mcp_protocol_observation6d ago0fd1ce30399f3788…
mcp_capability_observation6d ago32674447ffa76e43…

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

Operate this service?

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

Claim this profile →