content-strategy.api.trendsmcp.ai
https://content-strategy.api.trendsmcp.ai/mcp
71
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 | +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 | 7be8c118ac522196… |
| http_response_observation | 2d ago | 0a30b48c18fc8e3b… |
| availability_observation | 2d ago | 2fe69ac708d85598… |
| hosting_provider_observation | 2d ago | e0cc952cc06f53e3… |
| tls_certificate_observation | 2d ago | 583a4723297c1af4… |
| oauth_metadata_observation | 2d ago | a36e520e0d709930… |
| mcp_protocol_observation | 2d ago | dc07fade4195142c… |
| mcp_capability_observation | 2d ago | 3070f1625417370b… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of content-strategy.api.trendsmcp.ai to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.