mcp.aibvf.com/api
https://mcp.aibvf.com/api/mcp
61
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 17h ago
Why this score
| tls_present_and_valid | +4 |
| mcp_capabilities_discoverable | +4 |
| reachable | +2 |
| hsts_enabled | +1 |
Findings (0)
No findings from the current evidence set.
Evidence (8)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 17h ago | 599f8b56bc2efeb2… |
| http_response_observation | 17h ago | 26e3d11a18db1db8… |
| availability_observation | 17h ago | b5b7ae85f873e87e… |
| hosting_provider_observation | 17h ago | 07b610f7cd67ffa2… |
| tls_certificate_observation | 17h ago | ced2fbc9745ba4af… |
| oauth_metadata_observation | 17h ago | ea0f906cad0475de… |
| mcp_protocol_observation | 17h ago | 32c13727e540bffb… |
| mcp_capability_observation | 17h ago | c5dc7ed331a0131a… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of mcp.aibvf.com/api to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.