Someone describes their week in ordinary words and gets back a scored breakdown, a direction of travel, and something to do about it. The team side returns aggregates rather than a list of named individuals, and every output repeats that persistent exhaustion is a matter for a doctor.
A client for the StressZero Intelligence API. It scores self-reported answers on physical, emotional and effectiveness dimensions and returns a total with a risk level, the factors behind it and prevention suggestions. The scores are indicative and self-assessed — the server states plainly that it is not a medical device and offers no diagnosis or triage.
- A 0-100 total with a risk level of low, moderate, high or critical, from 3 to 20 response items covering all three dimensions
- A one-line screen for conversation: three scores in, the same assessment out with sensible defaults filled in
- A full report with dimension-by-dimension interpretation and immediate, short-term and long-term action plans
- Team-level analysis over 2 to 500 members returning averages, spread, distribution by risk band and a department breakdown, with an anonymize option — and each member counted as one API call
- A projection of where the scores go over 7, 14 and 30 days, with a trajectory label and a days-to-critical estimate
- Answers in either French or English, and an OpenAPI 3.1 specification exposed as a resource
- A free API key created from inside the conversation for someone who has none, and a health check that needs no authentication at all
STRESSZERO_API_KEY, a key starting sz_live_ from stresszeroentrepreneur.fr — the free tier needs no card, and the server can mint one for a user in the conversation. Runs over stdio from npm as stresszero-mcp. STRESSZERO_API_URL moves the base URL. The report and the team analysis need the Starter tier or above; on the free tier they return 403.
One command plus a key — npx -y stresszero-mcp, then supply credentials