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.

Agent Domains

NPM · @CLIZE/DOMAINS

Domains your AI agent can buy, point and monitor, with four-layer health checks and alerts.

Available components

npm · @clize/domains 35
0 this week 35 Trust /100

Last scanned (12 hours ago)

Scores higher than 12% of npm servers

Category Cloud Infrastructure

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 Security90
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, reached via @clize/clize > zod. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 30 of 121 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency39
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 →

What we tested

Checks we ran (9)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure

Checks we could not complete (5)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: our sandbox could not run this package, so we have no schema to compare.
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan.
  • Capabilities in Capabilities (scores 0 for this)Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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.

  • 24 Oct 26 −3
    • CVE-2023-54404 affects this package: high ▼ security
    • Known CVEs: pass → fail ▼ security
  • 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
  • 25 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
  • 4 Sept 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
  • 3 Sept 26 0
    • Known CVEs: 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
    • Dependency health: unverified → 0.89 ▲ functional
    • 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.35.2 → 0.35.5 functional
    • Package version: 0.35.2 → 0.35.4 functional
    • Package version: 0.35.2 → 0.35.3 functional
  • 2 Sept 26 0
    • Known CVEs: 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
    • Dependency health: unverified → 0.89 ▲ functional
    • 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.32.0 → 0.35.2 functional
    • Package version: 0.32.0 → 0.35.1 functional
    • Package version: 0.32.0 → 0.35.0 functional
    • Package version: 0.32.0 → 0.33.0 functional
  • 1 Sept 26 0
    • Known CVEs: unverified → partial ▲ security
    • Known CVEs: 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
    • Dependency health: unverified → partial ▲ functional
    • Dependency health: unverified → 0.89 ▲ functional
    • 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.29.1 → 0.32.0 functional
    • Package version: 0.29.1 → 0.31.1 functional
  • 31 Aug 26 0
    • Known CVEs: pass → unverified ▼ security
    • Malware scan: unverified → pass ▲ 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.26.1 → 0.29.1 functional
    • Package version: 0.26.1 → 0.27.0 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 5 Nov 2026 · Analysed npm/@clize/domains@0.35.5

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 →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 121 packages
Packages resolved 121
Stale 30
Tree resolution Complete

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. Our sandbox could not run this package, so no tool list has been captured. That is a gap on our side, not a finding about the package.

Install

How do I install the Agent Domains MCP server?

Agent Domains runs locally as an npm package, launched with npx -y @clize/domains --profile domains. The registry lists launch arguments for this package that we cannot show safely, so they are left out. Check the registry entry for what the server needs. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

npm · @clize/domains

# add to Claude Code
claude mcp add ai-clize-domains -- npx -y @clize/domains --profile domains

The registry lists launch arguments for this package that we cannot show safely, so they are left out. Check the registry entry for what the server needs.

Common questions

What is the Agent Domains MCP server?

Agent Domains is an MCP server listed in the public MCP registry as ai.clize/domains. Domains your AI agent can buy, point and monitor, with four-layer health checks and alerts. This page covers its npm package (@clize/domains).

Is the Agent Domains MCP server safe to use?

Agent Domains scores 35 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. 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 Agent Domains MCP server still maintained?

Agent Domains 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 Agent Domains MCP server under?

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

What did VerifyMCP test on the Agent Domains MCP server?

VerifyMCP ran 9 checks on Agent Domains, covering Malware scan, Known CVEs, Install scripts, Dependency health and 5 more. 5 items could not be completed, a gap on our side rather than a finding about Agent Domains: Schema quality, Stability, Tool coverage, Tool safety and 1 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.