Home / MCP registry index / io.github.mcp-dir/datacrazy-mcp
DataCrazy
io.github.mcp-dir/datacrazy-mcp in the official MCP registry.
Endpoint https://api.mcp.ai/p_datacrazy. Source: github.com/mcp-dir/datacrazy-mcp.
The registry describes it as: DataCrazy omnichannel CRM (WhatsApp, Instagram, Facebook) via the official API: leads, deals, pipeli
We read its 70 tools on 2026-10-21. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
datacrazy_list_accounts datacrazy_activities_create datacrazy_activities_delete datacrazy_activities_get datacrazy_activities_list datacrazy_activities_patch datacrazy_attendants_crm_get datacrazy_attendants_crm_list datacrazy_attendants_multi_get datacrazy_attendants_multi_list datacrazy_business_loss_reasons_create datacrazy_business_loss_reasons_delete datacrazy_business_loss_reasons_get datacrazy_business_loss_reasons_list datacrazy_business_loss_reasons_update datacrazy_businesses_actions_lose_create datacrazy_businesses_actions_move_create datacrazy_businesses_actions_restore_create datacrazy_businesses_actions_win_create datacrazy_businesses_create datacrazy_businesses_delete datacrazy_businesses_get datacrazy_businesses_list datacrazy_businesses_patch datacrazy_conversations_finish_create datacrazy_conversations_list datacrazy_conversations_messages_create datacrazy_conversations_messages_list datacrazy_instances_get datacrazy_instances_list datacrazy_leads_activities_list datacrazy_leads_additional_fields_create datacrazy_leads_attachments_create datacrazy_leads_attachments_delete datacrazy_leads_attachments_list datacrazy_leads_businesses_list datacrazy_leads_create datacrazy_leads_delete datacrazy_leads_get datacrazy_leads_history_list datacrazy_leads_list datacrazy_leads_notes_create datacrazy_leads_notes_delete datacrazy_leads_notes_list datacrazy_leads_notes_update datacrazy_leads_patch datacrazy_lists_create datacrazy_lists_delete datacrazy_lists_get datacrazy_lists_list datacrazy_lists_update datacrazy_pipelines_get datacrazy_pipelines_list datacrazy_pipelines_stages_list datacrazy_products_create datacrazy_products_delete datacrazy_products_get datacrazy_products_list datacrazy_products_update datacrazy_tags_create and 10 more
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-mcp-dir-datacrazy-mcp)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.