atx/registry

mcp.threadminder.ai

https://mcp.threadminder.ai/mcp

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 ago17d4a4f348fe4978…
http_response_observation2d agoc04a3c018a0b13b4…
availability_observation2d ago4653992b1a386b93…
hosting_provider_observation2d ago8798e26cda16e4a4…
tls_certificate_observation2d ago0b874cf12fdfa62b…
oauth_metadata_observation2d ago2792e210e839a0d2…
mcp_protocol_observation2d ago5f4c66c82509bed4…

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

Operate this service?

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

Claim this profile →