api.reglyze.com
https://api.reglyze.com/mcp
61
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 4h ago
Why this score
| tls_present_and_valid | +4 |
| mcp_capabilities_discoverable | +4 |
| reachable | +2 |
| hsts_enabled | +1 |
Findings (1)
| info | CORS allows any origin cors.wildcard_origin @ 1.0.0 |
Evidence (8)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 4h ago | 7c86f1d712478d6f… |
| http_response_observation | 4h ago | 74e561b61b2e4e1e… |
| availability_observation | 4h ago | 7d5810af25dc8a00… |
| hosting_provider_observation | 4h ago | e7292135d1d3f6bd… |
| tls_certificate_observation | 4h ago | 6d2758987095879a… |
| oauth_metadata_observation | 4h ago | 0d9f0abdf74479b5… |
| mcp_protocol_observation | 4h ago | cee2f219b606a7f8… |
| mcp_capability_observation | 4h ago | 27452792f937fc94… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of api.reglyze.com to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.