Learn · Building Cindra

Measuring safety: VERA-MH and the five-axis evaluation.

You cannot ship what you cannot test. For mental health AI, the tests now exist, and they have known blind spots.

Karuna LabsUpdated 2026-10-025 min read
The short answer

VERA-MH is an open-source automated benchmark for evaluating how an AI chatbot detects and responds to suicide risk. It scores five dimensions: detecting risk, confirming it with direct questions, guiding to human care, addressing barriers, and following up. Clinician agreement on the rubric was 0.77 and the automated judge matched clinician consensus at 0.80 to 0.82, with sensitivity for high-harm responses between 77 and 85 percent. A broader five-axis framework adds protocol fidelity, hallucination risk, behavioral consistency, and demographic robustness. The research position is that no mental health AI should deploy without passing evaluation on all of them, and that even then, continuous monitoring is required.

For most of the short history of mental health chatbots, safety was asserted rather than measured. A systematic review in JMIR AI of 20 studies of large language model chatbots for counseling found that none reported a registered randomized trial, none reported independent clinical validation in a real care setting, and only three used psychometrically validated tools. Evaluation focused on how the language sounded, not on what happened to people.

That is changing, and the tools worth knowing are VERA-MH and the five-axis framework.

VERA-MH

VERA-MH is an open-source, automated benchmark published through JMIR AI for evaluating chatbot safety in suicide-risk detection and response. It uses simulated conversations and a rubric with five dimensions, each with a defined best practice and a defined high-harm failure.

The reliability numbers are the reason to take it seriously. Clinicians rating the same conversations agreed with each other at an alpha of 0.77. The automated LLM judge agreed with clinician consensus at 0.80 to 0.82, which is to say the machine grader was about as consistent with the clinicians as the clinicians were with each other. That is what makes it usable in an automated pipeline.

The sensitivity numbers are the reason not to rely on it alone. VERA-MH caught between 77.4 and 84.9 percent of responses with high potential for harm. That leaves roughly one in six harmful responses undetected. A benchmark with that miss rate is a valuable gate and an inadequate sole gate, and the research synthesis for Cindra says exactly that.

The five-axis framework

VERA-MH covers crisis. A mental health companion can fail in other ways, and a preprint studying safety alignment in therapy proposed five axes that together cover the territory.

Protocol fidelity. Does the system actually deliver the therapy it claims to? A companion built on ACT should produce ACT, including the parts that involve not agreeing with the user. This is the axis most products never measure, and it is where safety training can silently break therapy.

Hallucination risk. Does it make things up? Clinical facts, resources, the user's own history.

Behavioral consistency. Does it respond the same way to the same situation across sessions, phrasings, and days? A system that is safe on Tuesday and unsafe on Thursday is unsafe.

Crisis safety. VERA-MH's territory.

Demographic robustness. Does it hold up across age, gender, culture, language, and the ways different communities describe distress? The research flags this as largely untested across the field, which means every team is responsible for testing it on its own population.

The authors mapped these axes onto FDA software-as-a-medical-device guidance and the EU AI Act, and their position is unambiguous: no AI mental health system should proceed to deployment without passing multi-axis evaluation across all five.

Putting it in the pipeline

The practical recommendation is to run VERA-MH, or an equivalent, as part of continuous integration, the same way a software team runs its test suite. Every model change, every prompt change, every retrieval update gets scored before it ships. The five-axis evaluation runs on a longer cadence and before any major release.

Three things make this work in practice. The scenario set has to be maintained like code, with new failure cases added as they are discovered in production. The human review that validated the automated judge has to be repeated periodically so the judge does not drift. And the false-negative rate has to be covered by something else: human review of flagged conversations, user-facing escalation paths, and post-deployment monitoring. The three-stage governance framework in the literature calls this continuous oversight, and we cover it in governance and safety levels.

What the field still cannot measure

The JMIR AI review's findings bear repeating. No registered trials. No independent validation in real care. Standard clinical measures like the PHQ-9 and GAD-7 barely used. The benchmarks above measure whether a system behaves safely in test conversations. They do not measure whether people get better. That requires the slow, expensive work of clinical trials, which the field has mostly skipped. A team that passes VERA-MH and the five axes has met the floor. It has not shown that its product helps.

Cindra runs crisis evaluation against VERA-MH's five dimensions as a release gate, maintains an ACT-specific protocol fidelity test set, and tracks functional outcomes over time rather than taking test performance as evidence of benefit. The design guide describes the evaluation stack.

If you are building one

Find your false negatives

Take fifty production conversations your automated safety check passed. Have two clinicians review them blind. Count the ones they would have flagged. That number, divided by fifty, is your real miss rate, and it is the figure that belongs in your risk register next to the benchmark score.

Questions people ask

What is VERA-MH?

An open-source, automated benchmark for evaluating how AI chatbots detect and respond to suicide risk. It scores five dimensions: detecting risk, confirming it, guiding to human care, addressing barriers, and following up. Its automated judge agrees with clinician consensus at about 0.80.

Is VERA-MH enough to certify a mental health chatbot as safe?

No. Its sensitivity for high-harm responses is 77 to 85 percent, so roughly one in six harmful responses is missed. It is a valuable automated gate that must be paired with human review, broader evaluation, and post-deployment monitoring.

What is the five-axis evaluation for mental health AI?

A framework covering protocol fidelity, hallucination risk, behavioral consistency, crisis safety, and demographic robustness. Its authors map it onto FDA and EU AI Act requirements and argue no mental health AI should deploy without passing all five.

Has any LLM mental health chatbot been clinically validated?

A JMIR AI review of 20 LLM counseling chatbot studies found no registered randomized trials and no independent validation in real care settings. Earlier conversational agents like Wysa and Woebot have early trials, but LLM-based companions remain largely unvalidated.

Design guide

The full engineering and safety guide.

These articles are the short version. Building Compassionate AI is the long one: an emotionally aware agent modeled as active inference, governed by an explicit compassion objective, bounded by safety rules. Written for the people who have to ship it.

Read the guide

This article describes an engineering and clinical-safety approach and the published evidence behind it, much of which is early. It is not legal, regulatory, or clinical advice. Thresholds quoted from Cindra's requirements document are initial proposals pending clinical and regulatory review.