Email Footer Law Lint

io.github.jmshinhwaPublished by GitHub account jmshinhwav1.0.6Updated Oct 24, 2026

Fourteen checks on an HTML email footer: CAN-SPAM postal address and 10-business-day opt-out, CASL's

Overview

AI-generated overview

Runs fourteen compliance checks on an HTML email footer, covering rules such as CAN-SPAM postal address and opt-out requirements.

What you can do
This local MCP server exposes linting for HTML email footers. According to its registry description, it applies fourteen checks, including CAN-SPAM requirements for a postal address and a 10-business-day opt-out, and CASL-related rules. The manifest does not list individual tool names, so the exact interface is not documented here.
When to use it
Useful when an assistant is drafting or reviewing marketing email templates and you want footer compliance issues flagged before sending. It fits review workflows where a quick automated pass over footer markup is helpful.
Requirements
Runs as a local process over stdio, started with npx from the npm package @readystack/email-footer-law-lint. No authentication, environment variables, or headers are declared. Desktop only; not available as a web executable.
Before you install
The registry description is truncated, so the full set of fourteen checks and their exact behavior are not shown. The README content appears unrelated to this server, so treat it as unreliable. Verify the package and its output before relying on it for legal compliance.

Installation

In SourceWeft

  1. Open Email Footer Law 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

4
  1. v1.0.6LatestSep 23, 2026
  2. v1.0.4Sep 19, 2026
  3. v1.0.3Sep 18, 2026
  4. v1.0.2Sep 16, 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.