Security Txt Cra Lint

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

13 rules that decide whether a vulnerability report ever reaches you

VerifiedSTDIODesktop onlySecurity & Monitoring

Overview

AI-generated overview

A local MCP server that lints security.txt files against 13 rules, helping an assistant check whether vulnerability reports can reach you.

What you can do
Checks security.txt files against a set of 13 lint rules that decide whether a vulnerability report ever reaches you. Runs locally over stdio as an npm package invoked with npx. No tools are listed in the manifest, so the exact operations are not documented.
When to use it
Worth considering when you maintain a security.txt file and want an assistant to review it for problems that could stop vulnerability reports from reaching you.
Requirements
Runs as a local process on the user's machine via npx from the npm package @readystack/security-txt-cra-lint; Node.js is needed. No authentication, environment variables or headers are declared. Desktop only.
Before you install
The README text describes unrelated VS Code themes and does not document usage, so the server's behavior is largely unverified from the supplied material. Review the package before running it locally.

Installation

In SourceWeft

  1. Open Security Txt Cra 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.7LatestSep 26, 2026
  2. v1.0.3Sep 19, 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.