api.relux.works
https://api.relux.works/mcp
75
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 4d 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 | 4d ago | bd2b01583d05f7c9… |
| http_response_observation | 4d ago | bf729595983aa51a… |
| availability_observation | 4d ago | 9adeb3142b5263a8… |
| hosting_provider_observation | 4d ago | e7292135d1d3f6bd… |
| tls_certificate_observation | 4d ago | 829224af205236b0… |
| oauth_metadata_observation | 4d ago | b22403cae9763554… |
| mcp_protocol_observation | 4d ago | 5b57b235dd783f13… |
| mcp_capability_observation | 4d ago | a1790c2dbd6ea753… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of api.relux.works to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.