mcp.time.mcpcentral.io
https://mcp.time.mcpcentral.io/
57
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 2d 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 | 2d ago | 0d890905f05f1aed… |
| http_response_observation | 2d ago | b0f54163f5121829… |
| availability_observation | 2d ago | 4837ed604c07e23e… |
| hosting_provider_observation | 2d ago | e7292135d1d3f6bd… |
| tls_certificate_observation | 2d ago | 86f69870c6813a81… |
| oauth_metadata_observation | 2d ago | 9e6342b44d743db0… |
| mcp_protocol_observation | 2d ago | 40bc3d7af1551542… |
| mcp_capability_observation | 2d ago | 7fc17a7e45254df6… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of mcp.time.mcpcentral.io to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.