Easy Email Builder
NPM · EASY-EMAIL-BUILDER-MCP
Design HTML email templates with AI: render to HTML and open them in a visual editor
Available components
Last scanned (9 hours ago)
Scores higher than 37% of npm servers
Category Design and Media
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
- No install/post-install scripts declared.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 5 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability40
- 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 480 tokens (~96/item across 5 items; 4 tools + 1 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 Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.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 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 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 +25
- Injection markers: 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
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 0 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: fair functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: pass functional
- First check of Tool coverage: 100 functional
- 11 Oct 26 39
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 17 Oct 2026 · Analysed npm/easy-email-builder-mcp@0.1.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
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 →
build_email Build email ~252
Validates a template, renders the final email HTML, lists its variables, and returns a preview link that opens the email in the Easy Email Builder visual editor (where it can be edited and exported). Accepts the tree format ({ layout, header, footer, blocks }) or a flat editor document. On validation errors nothing is rendered; fix them and call again. "warnings" also flags things that break in Outlook or Gmail (nested columns, oversized images, unsupported CSS in raw HTML, clipping); fix those too unless the user accepts them.
| Name | Type | Req | Description |
|---|---|---|---|
| documentOutputPath | string | – | Also write the flat editor document (JSON) to this file path |
| htmlOutputPath | string | – | Also write the HTML to this file path |
| include | array | – | What to return besides the preview link and variables. Default: ["html"]. "document" is the flat JSON for the EmailBuilder React component. |
| template | object | yes | The template: { layout?, header?, footer?, blocks: [...] } (see get_block_reference) or a flat editor document |
| variables | object | – | Fallback values for contact variables used in the template, e.g. { "first_name": "there" } |
No output schema declared.
No examples provided.
get_block_reference Template format reference ~32
The template format: block types and their properties, layout, colors, variables. Read this before writing a template.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_template Get a starter template ~66
Returns a starter template to adapt. "tree" (default) is the nested format build_email accepts; "document" is the flat editor JSON.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Default: tree |
| name | string | yes | Template name from list_templates, e.g. "welcome" |
No output schema declared.
No examples provided.
list_templates List starter templates ~52
Lists the starter email templates (welcome, newsletter, order confirmation, password reset, …) and the built-in header/footer ids usable in build_email.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Only list starter templates in this category |
No output schema declared.
No examples provided.
How do I install the Easy Email Builder MCP server?
Easy Email Builder runs locally as an npm package, launched with npx -y easy-email-builder-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · easy-email-builder-mcp
claude mcp add shahkarkhan440-easy-email-builder -- npx -y easy-email-builder-mcp
What is the Easy Email Builder MCP server?
Easy Email Builder is an MCP server listed in the public MCP registry as io.github.Shahkarkhan440/easy-email-builder. Design HTML email templates with AI: render to HTML and open them in a visual editor. This page covers its npm package (easy-email-builder-mcp).
Is the Easy Email Builder MCP server safe to use?
Easy Email Builder scores 64 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 17 October 2026. It declares no install or post-install scripts. 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 Easy Email Builder MCP server expose?
Easy Email Builder exposes 4 tools: get_block_reference, list_templates, get_template, build_email. Their descriptions and schemas cost roughly 402 tokens of context every time the server is loaded.
Is the Easy Email Builder MCP server still maintained?
Easy Email Builder is still listed as active in the MCP registry. We last reached this channel on 17 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 Easy Email Builder MCP server under?
Easy Email Builder declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.