
Fedramp Oscal Ssp Lint
io.github.jmshinhwaPublished by GitHub account jmshinhwav1.0.2Updated Nov 3, 2026
16 checks on a system-security-plan JSON, in your editor, before a validator returns the package
Overview
Local stdio MCP server that runs 16 checks on a FedRAMP OSCAL system-security-plan JSON file so an assistant can lint it before validation.
- What you can do
- Run 16 lint checks against a system-security-plan JSON document.
- Report problems found in the plan so they can be fixed before a validator processes the package.
- Work inside the editor workflow, on a local file, rather than through a hosted service.
- When to use it
- Useful when you author or review FedRAMP OSCAL system-security-plan JSON and want early feedback on problems before submitting the package to a validator.
- Requirements
- Runs as a local process over stdio, started with npx from the npm package @readystack/fedramp-oscal-ssp-lint, so Node.js and network access for the package are needed. No authentication, environment variables or headers are declared. Desktop only.
Installation
In SourceWeft
- Open Fedramp Oscal Ssp Lint in the dashboard and add it to a workspace.
- 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
0Version history
1- v1.0.2LatestSep 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.