Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

ai.powerline/inbox-preview

REMOTE · API.POWERLINE.AI · SCANNED AUG 3

Render HTML/.eml emails in real Gmail, Outlook & Yahoo web clients and screenshot them

Available components

61 Trust /100
Trust breakdown (6 categories)

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 →

Endpoint Security46
Transport & Reachability100
Schema Quality & AI Usability71
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 412 tokens (~103/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 Management20
  • Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · api.powerline.ai

# add to Claude Code
claude mcp add --transport http ai-powerline-inbox-preview https://api.powerline.ai/v1/mcp
# ~/.codex/config.toml
[mcp_servers.ai-powerline-inbox-preview]
url = "https://api.powerline.ai/v1/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-powerline-inbox-preview": {
      "type": "remote",
      "url": "https://api.powerline.ai/v1/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add ai-powerline-inbox-preview --url https://api.powerline.ai/v1/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  ai-powerline-inbox-preview:
    url: "https://api.powerline.ai/v1/mcp"
// mcp.json
{
  "mcpServers": {
    "ai-powerline-inbox-preview": {
      "type": "http",
      "url": "https://api.powerline.ai/v1/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 3 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Jul 26 −2
    • 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 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 29 Jul 26 +1
    • Stability: unverified → 0.03 functional
  • 28 Jul 26 59

    First indexed and scored.

Diagnostics

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 3 Aug 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=YE2,O=Let's Encrypt,C=US 30 Jun 2026 28 Sept 2026 ECDSA 256 ECDSA-SHA384 5a680fefd8b8265b2dd06ed4d8f5d0835e7
SANs: *.powerline.ai, powerline.ai
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
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
DNSSEC insecure

Validation of api.powerline.ai. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 3799 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
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
MCP tools — 4 exposed · ~412 tokens

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.

Tool Tokens
get_job ~40

Get the status and screenshots for a preview job. Poll until status is "completed".

NameTypeReqDescription
job_idstringyesThe 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).

NameTypeReqDescription
clientstringyesClient ID
color_schemestringThe render's color scheme
images_disabledbooleanWhether the render had images blocked
job_idstringyesThe job ID
viewport_widthnumberyesViewport 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 ~234

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.

NameTypeReqDescription
emlstringA complete raw RFC 822 message (.eml), base64-encoded — inserted verbatim (real headers, multipart, attachments). Max 10MB decoded. Provide exactly one of html or eml.
htmlstringThe full email HTML to preview. Provide exactly one of html or eml.
include_previewsbooleanAlso 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…
rendersarrayExactly 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.
subjectstringEmail subject line

No output schema declared.

No examples provided.