# allinbox (npm · allinbox)

Search all your email accounts in one query. Read-only IMAP, cannot send; optional drafts.

- Trust score: 78/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- npm · `allinbox`: 78/100 (this document), [markdown](https://verifymcp.io/servers/tomasbenavidez-allinbox/allinbox.md), [page](https://verifymcp.io/servers/tomasbenavidez-allinbox/allinbox)

## Channel facts

- Registry: `npm`
- Package: `allinbox`
- Version: `0.3.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Supply Chain Security**: 99/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 36 of 148 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to tomasbenavidez/allinbox).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 8 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 389 tokens (~97/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 79/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 38% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the allinbox MCP server?

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

### Claude

```bash
claude mcp add tomasbenavidez-allinbox -- npx -y allinbox serve
```

### Cursor

```json
{
  "mcpServers": {
    "tomasbenavidez-allinbox": {
      "command": "npx",
      "args": [
        "-y",
        "allinbox",
        "serve"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "tomasbenavidez-allinbox": {
      "command": "npx",
      "args": [
        "-y",
        "allinbox",
        "serve"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add tomasbenavidez-allinbox -- npx -y allinbox serve
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "tomasbenavidez-allinbox": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "allinbox",
        "serve"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add tomasbenavidez-allinbox --command npx --arg -y --arg allinbox --arg serve
```

### Hermes

```yaml
mcp_servers:
  tomasbenavidez-allinbox:
    command: "npx"
    args: ["-y", "allinbox", "serve"]
```

### Netclaw

```json
{
  "McpServers": {
    "tomasbenavidez-allinbox": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "allinbox",
        "serve"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add tomasbenavidez-allinbox -t stdio -c npx -a -y allinbox serve
```

### Other

```json
{
  "mcpServers": {
    "tomasbenavidez-allinbox": {
      "command": "npx",
      "args": [
        "-y",
        "allinbox",
        "serve"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-13 (score 78)

First indexed and scored.

## MCP tools (4)

### `list_accounts` (~18 tokens)

List the email accounts allinbox can search.

### `search_all` (~105 tokens)

Search ALL email accounts in one call. Returns one line per message: id | date | from | subject. Duplicates across accounts (same Message-ID) are merged. Empty query = latest messages.

Input parameters:

- `accounts` (array): Restrict to these account ids. Default: all.
- `limit` (integer)
- `query` (string): Free text: words, sender name or address, subject.
- `since_days` (integer): Only messages newer than N days.

### `read_email` (~39 tokens)

Read one email by id. Quoted replies, signatures and HTML are stripped.

Input parameters:

- `id` (string, required)
- `max_chars` (integer)

### `read_thread` (~55 tokens)

Read the whole conversation an email belongs to, oldest first, each message cleaned. Cheaper than several read_email calls: the char budget is split across messages.

Input parameters:

- `id` (string, required)
- `max_chars` (integer)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/tomasbenavidez-allinbox/allinbox#diagnostics

## Score history

- 2026-11-21: 78
- 2026-11-20: 78
- 2026-11-19: 78
- 2026-11-18: 78
- 2026-11-17: 78
- 2026-11-16: 78
- 2026-11-15: 78
- 2026-11-14: 78
- 2026-11-13: 78

## Common questions

### What is the allinbox MCP server?

allinbox is an MCP server listed in the public MCP registry as io.github.tomasbenavidez/allinbox. Search all your email accounts in one query. Read-only IMAP, cannot send; optional drafts. This page covers its npm package (allinbox).

### Is the allinbox MCP server safe to use?

allinbox scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 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 allinbox MCP server expose?

allinbox exposes 4 tools: list_accounts, search_all, read_email, read_thread. Their descriptions and schemas cost roughly 217 tokens of context every time the server is loaded.

### Is the allinbox MCP server still maintained?

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

allinbox 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 allinbox MCP server?

VerifyMCP ran 15 checks on allinbox, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about allinbox: Stability. One category scores 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.

## Links

- npm package: https://www.npmjs.com/package/allinbox
- Socket report: https://socket.dev/npm/package/allinbox
- Repository: https://github.com/tomasbenavidez/allinbox
- Changelog RSS feed: https://verifymcp.io/servers/tomasbenavidez-allinbox/allinbox.xml
- Changelog JSON feed: https://verifymcp.io/servers/tomasbenavidez-allinbox/allinbox/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/tomasbenavidez-allinbox/allinbox.json
- HTML version of this page: https://verifymcp.io/servers/tomasbenavidez-allinbox/allinbox
