ozmoz

io.ozmoz/ozmoz · version 0.1.78 · 2,519 weekly npm downloads · audited 2026-11-03

Notes

Findings

No hidden-instruction or invisible-character findings in any tool, prompt, or resource description.

Claude Connectors Directory readiness

❌ Every tool has a title Missing on 4 of 4: oz_create_project, oz_update_project, oz_publish_function, oz_get_contract
❌ Every tool declares readOnlyHint or destructiveHint Missing on 4 of 4: oz_create_project, oz_update_project, oz_publish_function, oz_get_contract
✅ Tool names are 64 characters or fewer All within limit
❌ Descriptions avoid instructions about model behavior or other tools 2 of 4 descriptions reference other tools or tell the model what it must do: oz_create_project, oz_publish_function
✅ No hidden instructions or invisible characters in tool metadata None found

Checks the directory's published tool requirements that are visible from tools/list. Passing them does not guarantee acceptance.

Supply chain

Install scripts: none
npm provenance: no
Source repository linked: no
License: UNLICENSED
Direct dependencies: 0

Tools (4)

Name	Hint	Description
`oz_create_project`	none	Use this when the user asks to build an app with OZmoz or to store an app's data with OZmoz. Creates a NEW OZmoz Cloud project. Call this ONLY when starting a brand new application from scratch. DO NOT call it if the pro…
`oz_update_project`	none	HARD STOP: call this tool ONLY after the user has explicitly approved the screens in a message that arrived AFTER you gave them the dev-server address (first sealing), or when they ask for a data change (later). NEVER in…
`oz_publish_function`	none	Deploys an OZmoz serverless function to the VM Sandbox. HARD STOP: Serverless functions incur infrastructure costs. NEVER call this tool without having explicitly explained its intent and obtained the user's explicit pri…
`oz_get_contract`	none	Call this FIRST whenever the user mentions OZmoz. Provides the official data contract, SDK directives, production lifecycle and canonical blueprint.

Check your own setup

npx mcpvetter scan --live

Badge

Add this to a README:

[![MCPVetter](https://mcpvetter.com/badge/ozmoz.svg)](https://mcpvetter.com/servers/ozmoz)

Publish this server?

Get the MCPVetter verified badge, a re-audit within 24 hours of every npm release, and an email whenever tools, findings, or Claude directory readiness change. $29 per server per month. You prove ownership first, free.