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 Inbox

NPM · @CLIZE/INBOX · SCANNED SEP 20

A real email inbox for AI agents: human-approved sends, untrusted-by-default inbound.

Available components

npm · @clize/inbox 39
0 this week 39 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 Security99
  • 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
  • 31 of 124 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability0
  • Schema quality not yet verified: our sandbox run of this package did not complete, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: our sandbox run of this package did not complete, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: our sandbox run of this package did not complete, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: our sandbox run of this package did not complete, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: our sandbox run of this package did not complete, 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 Agent Inbox MCP server?

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

npm · @clize/inbox

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

  • 4 Sept 26 0
    • Stability: Stability not yet verified: our sandbox run of this package did not complete, so we have no schema to compare. security
    • Tool safety: Tool safety not yet verified: our sandbox run of this package did not complete, so we have no tool text to scan. security
    • Schema quality: Schema quality not yet verified: our sandbox run of this package did not complete, so we have no schema to assess. functional
    • Capabilities: Protocol version not yet verified: our sandbox run of this package did not complete, so we never saw its MCP handshake. functional
    • Tool coverage: Tool coverage not yet verified: our sandbox run of this package did not complete, so we have no tool definitions to assess. functional
  • 3 Sept 26 +11
    • Known CVEs: unverified → pass ▲ security
    • Stability: Stability not yet verified: our sandbox run of this package did not complete, so we have no schema to compare. security
    • Tool safety: Tool safety not yet verified: our sandbox run of this package did not complete, so we have no tool text to scan. security
    • Dependency health: unverified → 0.89 ▲ functional
    • Schema quality: Schema quality not yet verified: our sandbox run of this package did not complete, so we have no schema to assess. functional
    • Capabilities: Protocol version not yet verified: our sandbox run of this package did not complete, so we never saw its MCP handshake. functional
    • Tool coverage: Tool coverage not yet verified: our sandbox run of this package did not complete, 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 run of this package did not complete, so we have no schema to compare. security
    • Tool safety: Tool safety not yet verified: our sandbox run of this package did not complete, so we have no tool text to scan. security
    • Dependency health: unverified → 0.89 ▲ functional
    • Schema quality: Schema quality not yet verified: our sandbox run of this package did not complete, so we have no schema to assess. functional
    • Capabilities: Protocol version not yet verified: our sandbox run of this package did not complete, so we never saw its MCP handshake. functional
    • Tool coverage: Tool coverage not yet verified: our sandbox run of this package did not complete, 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 run of this package did not complete, so we have no schema to compare. security
    • Tool safety: Tool safety not yet verified: our sandbox run of this package did not complete, 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 run of this package did not complete, so we have no schema to assess. functional
    • Capabilities: Protocol version not yet verified: our sandbox run of this package did not complete, so we never saw its MCP handshake. functional
    • Tool coverage: Tool coverage not yet verified: our sandbox run of this package did not complete, 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 +4
    • 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
  • 30 Aug 26 24

    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 20 Sept 2026 · Analysed npm/@clize/inbox@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 →

Dependencies 124 packages
Packages resolved 124
Stale 31
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. The most recent sandbox run could not capture a tool list from this package.

Common questions

What is the Agent Inbox MCP server?

Agent Inbox is an MCP server listed in the public MCP registry as ai.clize/inbox. A real email inbox for AI agents: human-approved sends, untrusted-by-default inbound. This page covers its npm package (@clize/inbox).

Is the Agent Inbox MCP server safe to use?

Agent Inbox scores 39 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. 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 Inbox MCP server still maintained?

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

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