api.jentic.com
https://api.jentic.com/mcp
89
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_requires_authentication | +10 |
| reachable | +6 |
| headers.missing_hsts | -3 |
Findings (1)
| low | No Strict-Transport-Security header headers.missing_hsts @ 1.0.0 |
Evidence (6)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 2d ago | ec8faad084c34a12… |
| http_response_observation | 2d ago | 081ba56e68f8ba0a… |
| availability_observation | 2d ago | e4344b088f4702c4… |
| tls_certificate_observation | 2d ago | 4e50855eacdf29c7… |
| oauth_metadata_observation | 2d ago | f61d1f5f38be4b68… |
| 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.jentic.com to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.