com.atkvn/security-checks · v0.2.0 · security
ATK Security Checks is healthy: it completed an MCP handshake in 1571 ms and exposes 4 tools.
Post-quantum TLS + cert checks; Wazuh rules tested on a real manager: does your rule fire?
Endpoint: https://atkvn.com/agent/mcp (streamable-http)
No repository listed · Website · JSON · Add to my inventory
| Users (last 30 days) | 0 |
| Handshake | Healthy |
| Auth needed | None |
| Tool count | 4 |
| Latency | 1571 ms |
| Last checked (UTC) | 2026-10-22T16:50:14.611Z |
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-10-22T16:50:14.611Z | Healthy | 1571 |
check_post_quantum_tls | Does this public hostname negotiate hybrid post-quantum key exchange (X25519MLKEM768)? Returns TLS version, hybrid yes/no and a one-line verdict. Free. One TLS handshake per probe, no scanning. |
check_tls_certificate | Certificate issuer, expiry date, days left, and whether the chain verifies for the hostname from a strict client (catches missing intermediate certificates and name mismatches). Free. |
audit_wazuh_rules | Finds Wazuh custom rules that pass wazuh-analysisd -t but are dropped at load (load order across ruleset/rules and etc/rules, missing parents, duplicate or colliding ids). Input: list of {filename, xml}. Supported versions: 4.14.7, 4.14.9. Free: counts + 2 findings. Full report: pass api_key. |
test_wazuh_rule | Runs log lines through a real wazuh-manager 4.14.9 (fresh logtest session) with your custom rules and decoders: which decoder and rule matched, whether YOUR rule fired, and load warnings such as 7617/7619. Logtest engine: frequency/timeframe rules and some live-only behaviour are out of scope. Free: |