snapto.link/api
https://snapto.link/api/mcp
77
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 7d ago
Why this score
| oauth_metadata_present | +14 |
| mcp_requires_authentication | +10 |
| tls_present_and_valid | +4 |
| headers.missing_hsts | -3 |
| reachable | +2 |
Findings (2)
| low | No Strict-Transport-Security header headers.missing_hsts @ 1.0.0 |
| info | CORS allows any origin cors.wildcard_origin @ 1.0.0 |
Evidence (7)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 7d ago | 42bf84b8434498f3… |
| http_response_observation | 7d ago | cca17622a497e0c6… |
| availability_observation | 7d ago | 533bad72ed79ce21… |
| hosting_provider_observation | 7d ago | e7292135d1d3f6bd… |
| tls_certificate_observation | 7d ago | 282eee4419d2f563… |
| oauth_metadata_observation | 7d ago | 3b05b26cd194190a… |
| mcp_protocol_observation | 7d ago | 5f4c66c82509bed4… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of snapto.link/api to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.