runpay-backend-visibility-production.up.railway.app
https://runpay-backend-visibility-production.up.railway.app/mcp
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 (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 (8)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 2d ago | 59830d198d2ca914… |
| http_response_observation | 2d ago | ea4d1e68d4d467f3… |
| availability_observation | 2d ago | 96b5add44bf4768b… |
| hosting_provider_observation | 2d ago | f6ca63562d443d49… |
| tls_certificate_observation | 2d ago | 134128aa6d5a7f54… |
| oauth_metadata_observation | 2d ago | d631efb37e08c523… |
| mcp_protocol_observation | 2d ago | 0692d01aed6e0069… |
| mcp_capability_observation | 2d ago | feb9586a09fdfb30… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of runpay-backend-visibility-production.up.railway.app to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.