
Pqc Deprecation Lint
io.github.jmshinhwaPublished by GitHub account jmshinhwav1.0.3Updated Nov 3, 2026
Dates every quantum-vulnerable algorithm in your code against the NIST IR 8547 clock: deprecated aft
Overview
Local stdio MCP server that dates quantum-vulnerable algorithms in code against the NIST IR 8547 deprecation timeline.
- What you can do
- The manifest lists no tools, so the exact operations are not documented.
- Based on the description, it appears to scan code for quantum-vulnerable algorithms and report when each one becomes deprecated under the NIST IR 8547 schedule.
- It is intended as a lint-style check that an assistant can run over a codebase.
- The README does not describe usage; it only contains unrelated theme and branding text.
- When to use it
- Worth considering if you are preparing code for post-quantum migration and want an assistant to flag cryptographic algorithms against the NIST IR 8547 deprecation dates. The sparse documentation means you should verify its actual behavior before relying on it.
- Requirements
- Runs as a local process over stdio, launched with npx from the npm package @readystack/pqc-deprecation-lint, so Node.js and network access for package download are needed. No authentication, environment variables or headers are declared. Desktop only.
Installation
In SourceWeft
- Open Pqc Deprecation 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
3- v1.0.3LatestSep 19, 2026
- v1.0.2Sep 18, 2026
- v1.0.1Sep 16, 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.