yieldsignal.vercel.app
https://yieldsignal.vercel.app/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 | e4e6f7409d172fa9… |
| http_response_observation | 6d ago | 099f14d6d6555338… |
| availability_observation | 6d ago | a0019a0b6a35f78b… |
| hosting_provider_observation | 6d ago | 07b610f7cd67ffa2… |
| tls_certificate_observation | 6d ago | a72cfaf22a290d8b… |
| oauth_metadata_observation | 6d ago | 966b8f8413de5f78… |
| mcp_protocol_observation | 6d ago | f9a7c659e1f49339… |
| mcp_capability_observation | 6d ago | 91a360544f5632ba… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of yieldsignal.vercel.app to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.