api.lmgram.com
https://api.lmgram.com/mcp
75
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 2d ago
Why this score
| oauth_metadata_present | +14 |
| tls_present_and_valid | +12 |
| mcp.unauthenticated_consequential_tools | -8 |
| reachable | +6 |
| mcp_capabilities_discoverable | +4 |
| headers.missing_hsts | -3 |
Findings (2)
| medium | Capabilities are listable without authentication, including 1 whose name suggests state change (send_message) — 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 (7)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 2d ago | 3e05f104d97b721d… |
| http_response_observation | 2d ago | 02bdc78cdca4765a… |
| availability_observation | 2d ago | 21bb3c9a074ad7d8… |
| tls_certificate_observation | 2d ago | 2f40722f69c6b356… |
| oauth_metadata_observation | 2d ago | 08358cbc54be8d1d… |
| mcp_protocol_observation | 2d ago | fdb3db9b14030625… |
| mcp_capability_observation | 2d ago | fc6d5ad8349d9952… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of api.lmgram.com to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.