Wordpress Privacy Lint

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

Finds the 12 author-side privacy duties your plugin PHP breaks, with the article and the fix on ever

VerifiedSTDIODesktop onlyDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Local MCP server that lints WordPress plugin PHP for author-side privacy duties and points to the relevant article and fix.

What you can do
  • Checks WordPress plugin PHP code for privacy problems.
  • Reports which of twelve author-side privacy duties the code breaks.
  • Points to the relevant article and suggested fix for each finding.
  • No individual tools are listed, so exact operations are not documented.
When to use it
Useful when reviewing or shipping a WordPress plugin and you want an assistant to flag privacy obligations in the plugin's PHP before release.
Requirements
Runs locally over stdio, started with npx from the npm package @readystack/wordpress-privacy-lint, so Node.js and network access for the package download are needed. No authentication, environment variables or headers are declared.
Before you install
The README is largely unrelated to the tool and only mentions VS Code themes and a website, so documentation is thin; verify what it does before relying on its findings. It inspects your plugin source code locally.

Installation

In SourceWeft

  1. Open Wordpress Privacy 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

2
  1. v1.0.5LatestSep 23, 2026
  2. v1.0.1Sep 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.