mcp.busymate.dev
https://mcp.busymate.dev/
90
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 2d ago
Why this score
| oauth_metadata_present | +14 |
| tls_present_and_valid | +12 |
| reachable | +6 |
| hsts_enabled | +4 |
| mcp_capabilities_discoverable | +4 |
Findings (0)
No findings from the current evidence set.
Evidence (7)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 2d ago | b521956b83ec534f… |
| http_response_observation | 2d ago | 4fcb905dd35ef9de… |
| availability_observation | 2d ago | 2d241d87e7197225… |
| tls_certificate_observation | 2d ago | 7c2737aa61c83996… |
| oauth_metadata_observation | 2d ago | dc213ce577857429… |
| mcp_protocol_observation | 2d ago | 16ea09d067dfc696… |
| mcp_capability_observation | 2d ago | 45ed70082b636130… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of mcp.busymate.dev to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.