io.github.jmshinhwa/crypto-export-notice-lint MCP Server
io.github.jmshinhwa/crypto-export-notice-lint
What this kind of tool is for
- Scan a repository or dependency tree for known vulnerabilities.
- Audit secrets, permissions, or headers during a pre-release review.
- Have your agent explain a suspicious script or config before you run it.
How to compare servers like this
- Failure mode:
- Vulnerability reports are probabilistic; read findings as leads to verify, not verdicts.
- Data leaving the box:
- Check whether files or code are uploaded anywhere before scanning anything private.
- Maintenance signal:
- Security rulesets age fast; stale tools miss new classes of issue.
- Report clarity:
- The best tools say what is wrong, how sure they are, and how to fix it — verify findings yourself.
This page carries your copy-paste config: pick your MCP client in the install section on this page and use the copy button.
What is the io.github.jmshinhwa/crypto-export-notice-lint MCP server?
Ten checks on the export paragraph of a repository that ships encryption
How to install io.github.jmshinhwa/crypto-export-notice-lint
Copy-paste configuration for popular MCP clients.
{
"mcpServers": {
"crypto-export-notice-lint": {
"command": "npx",
"args": [
"-y",
"@readystack/crypto-export-notice-lint",
"--mcp"
]
}
}
}Related MCP servers
Finds the money lines that send the wrong amount to a payment API: the x100 that charges 100x in JPY
View repository →Reads your cloud contract text and names every clause Chapter VI no longer allows, with the article
View repository →15 Prüfungen für Auskunftsschreiben nach Art. 15 DSGVO – samt Monatsfrist ab Eingangsdatum
View repository →電子取引データの索引簿を12ルールで検査し、取引年月日・取引金額・取引先・ファイル名のうち検索要件を満たさない行と直し方を出します。同梱の12行サンプルでは6行・7件を指摘しました。
View repository →status = "ok" compiles clean and the node never appears. 23 rules over 7 config languages, on the fi
View repository →Pflichtinhalte nach § 17, 18, 20 BewachV und § 34a Abs. 1a GewO
View repository →