atx/registry

mcp.biddeed.ai/api

https://mcp.biddeed.ai/api/mcp

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

Why this score

oauth_metadata_present+14
mcp_requires_authentication+10
tls_present_and_valid+4
reachable+2
hsts_enabled+1

Findings (1)

infoCORS allows any origin
cors.wildcard_origin @ 1.0.0

Evidence (7)

TypeObservedSHA-256
dns_resolution_observation2d ago0fceb8a2bdbbb503…
http_response_observation2d ago193bc3efaa645839…
availability_observation2d ago89c7f27ec3aedc23…
hosting_provider_observation2d ago07b610f7cd67ffa2…
tls_certificate_observation2d agocd90d05efd8388d0…
oauth_metadata_observation2d agoc0296673b4fe1fe5…
mcp_protocol_observation2d ago5f4c66c82509bed4…

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

Operate this service?

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

Claim this profile →