mcp.nansen.ai/api
https://mcp.nansen.ai/api/mcp
79
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 2d ago
Why this score
| oauth_metadata_present | +14 |
| tls_present_and_valid | +12 |
| reachable | +6 |
| headers.missing_hsts | -3 |
Findings (1)
| low | No Strict-Transport-Security header headers.missing_hsts @ 1.0.0 |
Evidence (5)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 2d ago | ed8d8d4bf2526e3b… |
| http_response_observation | 2d ago | b06e29cd22ec09c5… |
| availability_observation | 2d ago | 116a723f4f92b9a9… |
| tls_certificate_observation | 2d ago | a12eaff085e162e2… |
| oauth_metadata_observation | 2d ago | d49d13fe9c7c82fe… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of mcp.nansen.ai/api to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.