gigaverse.ai/api
https://gigaverse.ai/api/mcp
57
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 3h 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 | 3h ago | 3b47c50b97fea350… |
| http_response_observation | 3h ago | 783bf425dea0eb68… |
| availability_observation | 3h ago | 21b9aff907ed027d… |
| hosting_provider_observation | 3h ago | e7292135d1d3f6bd… |
| tls_certificate_observation | 3h ago | 43e768e3250943ec… |
| oauth_metadata_observation | 3h ago | 1d2ec6fe4a3d9f1d… |
| mcp_protocol_observation | 3h ago | f54cef680947e9be… |
| mcp_capability_observation | 3h ago | 63e762629d495ad1… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of gigaverse.ai/api to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.