salvagesignal.com/api
https://salvagesignal.com/api/mcp
61
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 6d ago
Why this score
| tls_present_and_valid | +4 |
| mcp_capabilities_discoverable | +4 |
| reachable | +2 |
| hsts_enabled | +1 |
Findings (0)
No findings from the current evidence set.
Evidence (8)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 6d ago | db0f4c8d7557553c… |
| http_response_observation | 6d ago | 674550aae66c78e1… |
| availability_observation | 6d ago | f5d211c531bec12f… |
| hosting_provider_observation | 6d ago | 7866a6c27a2779dd… |
| tls_certificate_observation | 6d ago | e3fcfd2acb511dd2… |
| oauth_metadata_observation | 6d ago | a6184366c53e0918… |
| mcp_protocol_observation | 6d ago | a3da6fe8c316441b… |
| mcp_capability_observation | 6d ago | 1d41eb42fd37d5e3… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of salvagesignal.com/api to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.