lmk.today/api/ucp
https://lmk.today/api/ucp/mcp
61
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 2d 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 | 2d ago | 860119b6e72ec708… |
| http_response_observation | 2d ago | 287d4332b595a10b… |
| availability_observation | 2d ago | a4edd94d379d753e… |
| hosting_provider_observation | 2d ago | 07b610f7cd67ffa2… |
| tls_certificate_observation | 2d ago | d065a24ac71d544b… |
| oauth_metadata_observation | 2d ago | 843aa29541ab54be… |
| mcp_protocol_observation | 2d ago | 140d1e7bf1d491df… |
| mcp_capability_observation | 2d ago | aef7dfe867ca1519… |
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.