ai.powerline/inbox-preview
REMOTE · API.POWERLINE.AI
Render HTML/.eml emails in real Gmail, Outlook & Yahoo web clients and screenshot them
Available components
Last scanned (5 hours ago)
Scores higher than 64% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Testing and QA
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 484 tokens (~121/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 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 4 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
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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 19 Sept 26 0
- Schema quality: 103 → 121 ▼ functional
- “submit_preview” added an optional parameter “include_full_page” cosmetic
- 27 Aug 26 0
- Stability: 0.97 → pass security
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 5 Nov 2026 · Probed https://api.powerline.ai/v1/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=powerline.ai | CN=YE1,O=Let's Encrypt,C=US | 26 Oct 2026 | 24 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6777cf730e7da9c4e419e4f9b917d833a4c |
| SANs: *.powerline.ai, powerline.ai | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.powerline.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| powerline.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.powerline.ai/v1/mcp | Verified | 200 | |
| http (plaintext) | http://api.powerline.ai/v1/mcp | Inconclusive | 405 |
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 →
get_job ~40
Get the status and screenshots for a preview job. Poll until status is "completed".
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | The job ID returned by submit_preview |
No output schema declared.
No examples provided.
get_screenshot ~109
Fetch a rendered screenshot. Returns the image URL for the given job, client, width, and environment (color scheme / images).
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | yes | Client ID |
| color_scheme | string | – | The render's color scheme |
| images_disabled | boolean | – | Whether the render had images blocked |
| job_id | string | yes | The job ID |
| viewport_width | number | yes | Viewport width of the render, matching the job (1280 when the job used client defaults) |
No output schema declared.
No examples provided.
list_clients ~29
List the email clients this deployment can render right now, with their rendering tier, engine, and capabilities
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
submit_preview ~306
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 or eml. |
| html | string | – | The full email HTML to preview. Provide exactly one of html or eml. |
| include_full_page | boolean | – | Also screenshot the whole client window around the opened email (the mailbox UI as well as the message), returned as full_page on each render next to the usual email-only screenshot. Default false. B… |
| 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. Default false: they cost more than the… |
| 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 width, light. |
| subject | string | – | Email subject line |
No output schema declared.
No examples provided.
How do I install the ai.powerline/inbox-preview MCP server?
ai.powerline/inbox-preview is a hosted endpoint at https://api.powerline.ai/v1/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.powerline.ai
claude mcp add --transport http ai-powerline-inbox-preview 'https://api.powerline.ai/v1/mcp'
What is the ai.powerline/inbox-preview MCP server?
ai.powerline/inbox-preview is an MCP server listed in the public MCP registry as ai.powerline/inbox-preview. Render HTML/.eml emails in real Gmail, Outlook & Yahoo web clients and screenshot them. This page covers its hosted endpoint (https://api.powerline.ai/v1/mcp).
Is the ai.powerline/inbox-preview MCP server safe to use?
ai.powerline/inbox-preview scores 75 out of 100 on VerifyMCP. 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 ai.powerline/inbox-preview MCP server expose?
ai.powerline/inbox-preview exposes 4 tools: list_clients, submit_preview, get_job, get_screenshot. Their descriptions and schemas cost roughly 484 tokens of context every time the server is loaded.
Does the ai.powerline/inbox-preview MCP server require authentication?
No. We connected to ai.powerline/inbox-preview without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ai.powerline/inbox-preview MCP server still maintained?
ai.powerline/inbox-preview is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.