Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.bepunk/zoogent

NPM · ZOOGENT · SCANNED SEP 20

AI agent orchestrator with Architect AI. Multi-team, web dashboard, 35+ MCP tools.

Available components

npm · zoogent 30
0 this week 30 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security69
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects nodemailer 7.0.13, a direct dependency. A fixed version is available. View diagnostics → Fail
  • Install-script check failed: the install command fetches or executes arbitrary code (inline_eval). An install hook runs on every machine, in CI, and on transitive installs, whether or not you ever run the server. View diagnostics → Fail
  • Dependency health was assessed across the 342 of 343 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability0
  • Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we never saw its MCP handshake.Unverified

Unverified: 5 categories

Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

Install

How do I install the io.github.bepunk/zoogent MCP server?

io.github.bepunk/zoogent runs locally as an npm package, launched with npx -y zoogent. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · zoogent

# add to Claude Code
claude mcp add bepunk-zoogent -- npx -y zoogent
// .cursor/mcp.json
{
  "mcpServers": {
    "bepunk-zoogent": {
      "command": "npx",
      "args": [
        "-y",
        "zoogent"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "bepunk-zoogent": {
      "command": "npx",
      "args": [
        "-y",
        "zoogent"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add bepunk-zoogent -- npx -y zoogent
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "bepunk-zoogent": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "zoogent"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add bepunk-zoogent --command npx --arg -y --arg zoogent
# ~/.hermes/config.yaml
mcp_servers:
  bepunk-zoogent:
    command: "npx"
    args: ["-y", "zoogent"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "bepunk-zoogent": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "zoogent"
      ]
    }
  }
}
# add to Vellum
assistant mcp add bepunk-zoogent -t stdio -c npx -a -y zoogent
// mcp.json
{
  "mcpServers": {
    "bepunk-zoogent": {
      "command": "npx",
      "args": [
        "-y",
        "zoogent"
      ]
    }
  }
}
Changelog

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.

  • 18 Sept 26 0
    • CVE-2026-92598 affects this package: high ▼ security
    • CVE-2026-92595 affects this package: high ▼ security
    • CVE-2026-92597 affects this package: high ▼ security
    • CVE-2026-92596 affects this package: high ▼ security
    • GHSA-cc9r-2j5m-2m83 no longer affects this package ▲ security
    • GHSA-8m3c-c648-2xjj no longer affects this package ▲ security
    • GHSA-wmmp-3585-3rmp no longer affects this package ▲ security
    • GHSA-2x7j-588g-ccc2 no longer affects this package ▲ security
  • 9 Sept 26 0
    • CVE-2026-85063 affects this package: high ▼ security
    • GHSA-8m3c-c648-2xjj affects this package: high ▼ security
    • GHSA-2x7j-588g-ccc2 affects this package: high ▼ security
    • GHSA-cc9r-2j5m-2m83 affects this package: high ▼ security
    • GHSA-wmmp-3585-3rmp affects this package: high ▼ security
  • 8 Sept 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 7 Sept 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 5 Sept 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 4 Sept 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 2 Sept 26 0
    • CVE-2026-82662 affects this package: high ▼ security
    • CVE-2026-82659 affects this package: high ▼ security
    • CVE-2026-82854 affects this package: high ▼ security
    • CVE-2026-82853 affects this package: high ▼ security
    • CVE-2026-82660 affects this package: high ▼ security
    • CVE-2026-82661 affects this package: high ▼ security
    • GHSA-wqvq-jvpq-h66f no longer affects this package ▲ security
    • GHSA-vvjj-xcjg-gr5g no longer affects this package ▲ security
    • GHSA-c7w3-x93f-qmm8 no longer affects this package ▲ security
    • GHSA-p6gq-j5cr-w38f no longer affects this package ▲ security
    • GHSA-r7g4-qg5f-qqm2 no longer affects this package ▲ security
    • GHSA-268h-hp4c-crq3 no longer affects this package ▲ security
  • 29 Aug 26 0
    • Security disclosure: unverified → fail ▼ functional
Diagnostics

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 20 Sept 2026 · Analysed npm/zoogent@0.4.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
postinstall dangerous node -e "console.log('\n ZooGent installed. To get started:\n\n mkdir my-agents && cd my-agents\n zoogent init\n zoogent start\n claude mcp add zoogent -s project -- npx zoogent mcp\n claude\n\n Then type: help me build an agent team\n')"

Background: Why install scripts are a supply-chain risk →

Vulnerabilities 16 findings
ID CVE Severity Vector Fix available
GHSA-5474-4w2j-mq4c CVE-2026-34451 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N yes
GHSA-p7fg-763f-g4gf CVE-2026-41686 medium yes
GHSA-8cw4-87c7-c6xx CVE-2026-85063 medium yes
GHSA-67mh-4wv8-2f99 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N yes
GHSA-gh4j-gqv2-49f6 CVE-2026-41650 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N yes
GHSA-268h-hp4c-crq3 CVE-2026-82661 medium CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N yes
GHSA-2x7j-588g-ccc2 CVE-2026-92596 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-8m3c-c648-2xjj CVE-2026-92595 medium CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:N yes
GHSA-c7w3-x93f-qmm8 CVE-2026-82854 low yes
GHSA-cc9r-2j5m-2m83 CVE-2026-92597 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N yes
GHSA-p6gq-j5cr-w38f CVE-2026-82659 high CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N yes
GHSA-r7g4-qg5f-qqm2 CVE-2026-82662 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N yes
GHSA-vvjj-xcjg-gr5g CVE-2026-82853 medium CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N yes
GHSA-wmmp-3585-3rmp CVE-2026-92598 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N yes
GHSA-wqvq-jvpq-h66f CVE-2026-82660 medium CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N yes
GHSA-w5hq-g745-h8pq CVE-2026-41907 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 342 packages
Packages resolved 342
Deprecated 3
Stale 85
Tree resolution Partial

The dependency tree was only partially resolved, so these counts may be incomplete.

Background: SBOMs and build attestations, explained →

MCP tools

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 →

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

Common questions

What is the io.github.bepunk/zoogent MCP server?

io.github.bepunk/zoogent is an MCP server listed in the public MCP registry as io.github.bepunk/zoogent. AI agent orchestrator with Architect AI. Multi-team, web dashboard, 35+ MCP tools. This page covers its npm package (zoogent).

Is the io.github.bepunk/zoogent MCP server safe to use?

io.github.bepunk/zoogent scores 30 out of 100 on VerifyMCP. We recorded 16 known advisories against it as of 20 September 2026. It declares an install script we flagged as high risk. 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.

Is the io.github.bepunk/zoogent MCP server still maintained?

io.github.bepunk/zoogent is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.bepunk/zoogent MCP server under?

io.github.bepunk/zoogent declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.