# GhostPaw Email (npm · @ghostpaw/email)

Email tools with a local SQLite cache and IMAP/SMTP account configuration.

- Trust score: 48/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-24

## Components

- npm · `@ghostpaw/email`: 48/100 (this document), [markdown](https://verifymcp.io/servers/ghostpawjs-email/ghostpaw-email.md), [page](https://verifymcp.io/servers/ghostpawjs-email/ghostpaw-email)

## Channel facts

- Registry: `npm`
- Package: `@ghostpaw/email`
- Version: `0.4.1`
- 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-10-24.

- **Supply Chain Security**: 13/100
  - Malware scan not yet available for this package.
  - Known CVEs could not be checked: the version this server declares is not published in its registry.
  - No install/post-install scripts declared.
  - Dependency health could not be checked: the version this server declares is not published in its registry.
- **Provenance & Transparency**: 71/100
  - Repository check failed: the declared repository URL redirects; it must resolve directly.
  - Cryptographically verified build provenance (signed, bound to GhostPawJS/email).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 847 tokens (~169/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - 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**: 97/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 90% 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (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 GhostPaw Email MCP server?

GhostPaw Email runs locally as an npm package, launched with npx -y @ghostpaw/email. 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 ghostpawjs-email -- npx -y @ghostpaw/email
```

### Cursor

```json
{
  "mcpServers": {
    "ghostpawjs-email": {
      "command": "npx",
      "args": [
        "-y",
        "@ghostpaw/email"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ghostpawjs-email": {
      "command": "npx",
      "args": [
        "-y",
        "@ghostpaw/email"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add ghostpawjs-email -- npx -y @ghostpaw/email
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ghostpawjs-email": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@ghostpaw/email"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ghostpawjs-email --command npx --arg -y --arg @ghostpaw/email
```

### Hermes

```yaml
mcp_servers:
  ghostpawjs-email:
    command: "npx"
    args: ["-y", "@ghostpaw/email"]
```

### Netclaw

```json
{
  "McpServers": {
    "ghostpawjs-email": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@ghostpaw/email"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add ghostpawjs-email -t stdio -c npx -a -y @ghostpaw/email
```

### Other

```json
{
  "mcpServers": {
    "ghostpawjs-email": {
      "command": "npx",
      "args": [
        "-y",
        "@ghostpaw/email"
      ]
    }
  }
}
```

## 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-10-24 (score 48)

First indexed and scored.

## MCP tools (5)

### `mail_read` (~200 tokens)

Read mailbox state: folder list, message queue, thread view, single message body, attachment metadata, or raw EML export.

Use when: Inspect folders, cached messages, threads, attachments or raw message content.
Not for: Use mail_search to find messages by query or mail_organize to change them.

Input parameters:

- `folder` (string): Folder path (required for queue/message/attachment/eml).
- `limit` (integer): Maximum messages to return (queue view).
- `partPath` (string): Part path for a specific attachment (optional for attachment view).
- `refresh` (boolean): Fetch live folder list from server before returning (folders/queue view).
- `threadId` (string): Thread ID (required for thread view).
- `uid` (integer): Message UID (required for message/attachment/eml).
- `unreadOnly` (boolean): Filter to unread messages only (queue view).
- `view` (string, required): What to read.

### `mail_search` (~175 tokens)

Search for messages locally via FTS or remotely via IMAP SEARCH. Returns matching message references.

Use when: Find messages by a local full-text query or a remote IMAP search.
Not for: Use mail_read when the folder and message UID are already known.

Input parameters:

- `before` (string): ISO date string — only messages before this date.
- `folder` (string): Restrict search to a specific folder.
- `hasAttachments` (boolean): Filter to messages with attachments.
- `limit` (integer): Maximum number of results.
- `mode` (string): local (default) or remote IMAP SEARCH.
- `query` (string, required): Free-text search query or FTS5 expression.
- `since` (string): ISO date string — only messages after this date.
- `unreadOnly` (boolean): Filter to unread messages.

### `mail_compose` (~126 tokens)

Compose and send email: send new message, reply, forward, save/update/send a draft.

Use when: Send, reply, forward, or save and manage a draft after its content is agreed.
Not for: Use mail_read to inspect an existing message without sending or saving content.

Input parameters:

- `action` (string, required)
- `folder` (string): Source folder (required for reply/forward).
- `input` (object): ComposeInput / ReplyInput / ForwardInput payload.
- `uid` (integer): Source message UID (required for reply/forward/update_draft/send_draft).

### `mail_organize` (~176 tokens)

Organize messages: mark read/unread/starred/answered, copy, move, archive, trash, junk, label, or manage folders.

Use when: Change message flags, labels, destinations or folder organization.
Not for: Use mail_read or mail_search when only inspection is requested.

Input parameters:

- `action` (string, required)
- `destination` (string): Destination folder (required for copy/move).
- `folder` (string): Source folder (required for message actions).
- `labels` (array): Labels to set/add/remove.
- `newPath` (string): New folder path (required for rename_folder).
- `oldPath` (string): Old folder path (required for rename_folder).
- `path` (string): Folder path (required for folder actions).
- `uids` (array): Message UIDs to act on.

### `mail_sync` (~112 tokens)

Manage the IMAP connection lifecycle and sync local state: connect, disconnect, reconnect, sync folders, or refresh the folder list.

Use when: Connect, disconnect, reconnect, refresh folders or synchronize the cache.
Not for: Use mail_read for cached content or the network watch stream for continuous monitoring.

Input parameters:

- `action` (string, required)
- `bodies` (string): Body fetch strategy for sync (default: missing).
- `folders` (array): Folders to sync or watch (optional — defaults to all subscribed folders).

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/ghostpawjs-email/ghostpaw-email#diagnostics

## Score history

- 2026-10-24: 48

## Common questions

### What is the GhostPaw Email MCP server?

GhostPaw Email is an MCP server listed in the public MCP registry as io.github.GhostPawJS/email. Email tools with a local SQLite cache and IMAP/SMTP account configuration. This page covers its npm package (@ghostpaw/email).

### Is the GhostPaw Email MCP server safe to use?

GhostPaw Email scores 48 out of 100 on VerifyMCP. 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 GhostPaw Email MCP server expose?

GhostPaw Email exposes 5 tools: mail_read, mail_search, mail_compose, mail_organize, mail_sync. Their descriptions and schemas cost roughly 789 tokens of context every time the server is loaded.

### Is the GhostPaw Email MCP server still maintained?

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

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

## Links

- npm package: https://www.npmjs.com/package/@ghostpaw/email
- Socket report: https://socket.dev/npm/package/@ghostpaw/email
- Website: https://email.ghostpaw.dev/
- Changelog RSS feed: https://verifymcp.io/servers/ghostpawjs-email/ghostpaw-email.xml
- Changelog JSON feed: https://verifymcp.io/servers/ghostpawjs-email/ghostpaw-email.json
- HTML version of this page: https://verifymcp.io/servers/ghostpawjs-email/ghostpaw-email