viewmax.studio/api
https://viewmax.studio/api/mcp
75
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 6d ago
Why this score
| oauth_metadata_present | +14 |
| tls_present_and_valid | +4 |
| mcp_capabilities_discoverable | +4 |
| reachable | +2 |
| hsts_enabled | +1 |
Findings (0)
No findings from the current evidence set.
Evidence (8)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 6d ago | 7bd44b7e8d3d89a1… |
| http_response_observation | 6d ago | 59f71adae17d2273… |
| availability_observation | 6d ago | 8030ded3d87c206d… |
| hosting_provider_observation | 6d ago | e7292135d1d3f6bd… |
| tls_certificate_observation | 6d ago | 0f67c11b516bfa10… |
| oauth_metadata_observation | 6d ago | 6e6dd497d7614932… |
| mcp_protocol_observation | 6d ago | 9801a4a15c17f54e… |
| mcp_capability_observation | 6d ago | de31d786de300e86… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of viewmax.studio/api to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.