ai.izap/whatsapp (ai.izap/whatsapp@1.16.1) The ai.izap/whatsapp MCP server, version 1.16.1, was published to the official MCP registry on 2026-09-09 as a hosted remote over streamable-http and filed under Chat & Messaging by the mcpindex index. A semantic screen of the server's description found no manipulation pattern and returned a pass status of PARTIAL, though mcpindex notes the deterministic conformance probe has not yet run and its confidence scores are uncalibrated at v1. The verdict was true at screening time in snapshot 2026-09-10, and mcpindex's gate pins the server's tool contracts to hold any silent drift before an agent acts. ← Index /leaderboard ai.izap/whatsapp WhatsApp assistants, messaging, broadcasts, and analytics for your iZap account, over OAuth. The current version, v1.16.1, was published to the official MCP registry on 2026-09-09. It is distributed as a hosted remote over streamable-http, filed under Chat & Messaging by this index. Removals and unreachable sources are measured across every server this index tracks, contract drift across the servers that answer in consecutive snapshots; the index's current counts /stats put this record in context. Using ai.izap/whatsapp in Claude, Cursor, Gemini CLI, Cline, or Zed? MCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and HOLDs the call when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself use Install this server for that . Rewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less uv tool install mcpindex-gate && mcpindex-config-wire method /methodology Semantic screen found no manipulation pattern in the description. Conformance probe not yet run. mcpindex.integrity.description passINFO evidence“Declares OAuth precondition, no secret access or data exfiltration”via static description - - Semantic screen only - the deterministic conformance probe has not run on this server - - Confidence is reported but not yet calibrated v1 - - Screen reads the tool description, not the live behavior - - advisory - - registry description only no input schema - - screen model 8b - - Still current: the description we screened is unchanged, re-checked against the registry - - The registry listing version, packages, links changed after this screen ran - the description we assessed did not Semantic screen: an LLM judge reads the tool description for hidden instructions status PARTIAL . A pass means the description is not lying, not that the tool is safe: a high-capability tool with an honest description still warrants caution. The deterministic conformance probe has not been run on this server yet, so the screen here is semantic-only. Posture: advisory. Confidences are reported but not yet calibrated calibrated=false at v1 . Full verdict history is not shown on this page. Own this server? Screen its description → /screen That verdict was true at screening time snapshot 2026-09-10 . Contracts can change after screening, with no version bump. The gate pins ai.izap/whatsapp’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday. See your first HOLD in 2 minutes → /guides/install-the-gate-first-hold Related: how to trust an MCP server /guides/how-to-trust-an-mcp-server · screen before install /guides/screen-mcp-server-before-install · silent contract drift /guides/mcp-silent-contract-drift People vet a server before wiring it in. One line on your project site or docs answers that with an independent record: screening verdict, registry provenance, contract drift history. It stays current as new screens and drift events land. Independent trust record for ai.izap/whatsapp https://mcpindex.ai/server/ai-izap-whatsapp - screening verdict, registry provenance, and contract drift monitoring.