# jmshinhwa/readystack-mcp [Health: Active]

**Category:** ⚖️ Legal  
**Repository:** https://github.com/jmshinhwa/readystack-mcp  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/jmshinhwa-readystack-mcp

## Description
Regulation and deadline linters for EU CRA, DORA, NIS2, the EU AI Act, PCI DSS, WCAG, e-invoicing and more, reporting file, line and fix for each finding.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "readystack-mcp": {
    "command": "npx",
    "args": ["-y","@readystack/k8s-removed-api-lint"]
  }
}
```

## Documentation

## What jmshinhwa/readystack-mcp does

The jmshinhwa/readystack-mcp MCP server is a repository of 40 focused compliance and lifecycle linting packages. Each package targets a defined rule set, such as EU Cyber Resilience Act reporting deadlines, DORA contract or register requirements, NIS2-related checks, EU AI Act model-card documentation, PCI DSS payment-page scripts, WCAG forms, e-invoicing formats, Kubernetes removed APIs, GitHub Actions shutdown dates, and expiring model or base-image versions.

The packages are intended for the Developer Tools category and are useful when compliance logic needs to run alongside code or configuration review. Results identify the relevant file and line and include a remediation or replacement where the rule supports one. The repository states that its packages are not affiliated with ReadyStack at readystack.dev.

## How it works

Every package uses a rule set shipped inside its npm package. Checks run offline against the files, directories, or text supplied to the process; the README states that no network calls are made. The same package exposes three operating modes:

- MCP over stdio for an agent or MCP client
- A command-line interface for individual files or directories
- A CI mode that can return a non-zero exit status when findings are present

The standard MCP tools are `check_file`, `check_text`, and `check_dir`. `check_text` evaluates content supplied directly, while `check_file` reads one file and `check_dir` performs a workspace-wide sweep with an exportable report and CI exit code.

## Setup and configuration

To use the jmshinhwa/readystack-mcp MCP server locally, select the package for the rule set you need and configure an MCP client to run it with `npx`. The documented pattern passes `--mcp` to the package command. For example, the Kubernetes checker is configured with `npx -y @readystack/k8s-removed-api-lint --mcp`.

The repository also publishes a remote streamable-HTTP endpoint at `https://mcp.getreadystack.com/mcp`. That endpoint requires no account or key according to the README and exposes `find_checker` for searching available checkers and `run_checker` for testing pasted text. A client can connect using its MCP server URL configuration. The README names Claude, ChatGPT developer mode, Gemini CLI, Cursor, VS Code, Claude Code, and Windsurf usage patterns.

For command-line or CI use, invoke the package with `--file` for one file or `--dir . --ci` for a repository sweep. The README says that `check_text` and `check_file` are available without an account, while `check_dir` requires a licence key from getreadystack.com. No environment-variable name for that key is specified in the supplied material.

## Tools and capabilities

The jmshinhwa/readystack-mcp MCP server supports checks across varied inputs and technologies, including XML invoices, YAML manifests, workflow files, model cards, privacy manifests, source code, dependency metadata, HTML, and compliance records. Representative packages cover:

- EU CRA and CSAF reporting clocks
- DORA ICT contract clauses and registers
- PCI DSS 6.4.3 and WCAG 2.1 or 2.2 checks
- EU AI Act model-card documentation
- KSeF, NF-e, UBL, CII, and EN 16931 invoice rules
- Kubernetes API removals and GitHub Actions end-of-life dates
- TLS certificate lifetime, base-image end of life, model retirement, and licence changes

Use `find_checker` on the remote service when the applicable checker is not known. It can search by regulation, deadline, file type, or platform.

## Limitations and notes

This repository contains separate npm packages rather than one universal checker. The applicable rules depend on the package selected and the input supplied. Offline execution means the bundled rule data is used; the README does not promise live retrieval of regulatory or vendor updates for locally installed packages. The remote service may receive newly published checkers over time.

The supplied material does not identify a licence for the repository or provide an environment-variable name for licensing. It also states that directory sweeps and their report or CI behavior require a licence key, whereas file and text checks do not.

_Full upstream README: https://allmcps.com/mcp/jmshinhwa-readystack-mcp/readme_