atx/registry

api.flato.ai/api/mcp/editor

https://api.flato.ai/api/mcp/editor

63
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 2d ago

Why this score

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

Findings (2)

lowNo Strict-Transport-Security header
headers.missing_hsts @ 1.0.0
infoCORS allows any origin
cors.wildcard_origin @ 1.0.0

Evidence (7)

TypeObservedSHA-256
dns_resolution_observation2d ago5fc350fc330d14a5…
http_response_observation2d ago686f0652b45a550b…
availability_observation2d agoc667e55408b5ce79…
hosting_provider_observation2d agoe7292135d1d3f6bd…
tls_certificate_observation2d ago23a4ee4810d4e998…
oauth_metadata_observation2d ago3fcd3f7fdf2909ab…
mcp_protocol_observation2d ago5f4c66c82509bed4…

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

Operate this service?

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

Claim this profile →