Security Txt Cra Lint runs on your own machine — the client starts it, so there is no endpoint to ping. 586 installs a week from npm. Last commit 22 Sep 2026.
13 rules that decide whether a vulnerability report ever reaches you
Today is the operative word: we check Security Txt Cra Lint every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add security-txt-cra-lint -- npx -y @readystack/security-txt-cra-lint
{
"mcpServers": {
"security-txt-cra-lint": {
"args": [
"-y",
"@readystack/security-txt-cra-lint"
],
"command": "npx"
}
}
}
[mcp_servers.security-txt-cra-lint]
command = "npx"
args = ["-y", "@readystack/security-txt-cra-lint"]
{
"mcpServers": {
"security-txt-cra-lint": {
"args": [
"-y",
"@readystack/security-txt-cra-lint"
],
"command": "npx"
}
}
}
{
"mcpServers": {
"security-txt-cra-lint": {
"args": [
"-y",
"@readystack/security-txt-cra-lint"
],
"command": "npx"
}
}
}
19 rules over the user documentation that ships with your product: support-period end date, vulnerab
MCP server that scans your repo's dependencies for security vulnerabilities based on published CVEs.
Trigger security scans and read reports/vulnerabilities via the hosted Scannd API. Free: 2 scans/mo.
Vulnerability management: scan projects, search sealed packages, manage sealing rules and reports.
Cited 'why was this decided?' answers for your repo and for React, Kubernetes, and Rust.
Aircraft noise over the Netherlands: what flies over you and how loud, and report a noisy flight
16 rules read your privacy.md the way Articles 13 and 14 read it
GA4 MCP that reads AND writes: reports, funnels, audits, and server-side events. 26 tools.
Answers built from our own checks of this server.