# addy.io (pypi · addy-mcp)

Manage addy.io email aliases, recipients, domains, rules and blocklist.

- Trust score: 79/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-16

## Components

- mcpb · `addy-mcp-0.1.2.mcpb`: 13/100, [markdown](https://verifymcp.io/servers/former-stranger-addy-mcp/addy-mcp.md), [page](https://verifymcp.io/servers/former-stranger-addy-mcp/addy-mcp)
- pypi · `addy-mcp`: 79/100 (this document), [markdown](https://verifymcp.io/servers/former-stranger-addy-mcp/addy-mcp-2.md), [page](https://verifymcp.io/servers/former-stranger-addy-mcp/addy-mcp-2)

## Channel facts

- Registry: `pypi`
- Package: `addy-mcp`
- Version: `0.1.2`
- 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-16.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - 1 of 31 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to Former-Stranger/addy-mcp).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 2 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 3711 tokens (~59/item across 62 items; 62 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**: 95/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 83% of tool parameters carry a description.
  - Structured output schemas are declared (2% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 9 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 63 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 addy.io MCP server?

addy.io runs locally as a PyPI package, launched with uvx addy-mcp. 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 former-stranger-addy-mcp -- uvx addy-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "former-stranger-addy-mcp": {
      "command": "uvx",
      "args": [
        "addy-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "former-stranger-addy-mcp": {
      "command": "uvx",
      "args": [
        "addy-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add former-stranger-addy-mcp -- uvx addy-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "former-stranger-addy-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "addy-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add former-stranger-addy-mcp --command uvx --arg addy-mcp
```

### Hermes

```yaml
mcp_servers:
  former-stranger-addy-mcp:
    command: "uvx"
    args: ["addy-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "former-stranger-addy-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "addy-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add former-stranger-addy-mcp -t stdio -c uvx -a addy-mcp
```

### Other

```json
{
  "mcpServers": {
    "former-stranger-addy-mcp": {
      "command": "uvx",
      "args": [
        "addy-mcp"
      ]
    }
  }
}
```

## 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-14 (score 79, +45)

- [security improvement] Injection markers: unverified → pass
- [security improvement] Malware scan: unverified → pass
- [security] First check of Judged manipulation: pass
- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Schema quality: fail
- [functional] First check of Tool coverage: 83
- [functional] First check of Destructive annotations: 100
- [functional] First check of Tool coverage: 2
- [functional] First check of Schema quality: pass
- [functional] First check of Schema quality: good
- [functional] Package version: 0.1.0 → 0.1.2
- [functional] Package version: 0.1.0 → 0.1.1

### 2026-10-13 (score 34)

First indexed and scored.

## MCP tools (62)

### `get_account_details` (~32 tokens)

Get account details: username, plan/subscription, bandwidth used, default alias domain/format, limits, etc.

### `get_api_token_details` (~27 tokens)

Get the name, creation date and expiry of the API token this server is using.

### `get_account_notifications` (~20 tokens)

Get account notifications/announcements from addy.io.

### `get_domain_options` (~27 tokens)

Get the domains available for creating aliases, plus the account's default alias domain and format.

### `get_app_version` (~25 tokens)

Get the addy.io app version (only available on self-hosted instances).

### `list_aliases` (~212 tokens)

List or search aliases. Results are paginated; the response includes `meta` with totals and page counts.

Input parameters:

- `active`: Only active (true) or inactive (false) aliases
- `deleted`: 'with' to include deleted aliases, 'only' for just deleted ones. Default excludes them.
- `descending` (boolean): Sort descending
- `domain_id`: Only aliases on this custom domain id
- `include`: Also return each alias's recipients or labels (the API allows only one per request)
- `label_id`: Only aliases with this label id
- `page`: Page number (1-based)
- `page_size`: Results per page (1-100)
- `pinned`: Only pinned (true) or unpinned (false) aliases
- `recipient_id`: Only aliases forwarding to this recipient id
- `search`: Search alias email addresses and descriptions
- `sort`: Field to sort by
- `username_id`: Only aliases on this username id

### `get_alias` (~37 tokens)

Get a single alias, including its recipients, labels and statistics.

Input parameters:

- `alias_id` (string, required): The id (UUID) of the item

### `create_alias` (~130 tokens)

Create a new alias. Use get_domain_options to see which domains are available.

Input parameters:

- `description`: What the alias is for, e.g. 'Amazon'
- `domain` (string, required): Domain for the alias, e.g. 'anonaddy.me' or a custom domain/username domain
- `format`: Alias format. 'custom' requires local_part and a custom domain or username domain.
- `label_ids`: Labels to attach
- `local_part`: The part before the @ (only with format='custom')
- `recipient_ids`: Recipients to forward to (default recipient if omitted)

### `update_alias` (~80 tokens)

Update an alias's description, from name, or labels. Only the fields you pass are changed.

Input parameters:

- `alias_id` (string, required): The id (UUID) of the item
- `description`: New description
- `from_name`: Display name used when replying/sending from the alias
- `label_ids`: Replace the alias's labels with these

### `delete_alias` (~41 tokens)

Delete an alias. It stops receiving mail but can be brought back with restore_alias.

Input parameters:

- `alias_id` (string, required): The id (UUID) of the item

### `restore_alias` (~29 tokens)

Restore a deleted alias.

Input parameters:

- `alias_id` (string, required): The id (UUID) of the item

### `forget_alias` (~44 tokens)

PERMANENTLY forget an alias: it is disassociated from the account and cannot be restored.

Input parameters:

- `alias_id` (string, required): The id (UUID) of the item

### `set_alias_option` (~104 tokens)

Turn an alias option on or off (activate/deactivate, pin/unpin, limit reply/send to attached recipients).

Input parameters:

- `alias_id` (string, required): The id (UUID) of the item
- `enabled` (boolean, required)
- `option` (string, required): 'active': whether the alias forwards mail (inactive aliases silently discard it). 'pinned': show first in lists. 'attached_recipients_only': only recipients attached to this alias may reply/send from…

### `set_alias_recipients` (~97 tokens)

Replace the set of recipients an alias forwards to.

Input parameters:

- `alias_id` (string, required): The id (UUID) of the item
- `family_member_ids`: Duo/Family plan member user ids to also deliver to
- `family_reply_send_ids`: Subset of family_member_ids allowed to reply/send from the alias
- `recipient_ids` (array, required): Recipients the alias should forward to (empty list = default recipient)

### `set_alias_labels` (~51 tokens)

Replace the labels attached to an alias.

Input parameters:

- `alias_id` (string, required): The id (UUID) of the item
- `label_ids` (array, required): Labels the alias should have (empty list removes all)

### `bulk_alias_action` (~62 tokens)

Apply one action to up to 25 aliases at once (or fetch them with action='get').

Input parameters:

- `action` (string, required): What to do to every alias. 'forget' is permanent.
- `alias_ids` (array, required): Alias ids (max 25)

### `bulk_set_alias_recipients` (~89 tokens)

Replace the recipients of up to 25 aliases at once.

Input parameters:

- `alias_ids` (array, required): Alias ids (max 25)
- `family_member_ids`: Duo/Family plan member user ids to also deliver to
- `family_reply_send_ids`: Subset of family_member_ids allowed to reply/send
- `recipient_ids` (array, required): Recipients every alias should forward to

### `bulk_set_alias_labels` (~49 tokens)

Replace the labels of up to 25 aliases at once.

Input parameters:

- `alias_ids` (array, required): Alias ids (max 25)
- `label_ids` (array, required): Labels every alias should have

### `list_recipients` (~55 tokens)

List the account's recipients (the real mailboxes aliases forward to).

Input parameters:

- `include_alias_count` (boolean): Include how many aliases use each recipient
- `verified`: Only verified (true) or unverified (false)

### `get_recipient` (~49 tokens)

Get a single recipient and its settings.

Input parameters:

- `include_alias_count` (boolean): Include how many aliases use this recipient
- `recipient_id` (string, required): The id (UUID) of the item

### `create_recipient` (~44 tokens)

Add a new recipient. addy.io emails it a verification link; it can't be used until verified.

Input parameters:

- `email` (string, required): The real email address to forward to

### `update_recipient` (~38 tokens)

Set a recipient's description.

Input parameters:

- `description` (string, required)
- `recipient_id` (string, required): The id (UUID) of the item

### `delete_recipient` (~41 tokens)

Delete a recipient. Aliases that used it fall back to the default recipient.

Input parameters:

- `recipient_id` (string, required): The id (UUID) of the item

### `resend_recipient_verification` (~38 tokens)

Resend the verification email for an unverified recipient.

Input parameters:

- `recipient_id` (string, required): The id (UUID) of the item

### `add_recipient_public_key` (~61 tokens)

Add a public GPG key to a recipient so forwarded mail can be encrypted.

Input parameters:

- `key_data` (string, required): ASCII-armored public GPG/OpenPGP key
- `recipient_id` (string, required): The id (UUID) of the item

### `remove_recipient_public_key` (~44 tokens)

Remove a recipient's public GPG key (this also turns off encryption for it).

Input parameters:

- `recipient_id` (string, required): The id (UUID) of the item

### `set_recipient_option` (~131 tokens)

Turn a recipient option on or off.

Input parameters:

- `enabled` (boolean, required)
- `option` (string, required): 'active': whether mail is forwarded to it. 'can_reply_send': whether it may reply/send from aliases. 'encryption': encrypt forwarded mail with its GPG key. 'inline_encryption': use PGP/Inline instead…
- `recipient_id` (string, required): The id (UUID) of the item

### `list_usernames` (~33 tokens)

List the account's usernames (each gives a subdomain like name.anonaddy.com for on-the-fly aliases).

### `get_username` (~32 tokens)

Get a single username and its settings.

Input parameters:

- `username_id` (string, required): The id (UUID) of the item

### `create_username` (~28 tokens)

Create an additional username (counts against the plan's username limit).

Input parameters:

- `username` (string, required)

### `update_username` (~74 tokens)

Update a username's description, from name, or auto-create regex.

Input parameters:

- `auto_create_regex`: Regex limiting which on-the-fly aliases may be auto-created
- `description`
- `from_name`: Display name for replies/sends
- `username_id` (string, required): The id (UUID) of the item

### `delete_username` (~33 tokens)

Delete a username. Its aliases stop working.

Input parameters:

- `username_id` (string, required): The id (UUID) of the item

### `set_username_default_recipient` (~57 tokens)

Set (or clear) the default recipient for aliases on a username.

Input parameters:

- `recipient_id` (required): Recipient id, or null to use the account default
- `username_id` (string, required): The id (UUID) of the item

### `set_username_option` (~86 tokens)

Turn a username option on or off.

Input parameters:

- `enabled` (boolean, required)
- `option` (string, required): 'active': whether its aliases forward mail. 'catch_all': auto-create aliases for any address at the username. 'can_login': whether the username can be used to log in to the account.
- `username_id` (string, required): The id (UUID) of the item

### `list_domains` (~17 tokens)

List the custom domains connected to the account.

### `get_domain` (~36 tokens)

Get a single custom domain and its settings/verification status.

Input parameters:

- `domain_id` (string, required): The id (UUID) of the item

### `create_domain` (~46 tokens)

Add a custom domain. Its DNS must already have the TXT verification record addy.io shows in its dashboard.

Input parameters:

- `domain` (string, required): Domain name, e.g. 'example.com'

### `update_domain` (~75 tokens)

Update a custom domain's description, from name, or auto-create regex.

Input parameters:

- `auto_create_regex`: Regex limiting which on-the-fly aliases may be auto-created
- `description`
- `domain_id` (string, required): The id (UUID) of the item
- `from_name`: Display name for replies/sends

### `delete_domain` (~34 tokens)

Delete a custom domain. Its aliases stop working.

Input parameters:

- `domain_id` (string, required): The id (UUID) of the item

### `set_domain_default_recipient` (~58 tokens)

Set (or clear) the default recipient for aliases on a custom domain.

Input parameters:

- `domain_id` (string, required): The id (UUID) of the item
- `recipient_id` (required): Recipient id, or null to use the account default

### `check_domain_sending_records` (~53 tokens)

Check a custom domain's DNS records (SPF, DKIM, DMARC, ...) for sending/replying from aliases.

Input parameters:

- `domain_id` (string, required): The id (UUID) of the item

### `set_domain_option` (~92 tokens)

Turn a custom domain option on or off.

Input parameters:

- `domain_id` (string, required): The id (UUID) of the item
- `enabled` (boolean, required)
- `option` (string, required): 'active': whether its aliases forward mail. 'catch_all': auto-create aliases for any address at the domain. 'shared_with_family': share with Family plan members (turning off starts a 14-day grace per…

### `list_labels` (~25 tokens)

List the labels used to organise aliases.

Input parameters:

- `search`: Search labels by name

### `get_label` (~29 tokens)

Get a single label.

Input parameters:

- `label_id` (string, required): The id (UUID) of the item

### `create_label` (~97 tokens)

Create a label for organising aliases.

Input parameters:

- `colour` (string, required): #06b6d4 cyan, #22c55e green, #eab308 yellow, #f97316 orange, #ef4444 red, #8b5cf6 violet, #64748b slate, #ec4899 pink, #14b8a6 teal, #3b82f6 blue
- `name` (string, required)

### `update_label` (~110 tokens)

Rename a label or change its colour.

Input parameters:

- `colour`: #06b6d4 cyan, #22c55e green, #eab308 yellow, #f97316 orange, #ef4444 red, #8b5cf6 violet, #64748b slate, #ec4899 pink, #14b8a6 teal, #3b82f6 blue
- `label_id` (string, required): The id (UUID) of the item
- `name`

### `delete_label` (~37 tokens)

Delete a label (aliases are kept, just unlabelled).

Input parameters:

- `label_id` (string, required): The id (UUID) of the item

### `list_rules` (~19 tokens)

List all rules, in the order they are applied.

### `get_rule` (~34 tokens)

Get a single rule with its conditions and actions.

Input parameters:

- `rule_id` (string, required): The id (UUID) of the item

### `create_rule` (~154 tokens)

Create a rule that runs actions on emails matching conditions.

Example: block newsletters to a specific alias -> conditions=[{type:'alias', match:'is exactly',
values:['shop@anonaddy.me']}, {type:'header', match:'exists', values:['List-Unsubscribe']}],
actions=[{type:'block'}].

Input parameters:

- `actions` (array, required)
- `conditions` (array, required)
- `forwards` (boolean): Apply to mail forwarded to recipients
- `name` (string, required)
- `operator` (string): Whether all (AND) or any (OR) conditions must match
- `replies` (boolean): Apply to replies sent from aliases
- `sends` (boolean): Apply to new emails sent from aliases

### `update_rule` (~87 tokens)

Update a rule. Only the fields you pass change; the rest are kept from the current rule.

Input parameters:

- `actions`: Replaces all actions
- `conditions`: Replaces all conditions
- `forwards`
- `name`
- `operator`
- `replies`
- `rule_id` (string, required): The id (UUID) of the item
- `sends`

### `delete_rule` (~28 tokens)

Delete a rule.

Input parameters:

- `rule_id` (string, required): The id (UUID) of the item

### `reorder_rules` (~32 tokens)

Set the order rules are applied in.

Input parameters:

- `rule_ids` (array, required): All rule ids, in the new order

### `set_rule_active` (~38 tokens)

Activate or deactivate a rule.

Input parameters:

- `active` (boolean, required)
- `rule_id` (string, required): The id (UUID) of the item

### `list_blocklist` (~74 tokens)

List blocked senders/domains, with how many emails each has blocked.

Input parameters:

- `descending` (boolean)
- `page`: Page number (1-based)
- `page_size`: Results per page (1-100)
- `search`: Search by email or domain
- `sort`
- `type`

### `add_to_blocklist` (~54 tokens)

Block mail from sender email addresses or whole domains, across all aliases.

Input parameters:

- `type` (string, required): Whether values are email addresses or domains
- `values` (array, required): Addresses or domains to block (max 50)

### `remove_from_blocklist` (~39 tokens)

Unblock blocklist entries by id (see list_blocklist).

Input parameters:

- `entry_ids` (array, required): Blocklist entry ids (max 100)

### `list_failed_deliveries` (~74 tokens)

List emails that addy.io failed to deliver (or quarantined).

Input parameters:

- `email_type`: Filter by type; 'inbound_quarantined' shows mail quarantined by rules or spam checks
- `page`: Page number (1-based)
- `page_size`: Results per page (1-100)

### `get_failed_delivery` (~42 tokens)

Get details of a failed delivery (sender, alias, bounce reason, ...).

Input parameters:

- `failed_delivery_id` (string, required): The id (UUID) of the item

### `download_failed_delivery` (~47 tokens)

Download the raw email (.eml source) of a failed delivery, if addy.io stored it.

Input parameters:

- `failed_delivery_id` (string, required): The id (UUID) of the item

Output parameters:

- `result` (string)

### `resend_failed_delivery` (~57 tokens)

Retry delivering a failed or quarantined email.

Input parameters:

- `failed_delivery_id` (string, required): The id (UUID) of the item
- `recipient_ids`: Recipients to resend to (max 10); defaults to the alias's recipients

### `delete_failed_deliveries` (~38 tokens)

Delete failed delivery records (and any stored email).

Input parameters:

- `failed_delivery_ids` (array, required): Ids to delete (max 100)

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/former-stranger-addy-mcp/addy-mcp-2#diagnostics

## Score history

- 2026-10-16: 79
- 2026-10-15: 79
- 2026-10-14: 79
- 2026-10-13: 34

## Common questions

### What is the addy.io MCP server?

addy.io is an MCP server listed in the public MCP registry as io.github.Former-Stranger/addy-mcp. Manage addy.io email aliases, recipients, domains, rules and blocklist. This page covers its PyPI package (addy-mcp).

### Is the addy.io MCP server safe to use?

addy.io scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 16 October 2026. 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 addy.io MCP server expose?

addy.io exposes 62 tools: get_account_details, get_api_token_details, get_account_notifications, get_domain_options, get_app_version, and 57 more. Their descriptions and schemas cost roughly 3,526 tokens of context every time the server is loaded.

### Is the addy.io MCP server still maintained?

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

addy.io 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

- PyPI project: https://pypi.org/project/addy-mcp/
- Socket report: https://socket.dev/pypi/package/addy-mcp
- Repository: https://github.com/Former-Stranger/addy-mcp
- Changelog RSS feed: https://verifymcp.io/servers/former-stranger-addy-mcp/addy-mcp-2.xml
- Changelog JSON feed: https://verifymcp.io/servers/former-stranger-addy-mcp/addy-mcp-2.json
- HTML version of this page: https://verifymcp.io/servers/former-stranger-addy-mcp/addy-mcp-2