io.github.USHIKUNDESUYO/shiwake-mcp
NPM · SHIWAKE-MCP · SCANNED SEP 26
Journal entry testing (JET) for accounting audits. 11 screening rules, zero dependencies.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 581 tokens (~116/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
How do I install the io.github.USHIKUNDESUYO/shiwake-mcp server?
io.github.USHIKUNDESUYO/shiwake-mcp runs locally as an npm package, launched with npx -y shiwake-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · shiwake-mcp
claude mcp add ushikundesuyo-shiwake-mcp -- npx -y shiwake-mcp
{
"mcpServers": {
"ushikundesuyo-shiwake-mcp": {
"command": "npx",
"args": [
"-y",
"shiwake-mcp"
]
}
}
} {
"servers": {
"ushikundesuyo-shiwake-mcp": {
"command": "npx",
"args": [
"-y",
"shiwake-mcp"
]
}
}
} codex mcp add ushikundesuyo-shiwake-mcp -- npx -y shiwake-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ushikundesuyo-shiwake-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"shiwake-mcp"
],
"enabled": true
}
}
} openclaw mcp add ushikundesuyo-shiwake-mcp --command npx --arg -y --arg shiwake-mcp
mcp_servers:
ushikundesuyo-shiwake-mcp:
command: "npx"
args: ["-y", "shiwake-mcp"] {
"McpServers": {
"ushikundesuyo-shiwake-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"shiwake-mcp"
]
}
}
} assistant mcp add ushikundesuyo-shiwake-mcp -t stdio -c npx -a -y shiwake-mcp
{
"mcpServers": {
"ushikundesuyo-shiwake-mcp": {
"command": "npx",
"args": [
"-y",
"shiwake-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 +11
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 59
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 26 Sept 2026 · Analysed npm/shiwake-mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
benford_analysis ~169
金額の先頭桁の分布をベンフォードの法則と比較し、MAD と χ² を返す。母集団の性質を見るための道具で、個別仕訳の判定には使えない。
| Name | Type | Req | Description |
|---|---|---|---|
| amounts | array | – | journals の代わりに金額だけを渡す場合。 |
| digits | number | – | 1 = 先頭1桁、2 = 先頭2桁。既定は 1。 |
| journals | array | – | 仕訳の配列。簡易形 { date, debit_account, credit_account, amount } か、明細形 { date, lines: [{ account, debit, credit }] } のどちらでも受ける。 |
No output schema declared.
No examples provided.
check_balance ~98
貸借が一致しない仕訳だけを返す。取込不良と手入力の混入を最初に落とすために使う。
| Name | Type | Req | Description |
|---|---|---|---|
| journals | array | yes | 仕訳の配列。簡易形 { date, debit_account, credit_account, amount } か、明細形 { date, lines: [{ account, debit, credit }] } のどちらでも受ける。 |
No output schema declared.
No examples provided.
detect_duplicates ~95
計上日・金額・借方科目・貸方科目が完全に一致する仕訳をグループにして返す。
| Name | Type | Req | Description |
|---|---|---|---|
| journals | array | yes | 仕訳の配列。簡易形 { date, debit_account, credit_account, amount } か、明細形 { date, lines: [{ account, debit, credit }] } のどちらでも受ける。 |
No output schema declared.
No examples provided.
list_rules ~39
実装されているスクリーニングルールの一覧と、それぞれが何を示すかの説明を返す。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
screen_journals ~180
仕訳データに全ルールを適用し、リスクスコアの高い順に並べ替えて返す。先に人間が見るべき束を絞り込むための一次スクリーニング。検出は不正の証拠ではない。
| Name | Type | Req | Description |
|---|---|---|---|
| journals | array | yes | 仕訳の配列。簡易形 { date, debit_account, credit_account, amount } か、明細形 { date, lines: [{ account, debit, credit }] } のどちらでも受ける。 |
| options | object | – | スクリーニングの前提条件。監査対象の実態に合わせて渡す。 |
| top | number | – | 上位何件を返すか。既定は 50。 |
No output schema declared.
No examples provided.
What is the io.github.USHIKUNDESUYO/shiwake-mcp server?
io.github.USHIKUNDESUYO/shiwake-mcp is listed in the public MCP registry as io.github.USHIKUNDESUYO/shiwake-mcp. Journal entry testing (JET) for accounting audits. 11 screening rules, zero dependencies. This page covers its npm package (shiwake-mcp).
Is the io.github.USHIKUNDESUYO/shiwake-mcp server safe to use?
io.github.USHIKUNDESUYO/shiwake-mcp scores 70 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 26 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.USHIKUNDESUYO/shiwake-mcp server expose?
io.github.USHIKUNDESUYO/shiwake-mcp exposes 5 tools: screen_journals, check_balance, benford_analysis, detect_duplicates, list_rules. Their descriptions and schemas cost roughly 581 tokens of context every time the server is loaded.
Is the io.github.USHIKUNDESUYO/shiwake-mcp server still maintained?
io.github.USHIKUNDESUYO/shiwake-mcp is still listed as active in the MCP registry. We last reached this channel on 26 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.USHIKUNDESUYO/shiwake-mcp server under?
io.github.USHIKUNDESUYO/shiwake-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.