Assura
OfficialRelated Servers
Alternatives to Assura
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables AI agents to write, compose, and check assume-guarantee contracts, including refinement, consistency, compatibility, realizability, and LTL checks, and to use returned counterexamples to fix specifications.39513 PyPIBSD 3-Clause
- AlicenseAqualityCmaintenanceEnables AI coding agents and IDEs to prove SystemVerilog assertions with SymbiYosys (smtbmc+z3) and lint SVA syntax, returning honest verdicts such as PROVEN, FAILED, UNKNOWN, ERROR, or TIMEOUT.314 npmApache 2.0
- AlicenseAqualityCmaintenanceEnables logical entailment and satisfiability checks by dispatching formal SMT-LIB queries to both Z3 and cvc5, returning auditable solver verdicts, counterexamples, and caveats.4MIT
- AlicenseAqualityBmaintenanceDeterministic AI safety policy engine with Z3 formal verification. Write, verify, simulate, and enforce machine-verifiable safety constraints for AI agents. Completely outside the LLM.1198 PyPI27Apache 2.0
- AlicenseNot gradedqualityNot gradedmaintenanceEnables formal verification of LLM outputs against compliance ontologies using Z3 SMT solver. Validates that AI-generated content adheres to regulatory requirements like HIPAA or mortgage compliance rules.MIT
- AlicenseBqualityCmaintenanceEnables autonomous agents and developers to pay per call in Base USDC to run formal cryptographic invariant verification, including vault rounding, Polymarket solvency, ZK witness uniqueness, and differential consensus checks using Z3 SMT and bounded algebraic solvers.5MIT
TDQS
Scored across 6 tools
Each tool targets a distinct stage of the verification workflow: check (contract verification), ir_verify (IR verification), ir_prompt (IR generation prompt), infer (contract inference), type_map (type conversion), and explain (error lookup). The closest pair is assura_check and assura_ir_verify, but the descriptions clearly distinguish whole-contract verification from Implementation IR clause checking.
All tools share the assura_ prefix and snake_case, which gives a predictable namespace. The suffixes mix verbs (check, infer, explain) with noun-ish compounds (ir_verify, ir_prompt, type_map), a minor deviation but still readable and grouped by the ir_ family.
Six tools is well-scoped for a contract verification server, with each tool corresponding to a clear step (infer, type map, prompt, verify, check, explain). No tool feels redundant or trivial.
The surface covers the full loop: infer a contract from Rust, map types, render an IR prompt, verify IR, check contracts, and explain errors. Minor gaps exist, such as no tool to apply or auto-fix diagnostics or to list/decompose multi-contract files beyond the decl parameter.