mcp.sap.oobeprotocol.ai
https://mcp.sap.oobeprotocol.ai/mcp
69
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 2d ago
Why this score
| tls_present_and_valid | +12 |
| reachable | +6 |
| mcp_capabilities_discoverable | +4 |
| headers.missing_hsts | -3 |
Findings (1)
| low | No Strict-Transport-Security header headers.missing_hsts @ 1.0.0 |
Evidence (7)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 2d ago | be2f1e7b471f228a… |
| http_response_observation | 2d ago | b68416149c955ebd… |
| availability_observation | 2d ago | d16a90ca50ae0c21… |
| tls_certificate_observation | 2d ago | b772eddb60ec9e0d… |
| oauth_metadata_observation | 2d ago | 35334b1399620c96… |
| mcp_protocol_observation | 2d ago | 595f17fe41751bae… |
| mcp_capability_observation | 2d ago | 3070f1625417370b… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of mcp.sap.oobeprotocol.ai to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.