api.liminary.io/api
https://api.liminary.io/api/mcp/
67
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 2d ago
Why this score
| mcp_requires_authentication | +10 |
| tls_present_and_valid | +4 |
| reachable | +2 |
| hsts_enabled | +1 |
Findings (0)
No findings from the current evidence set.
Evidence (7)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 2d ago | e576147ee11b0733… |
| http_response_observation | 2d ago | 215daad699c7c9ad… |
| availability_observation | 2d ago | bfc4a883b836bd68… |
| hosting_provider_observation | 2d ago | 00d7b14f2bf09068… |
| tls_certificate_observation | 2d ago | 926b20090316327d… |
| oauth_metadata_observation | 2d ago | 65a72fe70fbe402a… |
| 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 api.liminary.io/api to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.