Render HTML/.eml emails in real Gmail, Outlook & Yahoo web clients and screenshot them
Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read from a real MCP initialize → tools/list handshake against the declared endpoint. No tool was ever invoked — tools/list is the read-only introspection call the protocol defines for this. It reflects what the server advertised at that moment; a hosted endpoint is not pinned to any version and can change without notice.
https://api.powerline.ai/v1/mcp4 tools · 1079mslist_clientsList the email clients this deployment can render right now, with their rendering tier, engine, and capabilitiesList the email clients this deployment can render right now, with their rendering tier, engine, and capabilities
No input schema was published for this tool.
submit_previewSubmit an email for rendering across email clients — full HTML, or a complete raw .eml (base64). Provide exactly one of html/eml. Returns a job ID to poll for results.Submit an email for rendering across email clients — full HTML, or a complete raw .eml (base64). Provide exactly one of html/eml. Returns a job ID to poll for results.
| Parameter | Type | Description |
|---|---|---|
| html | string | The full email HTML to preview. Provide exactly one of html or eml. |
| eml | string | A complete raw RFC 822 message (.eml), base64-encoded — inserted verbatim (real headers, multipart, attachments). Max 10MB decoded. Provide exactly one of html… |
| subject | string | Email subject line |
| include_previews | boolean | Also capture the inbox-list row (how the message looks unread in the list) and the subject heading, returned as inbox_preview / subject_preview on each render.… |
| renders | array | Exactly the renders you want, one entry each (e.g. outlook light + outlook dark are two entries). Omit for the server default: every live client at its default… |
get_jobGet the status and screenshots for a preview job. Poll until status is "completed".Get the status and screenshots for a preview job. Poll until status is "completed".
| Parameter | Type | Description |
|---|---|---|
| job_id* | string | The job ID returned by submit_preview |
get_screenshotFetch a rendered screenshot. Returns the image URL for the given job, client, width, and environment (color scheme / images).Fetch a rendered screenshot. Returns the image URL for the given job, client, width, and environment (color scheme / images).
| Parameter | Type | Description |
|---|---|---|
| job_id* | string | The job ID |
| client* | string | Client ID |
| viewport_width* | number | Viewport width of the render, matching the job (1280 when the job used client defaults) |
| color_scheme | string | The render's color scheme |
| images_disabled | boolean | Whether the render had images blocked |
4 of 4 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
Render HTML/.eml emails in real Gmail, Outlook & Yahoo web clients and screenshot them
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.