mcp.zapier.com/api/v1/connect
https://mcp.zapier.com/api/v1/connect
82
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 2d ago
Why this score
| tls_present_and_valid | +12 |
| mcp_requires_authentication | +10 |
| reachable | +6 |
| hsts_enabled | +4 |
Findings (0)
No findings from the current evidence set.
Evidence (6)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 2d ago | 107b9a994cfd4236… |
| http_response_observation | 2d ago | 5ab3165c2f96873a… |
| availability_observation | 2d ago | f71f56890c40b77e… |
| tls_certificate_observation | 2d ago | 24de0cbf6c02c0f9… |
| oauth_metadata_observation | 2d ago | 9a1d70065a7f07e1… |
| mcp_protocol_observation | 2d ago | 5f4c66c82509bed4… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of mcp.zapier.com/api/v1/connect to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.