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.

WireCat MAX

NPM · @WIRECAT/MAX-CLI

Your MAX account and bots for agents: read, search, send messages. Sign in with the max CLI first.

Available components

npm · @wirecat/max-cli 37
+4 this week 37 Trust /100

Last scanned (5 hours ago)

Scores higher than 13% of npm servers

Category Communication

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 Security56
  • No malware found by supply-chain analysis.Pass
  • Known CVEs could not be checked: the version this server declares is not published in its registry.Unverified
  • Declares code that runs automatically (postinstall) and that we could not recognise. It may be perfectly ordinary, but we have not established what it does. View diagnostics → Partial
  • Dependency health could not be checked: the version this server declares is not published in its registry.Unverified
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to WireCatLabs/max-cli). View diagnostics → Pass
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 0 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability0
  • Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: our sandbox could not run this package, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake.Unverified

Unverified: 5 categories

Categories scored 0 because our sandbox could not run this package, so we have no schema for these checks 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 we can run it. How we score packages →

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.

  • 5 Nov 26 −11
    • Known CVEs: pass → unverified ▼ security
    • Tool safety: Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. security
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • Dependency health: 0.89 → unverified ▼ functional
    • Capabilities: Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet. functional
    • Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. functional
    • Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
    • Package version: 0.98.0 → 0.100.0 functional
    • Package version: 0.98.0 → 0.99.0 functional
  • 2 Nov 26 0
    • Stability: Stability not yet verified: our sandbox could not run this package, so we have no schema to compare. security
    • Tool safety: Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan. security
    • Schema quality: Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess. functional
    • Capabilities: Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake. functional
    • Tool coverage: Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess. functional
    • Package version: 0.95.0 → 0.98.0 functional
    • Package version: 0.95.0 → 0.97.0 functional
    • Package version: 0.95.0 → 0.96.0 functional
  • 1 Nov 26 0
    • Known CVEs: pass → unverified ▼ security
    • Tool safety: Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. security
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • Dependency health: 0.88 → unverified ▼ functional
    • Capabilities: Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet. functional
    • Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. functional
    • Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
    • Package version: 0.93.0 → 0.95.0 functional
    • Package version: 0.93.0 → 0.94.0 functional
  • 31 Oct 26 0
    • Known CVEs: pass → unverified ▼ security
    • Dependency health: 0.88 → unverified ▼ functional
    • Package version: 0.87.0 → 0.93.0 functional
    • Package version: 0.87.0 → 0.92.0 functional
    • Package version: 0.87.0 → 0.91.0 functional
    • Package version: 0.87.0 → 0.90.0 functional
  • 30 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
    • Stability: Stability not yet verified: our sandbox could not run this package, so we have no schema to compare. security
    • Tool safety: Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan. security
    • Schema quality: Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess. functional
    • Capabilities: Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake. functional
    • Tool coverage: Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess. functional
    • Package version: 0.85.0 → 0.87.0 functional
    • Package version: 0.85.0 → 0.86.0 functional
  • 29 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
    • Tool safety: Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. security
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • Capabilities: Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet. functional
    • Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. functional
    • Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
    • Package version: 0.84.0 → 0.85.0 functional
  • 28 Oct 26 0
    • Known CVEs: partial → pass ▲ security
    • Dependency health: partial → 0.88 functional
    • Package version: 0.83.0 → 0.84.0 functional
  • 27 Oct 26 48

    First indexed and scored.

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 5 Nov 2026 · Analysed npm/@wirecat/max-cli@0.100.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 WireCatLabs/max-cli
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/WireCatLabs/max-cli/.github/workflows/release.yml@refs/heads/main
Rekor log index 3692480115
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:71d7f151e2aecb3929c8968febddd1224a14c269b7440648089a8b2ac9e260315251242b660f2e7162f170cdb9c834b73ced65b0c140c968f4115e5bd

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
postinstall unreviewed node install/postinstall.mjs

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

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.

Install

How do I install the WireCat MAX MCP server?

WireCat MAX runs locally as an npm package, launched with npx -y @wirecat/max-cli. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @wirecat/max-cli

# add to Claude Code
claude mcp add dev-wirecat-max-cli -- npx -y @wirecat/max-cli
Common questions

What is the WireCat MAX MCP server?

WireCat MAX is an MCP server listed in the public MCP registry as dev.wirecat/max-cli. Your MAX account and bots for agents: read, search, send messages. Sign in with the max CLI first. This page covers its npm package (@wirecat/max-cli).

Is the WireCat MAX MCP server safe to use?

WireCat MAX scores 37 out of 100 on VerifyMCP. 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.

Is the WireCat MAX MCP server still maintained?

WireCat MAX is still listed as active in the MCP registry. We last reached this channel on 5 November 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 WireCat MAX MCP server under?

WireCat MAX declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.