api.sessionkeeper.ai
https://api.sessionkeeper.ai/mcp
63
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 2d ago
Why this score
| 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 (6)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 2d ago | 828c6b001a44d1a0… |
| http_response_observation | 2d ago | 77e78a81b20cf1b4… |
| availability_observation | 2d ago | 4fc38066c8dcd391… |
| hosting_provider_observation | 2d ago | e7292135d1d3f6bd… |
| tls_certificate_observation | 2d ago | 6c388ce2e6ba51c4… |
| mcp_protocol_observation | 2d ago | 5f4c66c82509bed4… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of api.sessionkeeper.ai to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.