mcp.eusend.dev
https://mcp.eusend.dev/mcp
75
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 |
| headers.missing_hsts | -3 |
Findings (1)
| low | No Strict-Transport-Security header headers.missing_hsts @ 1.0.0 |
Evidence (6)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 2d ago | 7b5e08e67288a075… |
| http_response_observation | 2d ago | 35f5e24ac6ef826c… |
| availability_observation | 2d ago | b7860ece3b493a52… |
| tls_certificate_observation | 2d ago | eaea2ad63f720932… |
| oauth_metadata_observation | 2d ago | e850a5b0ceaa14a4… |
| 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.eusend.dev to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.