DataCrazy
REMOTE · API.MCP.AI · SCANNED OCT 6
DataCrazy omnichannel CRM (WhatsApp, Instagram, Facebook) via the official API: leads, deals, pipeli
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability59
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 4752 tokens (~67/item across 70 items; 70 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 9 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 71 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the DataCrazy MCP server?
DataCrazy is a hosted endpoint at https://api.mcp.ai/p_datacrazy, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.mcp.ai
claude mcp add --transport http mcp-dir-datacrazy-mcp 'https://api.mcp.ai/p_datacrazy'
{
"mcpServers": {
"mcp-dir-datacrazy-mcp": {
"url": "https://api.mcp.ai/p_datacrazy"
}
}
} {
"servers": {
"mcp-dir-datacrazy-mcp": {
"type": "http",
"url": "https://api.mcp.ai/p_datacrazy"
}
}
} [mcp_servers.mcp-dir-datacrazy-mcp] url = "https://api.mcp.ai/p_datacrazy"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"mcp-dir-datacrazy-mcp": {
"type": "remote",
"url": "https://api.mcp.ai/p_datacrazy",
"enabled": true
}
}
} openclaw mcp add mcp-dir-datacrazy-mcp --url 'https://api.mcp.ai/p_datacrazy' --transport streamable-http
mcp_servers:
mcp-dir-datacrazy-mcp:
url: "https://api.mcp.ai/p_datacrazy" {
"McpServers": {
"mcp-dir-datacrazy-mcp": {
"Transport": "http",
"Url": "https://api.mcp.ai/p_datacrazy"
}
}
} assistant mcp add mcp-dir-datacrazy-mcp -t streamable-http -u 'https://api.mcp.ai/p_datacrazy'
{
"mcpServers": {
"mcp-dir-datacrazy-mcp": {
"type": "http",
"url": "https://api.mcp.ai/p_datacrazy"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 6 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 0.9.358 → 0.9.365 functional
- 4 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 0.9.356 → 0.9.358 functional
- 3 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 0.9.353 → 0.9.356 functional
- 2 Oct 26 0
- Stability: 0.97 → pass security
- 1 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 0.9.351 → 0.9.353 functional
- 29 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 6 Oct 2026 · Probed https://api.mcp.ai/p_datacrazy
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.ai | CN=WE1,O=Google Trust Services,C=US | 28 Sept 2026 | 27 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 1bf4d405299e078a0e62ff16cded599b |
| SANs: mcp.ai, *.mcp.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.mcp.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| mcp.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.mcp.ai/p_datacrazy | Verified | 200 | |
| http (plaintext) | http://api.mcp.ai/p_datacrazy | Inconclusive | 406 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
authenticate ~99
MCP.AI for IDE agents (Cursor, etc.): log in in the browser, copy the access token. Best: add it to this server's config as a header `Authorization: Bearer <token>` for a permanent, non-expiring connection. Or paste it here for a session-only login: call with { token: "<jwt>" } after the user pastes, or with no args to get the link.
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | – | – |
No output schema declared.
No examples provided.
connect ~42
Returns connection status and URLs. When all providers are connected, returns authenticated:true and empty pending[]. When credentials are missing, returns connect_url for the toolkit and per-install URLs.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
datacrazy_activities_create ~45
Criar atividade (POST /api/v1/activities). [write, altera dados]
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| body | string | – | – |
No output schema declared.
No examples provided.
datacrazy_activities_delete ~71
Excluir atividade (DELETE /api/v1/activities/{id}). [write, altera dados] Bulk support: accepts ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| body | string | – | – |
| id | string | yes | – |
| ids | array | – | – |
No output schema declared.
No examples provided.
datacrazy_activities_get ~67
Buscar atividade por ID (GET /api/v1/activities/{id}). Bulk support: accepts ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| id | string | yes | – |
| ids | array | – | – |
| query | string | – | – |
No output schema declared.
No examples provided.
datacrazy_activities_list ~38
Buscar atividades (GET /api/v1/activities).
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| query | string | – | – |
No output schema declared.
No examples provided.
datacrazy_activities_patch ~71
Atualizar atividade (PATCH /api/v1/activities/{id}). [write, altera dados] Bulk support: accepts ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| body | string | – | – |
| id | string | yes | – |
| ids | array | – | – |
No output schema declared.
No examples provided.
datacrazy_attendants_crm_get ~76
Buscar atendente por ID (CRM) (GET /api/v1/attendants/crm/{id}). Bulk support: accepts ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| id | string | yes | – |
| ids | array | – | – |
| query | string | – | – |
No output schema declared.
No examples provided.
datacrazy_attendants_crm_list ~47
Buscar atendentes (CRM) (GET /api/v1/attendants/crm).
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| query | string | – | – |
No output schema declared.
No examples provided.
datacrazy_attendants_multi_get ~78
Buscar atendente por ID (multiatendimento) (GET /api/v1/attendants/multi/{id}). Bulk support: accepts ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| id | string | yes | – |
| ids | array | – | – |
| query | string | – | – |
No output schema declared.
No examples provided.
datacrazy_attendants_multi_list ~48
Buscar atendentes (multiatendimento) (GET /api/v1/attendants/multi).
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| query | string | – | – |
No output schema declared.
No examples provided.
datacrazy_business_loss_reasons_create ~51
Criar motivo de perda (POST /api/v1/business-loss-reasons). [write, altera dados]
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| body | string | – | – |
No output schema declared.
No examples provided.
datacrazy_business_loss_reasons_delete ~77
Excluir motivo de perda (DELETE /api/v1/business-loss-reasons/{id}). [write, altera dados] Bulk support: accepts ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| body | string | – | – |
| id | string | yes | – |
| ids | array | – | – |
No output schema declared.
No examples provided.
datacrazy_business_loss_reasons_get ~73
Buscar motivos de perda por ID (GET /api/v1/business-loss-reasons/{id}). Bulk support: accepts ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| id | string | yes | – |
| ids | array | – | – |
| query | string | – | – |
No output schema declared.
No examples provided.
datacrazy_business_loss_reasons_list ~44
Buscar motivos de perda (GET /api/v1/business-loss-reasons).
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| query | string | – | – |
No output schema declared.
No examples provided.
datacrazy_business_loss_reasons_update ~77
Atualizar motivo de perda (PUT /api/v1/business-loss-reasons/{id}). [write, altera dados] Bulk support: accepts ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| body | string | – | – |
| id | string | yes | – |
| ids | array | – | – |
No output schema declared.
No examples provided.
datacrazy_businesses_actions_lose_create ~51
Perder negócios (POST /api/v1/businesses/actions/lose). [write, altera dados]
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| body | string | – | – |
No output schema declared.
No examples provided.
datacrazy_businesses_actions_move_create ~50
Mover negócios (POST /api/v1/businesses/actions/move). [write, altera dados]
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| body | string | – | – |
No output schema declared.
No examples provided.
datacrazy_businesses_actions_restore_create ~50
Restaurar negócios (POST /api/v1/businesses/actions/restore). [write, altera dados]
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| body | string | – | – |
No output schema declared.
No examples provided.
datacrazy_businesses_actions_win_create ~50
Ganhar negócios (POST /api/v1/businesses/actions/win). [write, altera dados]
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| body | string | – | – |
No output schema declared.
No examples provided.
datacrazy_businesses_create ~45
Criar negócio (POST /api/v1/businesses). [write, altera dados]
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| body | string | – | – |
No output schema declared.
No examples provided.
datacrazy_businesses_delete ~71
Excluir negócio (DELETE /api/v1/businesses/{id}). [write, altera dados] Bulk support: accepts ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| body | string | – | – |
| id | string | yes | – |
| ids | array | – | – |
No output schema declared.
No examples provided.
datacrazy_businesses_get ~67
Buscar negócio por ID (GET /api/v1/businesses/{id}). Bulk support: accepts ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| id | string | yes | – |
| ids | array | – | – |
| query | string | – | – |
No output schema declared.
No examples provided.
datacrazy_businesses_list ~38
Buscar negócios (GET /api/v1/businesses).
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| query | string | – | – |
No output schema declared.
No examples provided.
datacrazy_businesses_patch ~71
Atualizar negócio (PATCH /api/v1/businesses/{id}). [write, altera dados] Bulk support: accepts ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| body | string | – | – |
| id | string | yes | – |
| ids | array | – | – |
No output schema declared.
No examples provided.
datacrazy_conversations_finish_create ~74
Finalizar atendimento (POST /api/v1/conversations/{id}/finish). [write, altera dados] Bulk support: accepts ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| body | string | – | – |
| id | string | yes | – |
| ids | array | – | – |
No output schema declared.
No examples provided.
datacrazy_conversations_list ~39
Buscar conversas (GET /api/v1/conversations).
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| query | string | – | – |
No output schema declared.
No examples provided.
datacrazy_conversations_messages_create ~77
Enviar mensagem para uma conversa (POST /api/v1/conversations/{id}/messages). [write, altera dados] Bulk support: accepts ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| body | string | – | – |
| id | string | yes | – |
| ids | array | – | – |
No output schema declared.
No examples provided.
datacrazy_conversations_messages_list ~69
Buscar conversa por ID (GET /api/v1/conversations/{id}/messages). Bulk support: accepts ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| id | string | yes | – |
| ids | array | – | – |
| query | string | – | – |
No output schema declared.
No examples provided.
datacrazy_instances_get ~66
Buscar instancia por ID (GET /api/v1/instances/{id}). Bulk support: accepts ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| id | string | yes | – |
| ids | array | – | – |
| query | string | – | – |
No output schema declared.
No examples provided.
datacrazy_instances_list ~38
Buscar instancias (GET /api/v1/instances).
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| query | string | – | – |
No output schema declared.
No examples provided.
datacrazy_leads_activities_list ~71
Buscar as atividades do lead (GET /api/v1/leads/{id}/activities). Bulk support: accepts ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| id | string | yes | – |
| ids | array | – | – |
| query | string | – | – |
No output schema declared.
No examples provided.
datacrazy_leads_additional_fields_create ~54
Criar lead com campos adicionais (POST /api/v1/leads/additional-fields). [write, altera dados]
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| body | string | – | – |
No output schema declared.
No examples provided.
datacrazy_leads_attachments_create ~63
Anexar arquivo ao lead (POST /api/v1/leads/{leadId}/attachments). [write, altera dados]
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| body | string | – | – |
| leadId | string | yes | – |
No output schema declared.
No examples provided.
datacrazy_leads_attachments_delete ~90
Apagar arquivo anexado ao lead (DELETE /api/v1/leads/{leadId}/attachments/{id}). [write, altera dados] Bulk support: accepts ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| body | string | – | – |
| id | string | yes | – |
| ids | array | – | – |
| leadId | string | yes | – |
No output schema declared.
No examples provided.
datacrazy_leads_attachments_list ~58
Buscar os arquivos anexados ao lead (GET /api/v1/leads/{leadId}/attachments).
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| leadId | string | yes | – |
| query | string | – | – |
No output schema declared.
No examples provided.
datacrazy_leads_businesses_list ~72
Buscar os negocios do lead (GET /api/v1/leads/{id}/businesses). Bulk support: accepts ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| id | string | yes | – |
| ids | array | – | – |
| query | string | – | – |
No output schema declared.
No examples provided.
datacrazy_leads_create ~45
Criar lead (POST /api/v1/leads). [write, altera dados]
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| body | string | – | – |
No output schema declared.
No examples provided.
datacrazy_leads_delete ~71
Excluir lead (DELETE /api/v1/leads/{id}). [write, altera dados] Bulk support: accepts ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| body | string | – | – |
| id | string | yes | – |
| ids | array | – | – |
No output schema declared.
No examples provided.
datacrazy_leads_get ~67
Buscar lead por ID (GET /api/v1/leads/{id}). Bulk support: accepts ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| id | string | yes | – |
| ids | array | – | – |
| query | string | – | – |
No output schema declared.
No examples provided.
datacrazy_leads_history_list ~69
Buscar histórico do lead (GET /api/v1/leads/{id}/history). Bulk support: accepts ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| id | string | yes | – |
| ids | array | – | – |
| query | string | – | – |
No output schema declared.
No examples provided.
datacrazy_leads_list ~38
Buscar leads (GET /api/v1/leads).
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| query | string | – | – |
No output schema declared.
No examples provided.
datacrazy_leads_notes_create ~59
Adicionar comentário (POST /api/v1/leads/{leadId}/notes). [write, altera dados]
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| body | string | – | – |
| leadId | string | yes | – |
No output schema declared.
No examples provided.
datacrazy_leads_notes_delete ~87
Excluir comentário do lead (DELETE /api/v1/leads/{leadId}/notes/{id}). [write, altera dados] Bulk support: accepts ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| body | string | – | – |
| id | string | yes | – |
| ids | array | – | – |
| leadId | string | yes | – |
No output schema declared.
No examples provided.
datacrazy_leads_notes_list ~54
Buscar comentários do lead (GET /api/v1/leads/{leadId}/notes).
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| leadId | string | yes | – |
| query | string | – | – |
No output schema declared.
No examples provided.
datacrazy_leads_notes_update ~87
Atualizar comentário do lead (PUT /api/v1/leads/{leadId}/notes/{id}). [write, altera dados] Bulk support: accepts ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| body | string | – | – |
| id | string | yes | – |
| ids | array | – | – |
| leadId | string | yes | – |
No output schema declared.
No examples provided.
datacrazy_leads_patch ~71
Atualizar lead (PATCH /api/v1/leads/{id}). [write, altera dados] Bulk support: accepts ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| body | string | – | – |
| id | string | yes | – |
| ids | array | – | – |
No output schema declared.
No examples provided.
datacrazy_list_accounts ~39
Lista as conexões (contas) DataCrazy vinculadas a este install — id, label.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
No output schema declared.
No examples provided.
datacrazy_lists_create ~44
Criar lista (POST /api/v1/lists). [write, altera dados]
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| body | string | – | – |
No output schema declared.
No examples provided.
datacrazy_lists_delete ~70
Excluir lista (DELETE /api/v1/lists/{id}). [write, altera dados] Bulk support: accepts ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| body | string | – | – |
| id | string | yes | – |
| ids | array | – | – |
No output schema declared.
No examples provided.
What is the DataCrazy MCP server?
DataCrazy is an MCP server listed in the public MCP registry as io.github.mcp-dir/datacrazy-mcp. DataCrazy omnichannel CRM (WhatsApp, Instagram, Facebook) via the official API: leads, deals, pipeli. This page covers its hosted endpoint (https://api.mcp.ai/p_datacrazy).
Is the DataCrazy MCP server safe to use?
DataCrazy scores 75 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the DataCrazy MCP server expose?
DataCrazy exposes 70 tools: datacrazy_list_accounts, datacrazy_activities_create, datacrazy_activities_delete, datacrazy_activities_get, datacrazy_activities_list, and 65 more. Their descriptions and schemas cost roughly 4,621 tokens of context every time the server is loaded.
Does the DataCrazy MCP server require authentication?
No. We connected to DataCrazy without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the DataCrazy MCP server still maintained?
DataCrazy is still listed as active in the MCP registry. We last reached this channel on 6 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.