Legal Validator

io.github.EvozimPublished by GitHub account Evozimv1.0.0Updated Oct 24, 2026

Regulatory compliance scanner validating SEC, FTC, and anti-spam rules.

VerifiedSSEWeb executableBusiness & Commerce

Overview

AI-generated overview

A remote MCP server that scans for regulatory compliance issues against SEC, FTC and anti-spam rules.

What you can do
Scans content or business practices for regulatory compliance issues, checking against SEC, FTC and anti-spam rules. Reports findings so an assistant can flag potential violations. Premium settlement is available through a payment signature, though the specific tools are not documented.
When to use it
Useful when reviewing marketing, financial or outreach material for possible SEC, FTC or anti-spam compliance problems before publishing or sending it.
Requirements
A remote SSE endpoint at the provider's hosted address; no local runtime or package is needed. Premium settlement requires a payment-signature header carrying a Base64-encoded EIP-3009 TransferWithAuthorization signature.
Before you install
The payment-signature header is a cryptographic authorization for a blockchain payment; supplying it can move funds, so treat it as a spending credential. The server is remote, so submitted content is sent to a third party. No tool list or documentation is provided, so scan behavior and data handling cannot be verified.

Installation

In SourceWeft

  1. Open Legal Validator in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via SSE. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Evozim%2Flegal-validator/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "legal-validator": {
      "type": "sse",
      "url": "https://legal-validator-mcp.vercel.app/api/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

67% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

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

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.