addy.io
PYPI · ADDY-MCP · 2 COMPONENTS
Manage addy.io email aliases, recipients, domains, rules and blocklist.
Available components
Last scanned (22 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 →
set_domain_default_recipient ~58
Set (or clear) the default recipient for aliases on a custom domain.
| Name | Type | Req | Description |
|---|---|---|---|
| domain_id | string | yes | The id (UUID) of the item |
| recipient_id | – | yes | Recipient id, or null to use the account default |
No output schema declared.
No examples provided.
set_domain_option ~92
Turn a custom domain option on or off.
| Name | Type | Req | Description |
|---|---|---|---|
| domain_id | string | yes | The id (UUID) of the item |
| enabled | boolean | yes | – |
| option | string | yes | '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… |
No output schema declared.
No examples provided.
set_recipient_option ~131
Turn a recipient option on or off.
| Name | Type | Req | Description |
|---|---|---|---|
| enabled | boolean | yes | – |
| option | string | yes | '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 | yes | The id (UUID) of the item |
No output schema declared.
No examples provided.
set_rule_active ~38
Activate or deactivate a rule.
| Name | Type | Req | Description |
|---|---|---|---|
| active | boolean | yes | – |
| rule_id | string | yes | The id (UUID) of the item |
No output schema declared.
No examples provided.
set_username_default_recipient ~57
Set (or clear) the default recipient for aliases on a username.
| Name | Type | Req | Description |
|---|---|---|---|
| recipient_id | – | yes | Recipient id, or null to use the account default |
| username_id | string | yes | The id (UUID) of the item |
No output schema declared.
No examples provided.
set_username_option ~86
Turn a username option on or off.
| Name | Type | Req | Description |
|---|---|---|---|
| enabled | boolean | yes | – |
| option | string | yes | '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 | yes | The id (UUID) of the item |
No output schema declared.
No examples provided.
update_alias ~80
Update an alias's description, from name, or labels. Only the fields you pass are changed.
| Name | Type | Req | Description |
|---|---|---|---|
| alias_id | string | yes | 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 |
No output schema declared.
No examples provided.
update_domain ~75
Update a custom domain's description, from name, or auto-create regex.
| Name | Type | Req | Description |
|---|---|---|---|
| auto_create_regex | – | – | Regex limiting which on-the-fly aliases may be auto-created |
| description | – | – | – |
| domain_id | string | yes | The id (UUID) of the item |
| from_name | – | – | Display name for replies/sends |
No output schema declared.
No examples provided.
update_label ~110
Rename a label or change its colour.
| Name | Type | Req | Description |
|---|---|---|---|
| colour | – | – | #06b6d4 cyan, #22c55e green, #eab308 yellow, #f97316 orange, #ef4444 red, #8b5cf6 violet, #64748b slate, #ec4899 pink, #14b8a6 teal, #3b82f6 blue |
| label_id | string | yes | The id (UUID) of the item |
| name | – | – | – |
No output schema declared.
No examples provided.
update_recipient ~38
Set a recipient's description.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | – |
| recipient_id | string | yes | The id (UUID) of the item |
No output schema declared.
No examples provided.
update_rule ~87
Update a rule. Only the fields you pass change; the rest are kept from the current rule.
| Name | Type | Req | Description |
|---|---|---|---|
| actions | – | – | Replaces all actions |
| conditions | – | – | Replaces all conditions |
| forwards | – | – | – |
| name | – | – | – |
| operator | – | – | – |
| replies | – | – | – |
| rule_id | string | yes | The id (UUID) of the item |
| sends | – | – | – |
No output schema declared.
No examples provided.
update_username ~74
Update a username's description, from name, or auto-create regex.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The id (UUID) of the item |
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.