api.bitfence.ai
https://api.bitfence.ai/mcp
69
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 1h ago
Why this score
| tls_present_and_valid | +12 |
| reachable | +6 |
| mcp_capabilities_discoverable | +4 |
| headers.missing_hsts | -3 |
Findings (1)
| low | No Strict-Transport-Security header headers.missing_hsts @ 1.0.0 |
Evidence (7)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 1h ago | 1ae0e3dfcc3eaed6… |
| http_response_observation | 1h ago | a574cf5b9b50fabd… |
| availability_observation | 1h ago | 3c5c60b31848cc42… |
| tls_certificate_observation | 1h ago | f90b842272c059fe… |
| oauth_metadata_observation | 1h ago | 57dc9ff376ffeab1… |
| mcp_protocol_observation | 1h ago | c252bceea7101e2d… |
| mcp_capability_observation | 1h ago | 3070f1625417370b… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of api.bitfence.ai to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.