api.savvly.com
https://api.savvly.com/mcp
73
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 3h ago
Why this score
| tls_present_and_valid | +12 |
| reachable | +6 |
| hsts_enabled | +4 |
| mcp_capabilities_discoverable | +4 |
| mcp.tool_schema_changed | -3 |
Findings (2)
| low | Input schema changed without a name change: check_savvly_eligibility, compare_savvly_vs_alternative, get_savvly_faq mcp.tool_schema_changed @ 1.0.0 |
| info | CORS allows any origin cors.wildcard_origin @ 1.0.0 |
Evidence (8)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 3h ago | 8bf76a32f7e8c0a0… |
| http_response_observation | 3h ago | d327b2cb7972e119… |
| availability_observation | 3h ago | b7591a3e00631711… |
| tls_certificate_observation | 3h ago | 6bf9a35d837f7a52… |
| oauth_metadata_observation | 3h ago | 4b0372e0502786d4… |
| mcp_protocol_observation | 3h ago | 4136785f5d082de4… |
| mcp_capability_observation | 3h ago | 956a700bfb74fb32… |
| mcp_capability_drift | 3h ago | c21fb41a489ca049… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of api.savvly.com to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.