Outlook Email Html Lint

io.github.jmshinhwaPublished by GitHub account jmshinhwav0.1.1Updated Oct 27, 2026

Classic Outlook renders with the Word engine, the new Outlook with WebView2. Lint one email file aga

VerifiedSTDIODesktop onlyDeveloper ToolsCommunication & Collaboration

Overview

AI-generated overview

Local MCP server that lints a single email HTML file against Outlook rendering differences, so an assistant can check markup before sending.

What you can do
  • Lint one email HTML file against Outlook rendering behavior.
  • Account for the difference between classic Outlook (Word engine) and new Outlook (WebView2).
  • No tool list is published, so the exact operations are not documented in the supplied material.
When to use it
Useful when you build or edit HTML email and want an assistant to check a file for Outlook-specific rendering problems before it is sent or handed to a designer.
Requirements
Runs as a local stdio process on the user's machine, started with npx from the npm package @readystack/outlook-email-html-lint, so Node.js and network access for the package download are needed. Desktop only; no authentication, environment variables or headers are declared.
Before you install
The supplied description is truncated and the README only advertises VS Code themes and a website, so the actual behavior and tool set cannot be verified from this listing. Review the package before running it, since npx executes third-party code locally.

Installation

In SourceWeft

  1. Open Outlook Email Html Lint in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

readystack-themes

Made by ReadyStack · free calculators and templates at getreadystack.com VS Code themes by ReadyStack

Source: README.md at commit ee1c884

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestSep 18, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.