addy.io
PYPI · ADDY-MCP · 2 COMPONENTS
Manage addy.io email aliases, recipients, domains, rules and blocklist.
Available components
Last scanned (21 hours ago)
Scores higher than 81% of PyPI servers
Category Communication
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 31 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to Former-Stranger/addy-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 3711 tokens (~59/item across 62 items; 62 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 83% of tool parameters carry a description.Partial
- Structured output schemas are declared (2% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 9 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 63 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
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.
- 14 Oct 26 +45
- Injection markers: unverified → pass ▲ security
- 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). security
- MCP protocol: unverified → pass ▲ functional
- 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 functional
- 13 Oct 26 34
First indexed and scored.
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 16 Oct 2026 · Analysed pypi/addy-mcp@0.1.2
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | Former-Stranger/addy-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/Former-Stranger/addy-mcp/.github/workflows/release.yml@refs/tags/v0.1.2 |
| Rekor log index | 3247707593 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:b70bb054286ecfee44e9d547b539d236475516b94e5afae629ff57cf448f53c8 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 31 packages
| Packages resolved | 31 |
|---|---|
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
add_recipient_public_key ~61
Add a public GPG key to a recipient so forwarded mail can be encrypted.
| Name | Type | Req | Description |
|---|---|---|---|
| key_data | string | yes | ASCII-armored public GPG/OpenPGP key |
| recipient_id | string | yes | The id (UUID) of the item |
No output schema declared.
No examples provided.
add_to_blocklist ~54
Block mail from sender email addresses or whole domains, across all aliases.
| Name | Type | Req | Description |
|---|---|---|---|
| type | string | yes | Whether values are email addresses or domains |
| values | array | yes | Addresses or domains to block (max 50) |
No output schema declared.
No examples provided.
bulk_alias_action ~62
Apply one action to up to 25 aliases at once (or fetch them with action='get').
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | What to do to every alias. 'forget' is permanent. |
| alias_ids | array | yes | Alias ids (max 25) |
No output schema declared.
No examples provided.
bulk_set_alias_labels ~49
Replace the labels of up to 25 aliases at once.
| Name | Type | Req | Description |
|---|---|---|---|
| alias_ids | array | yes | Alias ids (max 25) |
| label_ids | array | yes | Labels every alias should have |
No output schema declared.
No examples provided.
bulk_set_alias_recipients ~89
Replace the recipients of up to 25 aliases at once.
| Name | Type | Req | Description |
|---|---|---|---|
| alias_ids | array | yes | 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 | yes | Recipients every alias should forward to |
No output schema declared.
No examples provided.
check_domain_sending_records ~53
Check a custom domain's DNS records (SPF, DKIM, DMARC, ...) for sending/replying from aliases.
| Name | Type | Req | Description |
|---|---|---|---|
| domain_id | string | yes | The id (UUID) of the item |
No output schema declared.
No examples provided.
create_alias ~130
Create a new alias. Use get_domain_options to see which domains are available.
| Name | Type | Req | Description |
|---|---|---|---|
| description | – | – | What the alias is for, e.g. 'Amazon' |
| domain | string | yes | 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) |
No output schema declared.
No examples provided.
create_domain ~46
Add a custom domain. Its DNS must already have the TXT verification record addy.io shows in its dashboard.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain name, e.g. 'example.com' |
No output schema declared.
No examples provided.
create_label ~97
Create a label for organising aliases.
| Name | Type | Req | Description |
|---|---|---|---|
| colour | string | yes | #06b6d4 cyan, #22c55e green, #eab308 yellow, #f97316 orange, #ef4444 red, #8b5cf6 violet, #64748b slate, #ec4899 pink, #14b8a6 teal, #3b82f6 blue |
| name | string | yes | – |
No output schema declared.
No examples provided.
create_recipient ~44
Add a new recipient. addy.io emails it a verification link; it can't be used until verified.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | The real email address to forward to |
No output schema declared.
No examples provided.
create_rule ~154
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'}].
| Name | Type | Req | Description |
|---|---|---|---|
| actions | array | yes | – |
| conditions | array | yes | – |
| forwards | boolean | – | Apply to mail forwarded to recipients |
| name | string | yes | – |
| 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 |
No output schema declared.
No examples provided.
create_username ~28
Create an additional username (counts against the plan's username limit).
| Name | Type | Req | Description |
|---|---|---|---|
| username | string | yes | – |
No output schema declared.
No examples provided.
delete_alias ~41
Delete an alias. It stops receiving mail but can be brought back with restore_alias.
| Name | Type | Req | Description |
|---|---|---|---|
| alias_id | string | yes | The id (UUID) of the item |
No output schema declared.
No examples provided.
delete_domain ~34
Delete a custom domain. Its aliases stop working.
| Name | Type | Req | Description |
|---|---|---|---|
| domain_id | string | yes | The id (UUID) of the item |
No output schema declared.
No examples provided.
delete_failed_deliveries ~38
Delete failed delivery records (and any stored email).
| Name | Type | Req | Description |
|---|---|---|---|
| failed_delivery_ids | array | yes | Ids to delete (max 100) |
No output schema declared.
No examples provided.
delete_label ~37
Delete a label (aliases are kept, just unlabelled).
| Name | Type | Req | Description |
|---|---|---|---|
| label_id | string | yes | The id (UUID) of the item |
No output schema declared.
No examples provided.
delete_recipient ~41
Delete a recipient. Aliases that used it fall back to the default recipient.
| Name | Type | Req | Description |
|---|---|---|---|
| recipient_id | string | yes | The id (UUID) of the item |
No output schema declared.
No examples provided.
delete_rule ~28
Delete a rule.
| Name | Type | Req | Description |
|---|---|---|---|
| rule_id | string | yes | The id (UUID) of the item |
No output schema declared.
No examples provided.
delete_username ~33
Delete a username. Its aliases stop working.
| Name | Type | Req | Description |
|---|---|---|---|
| username_id | string | yes | The id (UUID) of the item |
No output schema declared.
No examples provided.
download_failed_delivery ~47
Download the raw email (.eml source) of a failed delivery, if addy.io stored it.
| Name | Type | Req | Description |
|---|---|---|---|
| failed_delivery_id | string | yes | The id (UUID) of the item |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
forget_alias ~44
PERMANENTLY forget an alias: it is disassociated from the account and cannot be restored.
| Name | Type | Req | Description |
|---|---|---|---|
| alias_id | string | yes | The id (UUID) of the item |
No output schema declared.
No examples provided.
get_account_details ~32
Get account details: username, plan/subscription, bandwidth used, default alias domain/format, limits, etc.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_account_notifications ~20
Get account notifications/announcements from addy.io.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_alias ~37
Get a single alias, including its recipients, labels and statistics.
| Name | Type | Req | Description |
|---|---|---|---|
| alias_id | string | yes | The id (UUID) of the item |
No output schema declared.
No examples provided.
get_api_token_details ~27
Get the name, creation date and expiry of the API token this server is using.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_app_version ~25
Get the addy.io app version (only available on self-hosted instances).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_domain ~36
Get a single custom domain and its settings/verification status.
| Name | Type | Req | Description |
|---|---|---|---|
| domain_id | string | yes | The id (UUID) of the item |
No output schema declared.
No examples provided.
get_domain_options ~27
Get the domains available for creating aliases, plus the account's default alias domain and format.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_failed_delivery ~42
Get details of a failed delivery (sender, alias, bounce reason, ...).
| Name | Type | Req | Description |
|---|---|---|---|
| failed_delivery_id | string | yes | The id (UUID) of the item |
No output schema declared.
No examples provided.
get_label ~29
Get a single label.
| Name | Type | Req | Description |
|---|---|---|---|
| label_id | string | yes | The id (UUID) of the item |
No output schema declared.
No examples provided.
get_recipient ~49
Get a single recipient and its settings.
| Name | Type | Req | Description |
|---|---|---|---|
| include_alias_count | boolean | – | Include how many aliases use this recipient |
| recipient_id | string | yes | The id (UUID) of the item |
No output schema declared.
No examples provided.
get_rule ~34
Get a single rule with its conditions and actions.
| Name | Type | Req | Description |
|---|---|---|---|
| rule_id | string | yes | The id (UUID) of the item |
No output schema declared.
No examples provided.
get_username ~32
Get a single username and its settings.
| Name | Type | Req | Description |
|---|---|---|---|
| username_id | string | yes | The id (UUID) of the item |
No output schema declared.
No examples provided.
list_aliases ~212
List or search aliases. Results are paginated; the response includes `meta` with totals and page counts.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
list_blocklist ~74
List blocked senders/domains, with how many emails each has blocked.
| Name | Type | Req | Description |
|---|---|---|---|
| descending | boolean | – | – |
| page | – | – | Page number (1-based) |
| page_size | – | – | Results per page (1-100) |
| search | – | – | Search by email or domain |
| sort | – | – | – |
| type | – | – | – |
No output schema declared.
No examples provided.
list_domains ~17
List the custom domains connected to the account.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_failed_deliveries ~74
List emails that addy.io failed to deliver (or quarantined).
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
No output schema declared.
No examples provided.
list_labels ~25
List the labels used to organise aliases.
| Name | Type | Req | Description |
|---|---|---|---|
| search | – | – | Search labels by name |
No output schema declared.
No examples provided.
list_recipients ~55
List the account's recipients (the real mailboxes aliases forward to).
| Name | Type | Req | Description |
|---|---|---|---|
| include_alias_count | boolean | – | Include how many aliases use each recipient |
| verified | – | – | Only verified (true) or unverified (false) |
No output schema declared.
No examples provided.
list_rules ~19
List all rules, in the order they are applied.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_usernames ~33
List the account's usernames (each gives a subdomain like name.anonaddy.com for on-the-fly aliases).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
remove_from_blocklist ~39
Unblock blocklist entries by id (see list_blocklist).
| Name | Type | Req | Description |
|---|---|---|---|
| entry_ids | array | yes | Blocklist entry ids (max 100) |
No output schema declared.
No examples provided.
remove_recipient_public_key ~44
Remove a recipient's public GPG key (this also turns off encryption for it).
| Name | Type | Req | Description |
|---|---|---|---|
| recipient_id | string | yes | The id (UUID) of the item |
No output schema declared.
No examples provided.
reorder_rules ~32
Set the order rules are applied in.
| Name | Type | Req | Description |
|---|---|---|---|
| rule_ids | array | yes | All rule ids, in the new order |
No output schema declared.
No examples provided.
resend_failed_delivery ~57
Retry delivering a failed or quarantined email.
| Name | Type | Req | Description |
|---|---|---|---|
| failed_delivery_id | string | yes | The id (UUID) of the item |
| recipient_ids | – | – | Recipients to resend to (max 10); defaults to the alias's recipients |
No output schema declared.
No examples provided.
resend_recipient_verification ~38
Resend the verification email for an unverified recipient.
| Name | Type | Req | Description |
|---|---|---|---|
| recipient_id | string | yes | The id (UUID) of the item |
No output schema declared.
No examples provided.
restore_alias ~29
Restore a deleted alias.
| Name | Type | Req | Description |
|---|---|---|---|
| alias_id | string | yes | The id (UUID) of the item |
No output schema declared.
No examples provided.
set_alias_labels ~51
Replace the labels attached to an alias.
| Name | Type | Req | Description |
|---|---|---|---|
| alias_id | string | yes | The id (UUID) of the item |
| label_ids | array | yes | Labels the alias should have (empty list removes all) |
No output schema declared.
No examples provided.
set_alias_option ~104
Turn an alias option on or off (activate/deactivate, pin/unpin, limit reply/send to attached recipients).
| Name | Type | Req | Description |
|---|---|---|---|
| alias_id | string | yes | The id (UUID) of the item |
| enabled | boolean | yes | – |
| option | string | yes | '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… |
No output schema declared.
No examples provided.
set_alias_recipients ~97
Replace the set of recipients an alias forwards to.
| Name | Type | Req | Description |
|---|---|---|---|
| alias_id | string | yes | 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 | yes | Recipients the alias should forward to (empty list = default recipient) |
No output schema declared.
No examples provided.
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.
pypi · addy-mcp
claude mcp add former-stranger-addy-mcp -- uvx addy-mcp
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.