padel.how
https://padel.how/mcp
61
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 1d 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 | 1d ago | 7a1ddd0266d0362c… |
| http_response_observation | 1d ago | 52cdc75486926597… |
| availability_observation | 1d ago | b63dd46b73092b86… |
| hosting_provider_observation | 1d ago | e7292135d1d3f6bd… |
| tls_certificate_observation | 1d ago | 5ff8b59a2a2ab7ae… |
| oauth_metadata_observation | 1d ago | 9c738fb3015405f1… |
| mcp_protocol_observation | 1d ago | 379a81a19b742513… |
| mcp_capability_observation | 1d ago | 53e088b59105091e… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of padel.how to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.