context.era.app
https://context.era.app/mcp
77
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 4h ago
Why this score
| oauth_metadata_present | +14 |
| mcp_requires_authentication | +10 |
| tls_present_and_valid | +4 |
| headers.missing_hsts | -3 |
| reachable | +2 |
Findings (1)
| low | No Strict-Transport-Security header headers.missing_hsts @ 1.0.0 |
Evidence (7)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 4h ago | 839678276c4df5d6… |
| http_response_observation | 4h ago | 76af1450c5c3caca… |
| availability_observation | 4h ago | 61f396089b0faddc… |
| hosting_provider_observation | 4h ago | 8798e26cda16e4a4… |
| tls_certificate_observation | 4h ago | f9372cf6bce45b1a… |
| oauth_metadata_observation | 4h ago | 3c1c51875c77d046… |
| mcp_protocol_observation | 4h ago | 5f4c66c82509bed4… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of context.era.app to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.