atx/registry

bittensormcp.com/api

https://bittensormcp.com/api/mcp

81
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 1h ago

Why this score

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

Findings (0)

No findings from the current evidence set.

Evidence (7)

TypeObservedSHA-256
dns_resolution_observation1h agoa5665368cbd38a8c…
http_response_observation1h agod049e6ac56358cee…
availability_observation1h ago4b8aee3a0c715c42…
hosting_provider_observation1h agof6ca63562d443d49…
tls_certificate_observation1h agod773416980d20d83…
oauth_metadata_observation1h agoc47a37c8cc1df0c2…
mcp_protocol_observation1h ago5f4c66c82509bed4…

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

Operate this service?

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

Claim this profile →