mcp.cut.pro
https://mcp.cut.pro/
77
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 1d ago
Why this score
| oauth_metadata_present | +14 |
| mcp_requires_authentication | +10 |
| tls_present_and_valid | +4 |
| headers.missing_hsts | -3 |
| reachable | +2 |
Findings (2)
| low | No Strict-Transport-Security header headers.missing_hsts @ 1.0.0 |
| info | CORS allows any origin cors.wildcard_origin @ 1.0.0 |
Evidence (7)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 1d ago | 67034eceabeddf8b… |
| http_response_observation | 1d ago | 25278a57e7c8e199… |
| availability_observation | 1d ago | 8270ca724f00a104… |
| hosting_provider_observation | 1d ago | e7292135d1d3f6bd… |
| tls_certificate_observation | 1d ago | 157b7693f876641e… |
| oauth_metadata_observation | 1d ago | 41da3ace526bd422… |
| mcp_protocol_observation | 1d ago | 5f4c66c82509bed4… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of mcp.cut.pro to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.