agentmailkit
PYPI · AGENTMAILKIT
Run scheduled LLM-written email digests from local files and feeds. Local-first MCP server.
Available components
Last scanned (22 hours ago)
Scores higher than 82% 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
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 86 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 272 tokens (~68/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% 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
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 19 Nov 26 0
- Provenance: unverified → fail ▼ security
- Stability: 0.97 → pass security
- 18 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- Stability: pass → 0.97 functional
- 15 Nov 26 0
- Provenance: fail → unverified ▼ security
- 13 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 12 Nov 26 0
- Stability: 0.97 → pass security
- 11 Nov 26 +1
- Provenance: unverified → fail ▼ security
- Security disclosure: unverified → fail ▼ functional
- 10 Nov 26 0
- Provenance: fail → unverified ▼ security
- Security disclosure: fail → unverified ▼ functional
- 9 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
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 21 Nov 2026 · Analysed pypi/agentmailkit@0.2.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | Known build tool | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
list_jobs ~37
List every configured job; takes no arguments and returns one object per job with id, schedule, sources, delivery, render, model and status.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
list_plugins ~41
List the registered plugin names grouped by kind, optionally narrowed to one kind out of source, model, gate, delivery, render or post.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
preview_job ~76
Render what the job named by job_id would email, optionally overriding its model (pass model="echo" for an offline preview), and return subject, path, chars, truncated, body and would_deliver_to; this path writes to a local file and can never send.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | – |
| model | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
run_job ~64
Run the job named by job_id through the real pipeline and return its run receipt; dry_run defaults to true and stops before delivery, while dry_run=false SENDS REAL EMAIL from the configured inbox.
| Name | Type | Req | Description |
|---|---|---|---|
| dry_run | boolean | – | – |
| job_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
How do I install the agentmailkit MCP server?
agentmailkit runs locally as a PyPI package, launched with uvx --from 'agentmailkit[mcp]' agentmailkit mcp. The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
pypi · agentmailkit
claude mcp add ariaxhan-agentmailkit -- uvx --from 'agentmailkit[mcp]' agentmailkit mcp
The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it.
What is the agentmailkit MCP server?
agentmailkit is an MCP server listed in the public MCP registry as io.github.ariaxhan/agentmailkit. Run scheduled LLM-written email digests from local files and feeds. Local-first MCP server. This page covers its PyPI package (agentmailkit).
Is the agentmailkit MCP server safe to use?
agentmailkit scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. 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 agentmailkit MCP server expose?
agentmailkit exposes 4 tools: list_jobs, run_job, preview_job, list_plugins. Their descriptions and schemas cost roughly 218 tokens of context every time the server is loaded.
Is the agentmailkit MCP server still maintained?
agentmailkit 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 agentmailkit MCP server under?
agentmailkit 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 agentmailkit MCP server?
VerifyMCP ran 16 checks on agentmailkit, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.