1cnf-verifier

Each tool targets a distinct verification concern—hashes, state intervals, agent policies, plan trajectories, embeddings, trade bounds, memory assertions, and risk vectors. The close pairing of verify_1cnf_invariants and verify_liquidity_invariant is mitigated by their clear descriptions, though both being 'invariant' checks creates slight potential for confusion.

The overwhelming majority follow a consistent verify_<domain> pattern, making the set predictable. The single exception is check_threat_blacklist, which swaps 'verify' for 'check', creating a minor deviation without breaking overall readability.

Eight tools is well within the ideal range and suits a verification-focused server. Each tool covers a distinct verification category, and none feel redundant or superfluous.

The tool surface covers a broad set of verification domains—security, invariants, planning, embeddings, liquidity, memory, and risk. It lacks an aggregate 'run all verifications' or status tool, but the individual coverage is strong enough that agents can perform the intended verification workflows.