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.

Zyrax Guard

NPM · ZYRAX-GUARD · SCANNED SEP 20

Audit AI agent configs for prompt injection & rogue MCP servers; vet packages

Available components

npm · zyrax-guard 94
0 this week 94 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 Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 0 of 6 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to tiagosilva07/zyrax-guard). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 44 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 219 tokens (~109/item across 2 items; 2 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 Coverage93
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 80% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 2 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
Install

How do I install the Zyrax Guard MCP server?

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

npm · zyrax-guard

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

  • 20 Sept 26 +1
    • Stability: 0.97 → pass security
  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 13 Sept 26 +1
    • Stability: 0.97 → pass security
  • 11 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 6 Sept 26 −3
    • Stability: pass → 0.77 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/zyrax-guard@0.13.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo tiagosilva07/zyrax-guard
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/tiagosilva07/zyrax-guard/.github/workflows/publish-npm.yml@refs/heads/main
Rekor log index 2357727573
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:246e995627d2febd728e48807492ebf9bfe93607786782653a512c85c7fad862e68b2977e8124522ab6324dd6b1a27c67f89af94e60dcddee4ff1637f

Background: How many MCP packages publish verified provenance →

Dependencies 6 packages
Packages resolved 6
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 2 exposed · ~219 tokens

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 →

Tool Tokens
check_package ~123

Vet a package for typosquats, known-malware, hallucinated names, and supply-chain risk BEFORE installing it. Returns SAFE, WARN, or BLOCK with reasons. Call this before running any package install. Set deep=true to also download the artifact and statically analyze install/build scripts (slower).

NameTypeReqDescription
deepboolean–download the artifact and statically analyze install/build scripts (slower)
ecosystemstring––
namestringyespackage name to check
versionstring–optional; defaults to the latest published version

No output schema declared.

No examples provided.

scan_agents ~96

Audit a directory for AI agent security risks: prompt injection in CLAUDE.md/AGENTS.md/GEMINI.md, malicious or unencrypted MCP server URLs, excessive permissions in settings.json, and supply-chain risks from unpinned npx MCP packages. Call this before running an agent in an unfamiliar repo, or in CI to gate agent config changes.

NameTypeReqDescription
dirstring–directory to scan (default: current working directory)

No output schema declared.

No examples provided.

Common questions

What is the Zyrax Guard MCP server?

Zyrax Guard is an MCP server listed in the public MCP registry as io.github.tiagosilva07/zyrax-guard. Audit AI agent configs for prompt injection & rogue MCP servers; vet packages. This page covers its npm package (zyrax-guard).

Is the Zyrax Guard MCP server safe to use?

Zyrax Guard scores 94 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Zyrax Guard MCP server expose?

Zyrax Guard exposes 2 tools: check_package, scan_agents. Their descriptions and schemas cost roughly 219 tokens of context every time the server is loaded.

Is the Zyrax Guard MCP server still maintained?

Zyrax Guard 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 Zyrax Guard MCP server under?

Zyrax Guard declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.