whenmeet.me
https://whenmeet.me/mcp
49
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 6d ago
Why this score
| mcp.unauthenticated_consequential_tools | -8 |
| tls_present_and_valid | +4 |
| mcp_capabilities_discoverable | +4 |
| headers.missing_hsts | -3 |
| reachable | +2 |
Findings (2)
| medium | Capabilities are listable without authentication, including 2 whose names suggest state change (create_meeting, set_manual_availability) — inferred from tool names, not confirmed mcp.unauthenticated_consequential_tools @ 1.0.0 |
| low | No Strict-Transport-Security header headers.missing_hsts @ 1.0.0 |
Evidence (8)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 6d ago | 92fbe725f2829746… |
| http_response_observation | 6d ago | 1267731cc140377d… |
| availability_observation | 6d ago | d1eaec7e7254268c… |
| hosting_provider_observation | 6d ago | e7292135d1d3f6bd… |
| tls_certificate_observation | 6d ago | 408a0102a2128128… |
| oauth_metadata_observation | 6d ago | 5c47c145a52d47a3… |
| mcp_protocol_observation | 6d ago | a8927e92889fb3f5… |
| mcp_capability_observation | 6d ago | cfb1668f0fdbf16e… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of whenmeet.me to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.