busymail.app
https://busymail.app/mcp
67
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 1h ago
Why this score
| 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)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 1h ago | 9dbdfd7cca572a46… |
| http_response_observation | 1h ago | e1e50d1cd671d136… |
| availability_observation | 1h ago | 7f711c3aaf3e724b… |
| hosting_provider_observation | 1h ago | e7292135d1d3f6bd… |
| tls_certificate_observation | 1h ago | bc0c3ec4e1137bcc… |
| oauth_metadata_observation | 1h ago | 2afaaeca92f40514… |
| mcp_protocol_observation | 1h ago | 5f4c66c82509bed4… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of busymail.app to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.