aicommander.dev
https://aicommander.dev/mcp
81
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 7h ago
Why this score
| oauth_metadata_present | +14 |
| mcp_requires_authentication | +10 |
| tls_present_and_valid | +4 |
| reachable | +2 |
| hsts_enabled | +1 |
Findings (0)
No findings from the current evidence set.
Evidence (7)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 7h ago | 3e0b28ca97cff563… |
| http_response_observation | 7h ago | 00ad943a5c6d5f9c… |
| availability_observation | 7h ago | 0f859c6f7b8027b6… |
| hosting_provider_observation | 7h ago | e7292135d1d3f6bd… |
| tls_certificate_observation | 7h ago | 1eb8c3c44a9b278b… |
| oauth_metadata_observation | 7h ago | d6a8fae70c7741af… |
| mcp_protocol_observation | 7h ago | 5f4c66c82509bed4… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of aicommander.dev to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.