mcp.lastping.dev
https://mcp.lastping.dev/
75
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 1d ago
Why this score
| tls_present_and_valid | +12 |
| mcp_requires_authentication | +10 |
| reachable | +6 |
| headers.missing_hsts | -3 |
Findings (1)
| low | No Strict-Transport-Security header headers.missing_hsts @ 1.0.0 |
Evidence (6)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 1d ago | 75bd71beef9aad68… |
| http_response_observation | 1d ago | faf61b0d292c0a93… |
| availability_observation | 1d ago | ea163130e68f3c0a… |
| tls_certificate_observation | 1d ago | af88299267a9e6b3… |
| oauth_metadata_observation | 1d ago | 163c95a37d6ba370… |
| mcp_protocol_observation | 1d ago | 5f4c66c82509bed4… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of mcp.lastping.dev to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.