lme.viibe.to
https://lme.viibe.to/mcp
63
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 1d ago
Why this score
| 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 | 1d ago | d1faead66a5cd023… |
| http_response_observation | 1d ago | 73bd6a9c12ca9ebf… |
| availability_observation | 1d ago | 2990df4201e70685… |
| hosting_provider_observation | 1d ago | e7292135d1d3f6bd… |
| tls_certificate_observation | 1d ago | d9d484bdd9e13643… |
| oauth_metadata_observation | 1d ago | f3b308aa1d86abc2… |
| mcp_protocol_observation | 1d ago | 5f4c66c82509bed4… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of lme.viibe.to to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.