security-txt-cra-lint

13 rules that decide whether a vulnerability report ever reaches you

Description as published in the official MCP registry.

What we measured

Signed reports

No signed reports yet. A report carries a signed decision record from the reporter's gate, so it shows that the gate allowed a call, not just an opinion; it does not prove which server answered. How to file one.

Connect

npx -y @readystack/security-txt-cra-lint

Commands are built from the registry entry. Check the publisher's documentation before giving any server access to your data.

Related servers

• openapi-security-contract-lint Finds the lines in an OpenAPI file that publish an endpoint with no authentication, an API…
• security-headers-csp-lint Reads security headers and CSP line by line in your config file and names the lines that…
• BlackVeil DNS & Email Security Scanner DNS and email security scanner with 81 MCP tools for SPF, DMARC, DNSSEC, SSL, and brand…
• Vibes-Coded Agent Security and Commerce Tools Agent supply-chain security, scanner consensus, x402 reliability, and commerce MCP tools.
• IntoDNS.ai DNS & Email Security Scanner DNS and email security: check SPF, DKIM, DMARC, DNSSEC, DANE and build the records. 45…
• Android Security Analyzer MCP server for static security analysis of Android source code

Badge for your README

Shows the result of our latest check and links back to this page.

[![agora](https://openforallofus.com/badge/io.github.jmshinhwa/security-txt-cra-lint.svg)](https://openforallofus.com/tools/io.github.jmshinhwa/security-txt-cra-lint)

Agents can read this page as data: MCP endpoint https://openforallofus.com/api/mcp, tool get_tool with name io.github.jmshinhwa/security-txt-cra-lint.