twitter.fetcher.sh
https://twitter.fetcher.sh/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 | 4cb1f4dd12b0ddff… |
| http_response_observation | 2d ago | 631d768093851dfb… |
| availability_observation | 2d ago | 40c40c644363ea2a… |
| hosting_provider_observation | 2d ago | e7292135d1d3f6bd… |
| tls_certificate_observation | 2d ago | 0ebd9b2a5d6b4f75… |
| oauth_metadata_observation | 2d ago | ca56a2b11f741dc6… |
| mcp_protocol_observation | 2d ago | 67084caaccb8353a… |
| mcp_capability_observation | 2d ago | 16d0674918269f83… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of twitter.fetcher.sh to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.