mcp.jeda.ai
https://mcp.jeda.ai/mcp
57
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 1d ago
Why this score
| tls_present_and_valid | +4 |
| mcp_capabilities_discoverable | +4 |
| headers.missing_hsts | -3 |
| reachable | +2 |
Findings (1)
| low | No Strict-Transport-Security header headers.missing_hsts @ 1.0.0 |
Evidence (8)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 1d ago | a607bb3d6e137daa… |
| http_response_observation | 1d ago | aab5814ff514ac77… |
| availability_observation | 1d ago | 186e58206ad80198… |
| hosting_provider_observation | 1d ago | e7292135d1d3f6bd… |
| tls_certificate_observation | 1d ago | 2dd5a1d37c760491… |
| oauth_metadata_observation | 1d ago | 72fe58f2cef8db34… |
| mcp_protocol_observation | 1d ago | 8781bc9ea146575f… |
| mcp_capability_observation | 1d ago | ec4b6a9c17592a8e… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of mcp.jeda.ai to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.