mcp.tinysend.com
https://mcp.tinysend.com/
77
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 2d ago
Why this score
| oauth_metadata_present | +14 |
| mcp_requires_authentication | +10 |
| tls_present_and_valid | +4 |
| headers.missing_hsts | -3 |
| reachable | +2 |
Findings (1)
| low | No Strict-Transport-Security header headers.missing_hsts @ 1.0.0 |
Evidence (7)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 2d ago | ac66c4976ea46fd2… |
| http_response_observation | 2d ago | f08fe9a13cb34b7d… |
| availability_observation | 2d ago | 799783ffac59e27c… |
| hosting_provider_observation | 2d ago | e7292135d1d3f6bd… |
| tls_certificate_observation | 2d ago | 002bf80602c25cfd… |
| oauth_metadata_observation | 2d ago | b73ce713daca4448… |
| 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.tinysend.com to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.