atx/registry

api.serff.ai

https://api.serff.ai/mcp

71
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 2d ago

Why this score

oauth_metadata_present+14
tls_present_and_valid+4
mcp_capabilities_discoverable+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 (8)

TypeObservedSHA-256
dns_resolution_observation2d ago24c1d730ae89bce8…
http_response_observation2d ago24a64a6986480453…
availability_observation2d ago9bb6ba94c48a0953…
hosting_provider_observation2d ago958411567b2d9bdc…
tls_certificate_observation2d agoe6251a303111399a…
oauth_metadata_observation2d ago82e50f6043e18e33…
mcp_protocol_observation2d ago08f47ecc8814f24d…
mcp_capability_observation2d ago675fd13f21dff9a5…

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

Operate this service?

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

Claim this profile →