Sashiko MCP
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Sashiko MCPShow me critical findings no one noticed"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Sashiko MCP
MCP server that lets an AI agent query Sashiko — an AI kernel-patch review service — and hunt for critical/high severity vulnerabilities in the reviewed patches (LPE, UAF, OOB, refcount, race conditions, etc.), including AI reviews that may have gone unnoticed.
Install / config
cd ~/MCP/Sashiko && npm installRegister in opencode (~/.config/opencode/opencode.jsonc). Use the absolute
path to your copy of the repo on that machine (replace <PATH-TO-SASHIKO>
with the actual location):
"sashiko": {
"type": "local",
"command": ["node", "<PATH-TO-Sashiko>/src/index.js"],
"enabled": true
}Optional env: SASHIKO_BASE_URL (default http://34.149.213.196),
SASHIKO_TIMEOUT_MS (default 30000).
Related MCP server: patchwork-mcp-server
Tools
Tool | Purpose |
| service metadata |
| review + tool usage stats |
| paged lists with |
| full patchset detail + AI reviews with parsed findings |
| raw message + diff |
| AI review + model transcript/logs |
| find critical/high findings across patchsets (pre-filtered scan) |
| general severity/class scan (e.g. |
| enumerate the whole API surface |
Example queries
"Find LPE-type vulnerability reviews in applied patches" →
sashiko_findwithclass_keyword="lpe",severity="high""Show me critical findings no one noticed" →
sashiko_find_criticalseverity="critical", then compare against patchset status"What AI reviews mention use-after-free?" →
sashiko_findwithkeywords="use-after-free"
Notes
Reviews are public by design; findings are parsed from
review.output.The
findings_critical/findings_highcounts on the patchset list serve as a cheap pre-filter before fetching detail per patchset.See
docs/api-map.mdfor the full API and finding schema.
This server cannot be deployed
Maintenance
Related MCP Connectors
Security scanner for MCP servers. Detect vulnerabilities, prompt injection, and tool poisoning.
ZEN SecDB MCP server for CVE intelligence, CVSS/EPSS scoring, advisories, SSVC, and package audits.
Hosted CVE + bug-bounty-mechanic MCP: exploitation-first ranking, CVE fact-check, mechanic transfer
MCP server for static security analysis of Android source code
Related MCP Servers
- AlicenseAqualityCmaintenanceAn AppSec-focused MCP server that performs static analysis scans on C/C++ source code for memory-safety vulnerabilities and parses compiled PE/ELF binary headers locally to audit active defensive compiler mitigations (ASLR, DEP/NX, PIE).41MIT
- AlicenseAqualityCmaintenanceEnables LLM agents to query Patchwork kernel patches, series, CI checks, and comments via natural language through a read-only MCP server.8MIT
- AlicenseAqualityCmaintenanceAn MCP server that gives AI assistants the ability to check open-source packages for vulnerabilities, enrich findings with real-world exploit intelligence, and statically analyse whether vulnerable code is actually reachable in your project.31Apache 2.0
- AlicenseAqualityBmaintenanceMCP server for checking packages against an AI-aware vulnerability database, including CVEs, slopsquatting, CISA KEV, and MCP-server trust profiles.10537 PyPIElastic 2.0