lmk.today/api/ucp
https://lmk.today/api/ucp/mcp
61
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 2h 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 | 2h ago | 05ed8bc78f4c8f1e… |
| http_response_observation | 2h ago | 3d520a05e88575d9… |
| availability_observation | 2h ago | e141223655c4f4b8… |
| hosting_provider_observation | 2h ago | e7292135d1d3f6bd… |
| tls_certificate_observation | 2h ago | 7544e28bada67754… |
| oauth_metadata_observation | 2h ago | 843aa29541ab54be… |
| mcp_protocol_observation | 2h ago | 42671cc2b62be5cd… |
| mcp_capability_observation | 2h ago | 4c82047a7d037d21… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of lmk.today/api/ucp to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.