io.github.adeiltonpessini/zapcore-mcp

io.github.adeiltonpessini/zapcore-mcpv0.1.0Chat & Messaging

Servidor MCP do zapCore (WhatsApp): leitura sempre, envio atrás de flag e allowlist de destino.

The current version, v0.1.0, was published to the official MCP registry on 2026-09-13. It is distributed as zapcore-mcp on npm and as the Docker image ghcr.io/adeiltonpessini/zapcore-mcp:0.1.0, filed under Chat & Messaging by this index, and declares 8 environment variables. 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 put this record in context.

In-path gate · all MCP tools

Using io.github.adeiltonpessini/zapcore-mcp 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).

Install the mcpindex gate (one command)

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

Auditable install path →Watch it hold a drift →

Trust verdict · v1 advisory · method

NOT YET SCREENEDno verdict on file

Verdict not yet evaluated for this tool. The semantic screen takes adversarial cases first; coverage rolls out as the corpus expands (15/150 labels to graduation). The deterministic conformance probe is built but has not yet run on the public corpus, so a recorded verdict here is REVIEW or UNVERIFIED, never a clearing ALLOW. Until a verdict is recorded, an agent should treat this tool as not-yet-cleared and fall back to its own checks. Method: the eval, four-state verdict, honest limits.

Own this server? Screen its description →

That verdict was true at screening time (snapshot 2026-09-13).

Contracts can change after screening, with no version bump. The gate pins io.github.adeiltonpessini/zapcore-mcp’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 →

Environment variables

ZAPCORE_TOKEN

requiredsecret

Token da instância zapCore (header `token` da API v2).

ZAPCORE_URL

Base da API do zapCore.

ZAPCORE_MCP_WRITE

`1`/`true`/`yes` registra as 4 tools de envio. Sem allowlist (ZAPCORE_MCP_ALLOW) o servidor recusa a subir.

ZAPCORE_MCP_ALLOW

Destinos autorizados a receber envio: telefones E.164 (só dígitos) separados por vírgula. Obrigatório quando ZAPCORE_MCP_WRITE está ligado.

ZAPCORE_MCP_TIMEOUT_MS

Timeout por chamada HTTP à API do zapCore, em milissegundos.

ZAPCORE_MCP_DOWNLOAD_DIR

Diretório onde `zap_media_download` grava o arquivo baixado.

ZAPCORE_CF_ACCESS_CLIENT_ID

secret

Client ID do service token do Cloudflare Access, se a base estiver atrás do Access. Anda em par com ZAPCORE_CF_ACCESS_CLIENT_SECRET — os dois ou nenhum.

ZAPCORE_CF_ACCESS_CLIENT_SECRET

secret

Client secret do service token do Cloudflare Access. Par de ZAPCORE_CF_ACCESS_CLIENT_ID.

ZAPCORE_TOKEN

requiredsecret

Token da instância zapCore.

ZAPCORE_URL

Base da API do zapCore.

ZAPCORE_MCP_WRITE

Liga as 4 tools de envio; exige ZAPCORE_MCP_ALLOW.

ZAPCORE_MCP_ALLOW

Destinos autorizados, E.164 separados por vírgula.

MCP quality score · maturity, not trust · methodology

freshness

completeness

installability

documentation

stability

Alternatives in Chat & Messaging

GuildControl MCP

app.lasers.guildcontrol/discord

Safety-first MCP server for Discord with privacy-safe reads, audits, and reviewed administration

Cavyro

com.cavyro/cavyro

Telegram-native CRM for agents: contacts, deals, pipelines, campaigns, docs and reports.

Multi-workspace Slack MCP server with draft+confirm safety, vault auto-export, a

io.github.adelaidasofia/slack-mcp

Multi-workspace Slack MCP server with draft+confirm safety, vault auto-export, and triple-mode…

Install this server

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "zapcore-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "--",
        "zapcore-mcp"
      ],
      "env": {
        "ZAPCORE_TOKEN": "<your-zapcore_token>",
        "ZAPCORE_URL": "https://zapcore.barberai.online",
        "ZAPCORE_MCP_WRITE": "0",
        "ZAPCORE_MCP_ALLOW": "<zapcore_mcp_allow>",
        "ZAPCORE_MCP_TIMEOUT_MS": "30000",
        "ZAPCORE_MCP_DOWNLOAD_DIR": "<TEMP>/zapcore-mcp",
        "ZAPCORE_CF_ACCESS_CLIENT_ID": "<your-zapcore_cf_access_client_id>",
        "ZAPCORE_CF_ACCESS_CLIENT_SECRET": "<your-zapcore_cf_access_client_secret>"
      }
    }
  }
}

Cursor (.cursor/mcp.json)

{
  "mcpServers": {
    "zapcore-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "--",
        "zapcore-mcp"
      ],
      "env": {
        "ZAPCORE_TOKEN": "<your-zapcore_token>",
        "ZAPCORE_URL": "https://zapcore.barberai.online",
        "ZAPCORE_MCP_WRITE": "0",
        "ZAPCORE_MCP_ALLOW": "<zapcore_mcp_allow>",
        "ZAPCORE_MCP_TIMEOUT_MS": "30000",
        "ZAPCORE_MCP_DOWNLOAD_DIR": "<TEMP>/zapcore-mcp",
        "ZAPCORE_CF_ACCESS_CLIENT_ID": "<your-zapcore_cf_access_client_id>",
        "ZAPCORE_CF_ACCESS_CLIENT_SECRET": "<your-zapcore_cf_access_client_secret>"
      }
    }
  }
}

Cline (cline_mcp_settings.json)

npx -y -- zapcore-mcp

Claude Code (claude mcp add)

claude mcp add --scope user zapcore-mcp -- npx -y -- zapcore-mcp

Gemini CLI (gemini mcp add)

gemini mcp add -s user zapcore-mcp npx -y -- zapcore-mcp

Claude Desktop (Docker)

{
  "mcpServers": {
    "zapcore-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "--",
        "ghcr.io/adeiltonpessini/zapcore-mcp:0.1.0"
      ],
      "env": {
        "ZAPCORE_TOKEN": "<your-zapcore_token>",
        "ZAPCORE_URL": "https://zapcore.barberai.online",
        "ZAPCORE_MCP_WRITE": "0",
        "ZAPCORE_MCP_ALLOW": "<zapcore_mcp_allow>",
        "ZAPCORE_MCP_TIMEOUT_MS": "30000",
        "ZAPCORE_MCP_DOWNLOAD_DIR": "<TEMP>/zapcore-mcp",
        "ZAPCORE_CF_ACCESS_CLIENT_ID": "<your-zapcore_cf_access_client_id>",
        "ZAPCORE_CF_ACCESS_CLIENT_SECRET": "<your-zapcore_cf_access_client_secret>"
      }
    }
  }
}

Verdict API

curl -s mcpindex.ai/api/v1/trust/server/io-github-adeiltonpessini-zapcore-mcp

Free-tier verdict as JSON: decision + dimensions + severity. Call it from your agent before it invokes a tool it just discovered.

Details

version: v0.1.0
category: Chat & Messaging
quality: 80 / 100
operator: adeiltonpessini

Listing

Listed from the official MCP registry. Unclaimed by its maintainer. Maintainer? Email us →

Provenance

Each verdict is bound to a hash of the exact description it judged, so a re-crawl that changes the text produces a new record rather than silently inheriting this one. Verdict history is hash-chained and anchored to Bitcoin via OpenTimestamps (latest confirmed at block 966,775). Verify it yourself.

Links

Repository →