mcp.mux.com
https://mcp.mux.com/
67
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 1d ago
Why this score
| oauth_metadata_present | +14 |
| mcp.unauthenticated_consequential_tools | -8 |
| tls_present_and_valid | +4 |
| mcp_capabilities_discoverable | +4 |
| reachable | +2 |
| hsts_enabled | +1 |
Findings (1)
| medium | Capabilities are listable without authentication, including 1 whose name suggests state change (execute) — inferred from tool names, not confirmed mcp.unauthenticated_consequential_tools @ 1.0.0 |
Evidence (8)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 1d ago | 1319ea95b94860f0… |
| http_response_observation | 1d ago | 689057114a9f695c… |
| availability_observation | 1d ago | 90b1ae444bd08072… |
| hosting_provider_observation | 1d ago | 07b610f7cd67ffa2… |
| tls_certificate_observation | 1d ago | 0d6a2f892854de6d… |
| oauth_metadata_observation | 1d ago | a5ad9c729c3ce9b3… |
| mcp_protocol_observation | 1d ago | 63a188bd853efcab… |
| mcp_capability_observation | 1d ago | 9b8e41d2f55d9314… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of mcp.mux.com to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.