mcp.approval.studio
https://mcp.approval.studio/
63
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 2d ago
Why this score
| mcp_requires_authentication | +10 |
| tls_present_and_valid | +4 |
| headers.missing_hsts | -3 |
| reachable | +2 |
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 | a8497e4e0e21fa8d… |
| http_response_observation | 2d ago | a4b794876c7fc01d… |
| availability_observation | 2d ago | a6f1e4894e6d3462… |
| hosting_provider_observation | 2d ago | e7292135d1d3f6bd… |
| tls_certificate_observation | 2d ago | d320dc0e0f257777… |
| oauth_metadata_observation | 2d ago | dde77b132ef715e5… |
| mcp_protocol_observation | 2d ago | 5f4c66c82509bed4… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of mcp.approval.studio to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.