atx/registry

api.builderforce.ai

https://api.builderforce.ai/mcp

63
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 1h 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_observation1h ago4e635b8bc5ab0996…
http_response_observation1h ago2803cc9073d4a921…
availability_observation1h agofb7e7d4268a8210e…
hosting_provider_observation1h agoe7292135d1d3f6bd…
tls_certificate_observation1h agoa4356c3a4424e421…
oauth_metadata_observation1h ago0be4950e9ed26aa9…
mcp_protocol_observation1h ago5f4c66c82509bed4…

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

Operate this service?

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

Claim this profile →