content.mcp.xpay.sh
https://content.mcp.xpay.sh/mcp?key={api_key}
65
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 2d ago
Why this score
| 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 | 754ba11c0e4a671a… |
| http_response_observation | 2d ago | 7aa3a6b407c6e6f9… |
| availability_observation | 2d ago | 13f80c2d1ea069fd… |
| tls_certificate_observation | 2d ago | c70a873a4440b8c4… |
| oauth_metadata_observation | 2d ago | 51ef9c43bc425250… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of content.mcp.xpay.sh to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.