api.intentlink.io
https://api.intentlink.io/mcp/
57
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 2d ago
Why this score
| tls_present_and_valid | +4 |
| mcp_capabilities_discoverable | +4 |
| headers.missing_hsts | -3 |
| reachable | +2 |
Findings (1)
| low | No Strict-Transport-Security header headers.missing_hsts @ 1.0.0 |
Evidence (8)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 2d ago | 68fb887320fc5064… |
| http_response_observation | 2d ago | f87028d8471b3cc4… |
| availability_observation | 2d ago | 49a16e1ba9a03a86… |
| hosting_provider_observation | 2d ago | e7292135d1d3f6bd… |
| tls_certificate_observation | 2d ago | b98f8855666ff06a… |
| oauth_metadata_observation | 2d ago | 2b6dff7125d58869… |
| mcp_protocol_observation | 2d ago | 249cbe51110f05fb… |
| mcp_capability_observation | 2d ago | aee0e7b33ea142ff… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of api.intentlink.io to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.