Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.michielinksee/bantou

NPM · @KANSEI-LINK/BANTOU · SCANNED SEP 27

AI bookkeeping agent for Japanese accountants — auto-classifies freee/Yayoi/MF/TKC transactions.

Available components

0 this week 82 Trust /100
Trust breakdown (7 categories)

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 Security98
  • 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
  • 60 of 157 dependencies flagged as unhealthy (2 deprecated). View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability71
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1719 tokens (~132/item across 13 items; 13 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
  • Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 78% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the io.github.michielinksee/bantou MCP server?

io.github.michielinksee/bantou runs locally as an npm package, launched with npx -y @kansei-link/bantou. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @kansei-link/bantou

# add to Claude Code
claude mcp add michielinksee-bantou -- npx -y @kansei-link/bantou
// .cursor/mcp.json
{
  "mcpServers": {
    "michielinksee-bantou": {
      "command": "npx",
      "args": [
        "-y",
        "@kansei-link/bantou"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "michielinksee-bantou": {
      "command": "npx",
      "args": [
        "-y",
        "@kansei-link/bantou"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add michielinksee-bantou -- npx -y @kansei-link/bantou
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "michielinksee-bantou": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@kansei-link/bantou"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add michielinksee-bantou --command npx --arg -y --arg @kansei-link/bantou
# ~/.hermes/config.yaml
mcp_servers:
  michielinksee-bantou:
    command: "npx"
    args: ["-y", "@kansei-link/bantou"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "michielinksee-bantou": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@kansei-link/bantou"
      ]
    }
  }
}
# add to Vellum
assistant mcp add michielinksee-bantou -t stdio -c npx -a -y @kansei-link/bantou
// mcp.json
{
  "mcpServers": {
    "michielinksee-bantou": {
      "command": "npx",
      "args": [
        "-y",
        "@kansei-link/bantou"
      ]
    }
  }
}
Changelog

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.

  • 26 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 25 Sept 26 0
    • 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 +1
    • Security disclosure: fail → unverified ▼ functional
  • 22 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 21 Sept 26 +1
    • Stability: 0.97 → pass security
  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

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 27 Sept 2026 · Analysed npm/@kansei-link/bantou@0.2.3

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 157 packages
Packages resolved 157
Deprecated 2
Stale 58
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 13 exposed · ~1,719 tokens

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 →

Tool Tokens
check_duplicate ~56

Check if a transaction already exists in freee (= by date + amount + memo prefix). Use BEFORE register to prevent double-posting.

NameTypeReqDescription
amountnumberyes–
datestringyes–
memostringyes–

No output schema declared.

No examples provided.

check_exclusion ~107

7-rule exclusion check for Japanese accounting. Returns excluded:true if transaction should NOT be auto-journalized. Rules: 内容不明デビット / 借入金返済 / 社保税金 / 給与支払い / 投資 / ATM出金 / 公共料金.

NameTypeReqDescription
amountnumberyes–
employeesarray–Optional employee name list (= for salary_payment detection)
memostringyes–
partner_namestring––

No output schema declared.

No examples provided.

classify_transaction ~112

Two-stage classifier for Japanese tax accounting. Stage 1: keyword dictionary match (14 categories × ~50 keywords). Stage 2 (= deferred to Phase 1.B): Claude API fallback. Returns 勘定科目 + 税区分 + confidence.

NameTypeReqDescription
amountnumberyesTransaction amount (JPY)
datestringyesISO 8601 date YYYY-MM-DD
memostringyes取引摘要
partner_namestring–取引先名 (optional)

No output schema declared.

No examples provided.

correct_classification ~341

税理士修正フィードバック。誤分類を記録し、同パターンの取引が今後来たら修正後の勘定科目を自動適用。Linksee Memory caveat layer と同等(= 永続記憶、二度と同じ誤りをしない)。修正は全社共通 or 特定会社のみに適用可能。

NameTypeReqDescription
company_idnumber–特定会社のみに適用(省略 = 全社共通)
from_category_idstring–誤分類だった勘定科目ID(optional)
from_category_name_jastring–誤分類だった勘定科目名(optional)
memo_patternstringyesこの修正が適用される摘要パターン(例: "スターバックス 渋谷")
partner_namestring–取引先名(optional — memo_pattern だけでもOK)
reasonstringyes修正理由(例: "1人利用・5,000円以下は会議費")
to_category_idstringyes正しい勘定科目ID
to_category_name_jastringyes正しい勘定科目名
to_freee_account_codenumber–正しいfreee勘定科目コード(省略時は辞書から補完)
to_tax_codenumber–正しい税区分コード(省略時は辞書から補完)

No output schema declared.

No examples provided.

freee_doctor ~105

Diagnose the freee connection in ONE shot. Checks: (1) where the access token is sourced (FREEE_ACCESS_TOKEN env vs secrets file), (2) whether the token is expired (24h TTL, no auto-refresh), (3) lists ALL 事業所 the token can access and flags whether your configured company_id is live — fixes the "which of my test companies is the real one?" problem. Run this FIRST whenever a freee call fails.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

generate_monthly_report ~188

Generate a monthly review report. Takes transaction data (from freee API or CSV import), classifies all transactions, detects anomalies, and produces a structured Markdown report with category breakdown, anomaly alerts, and review items. Designed for tax accountants to present to clients.

NameTypeReqDescription
company_namestring–会社名 / 顧問先名
compare_labelstring–Comparison label (e.g. "前月", "前年同月")
compare_transactionsarray–Previous period transactions for comparison (optional)
formatstring––
monthstringyesTarget month YYYY-MM (e.g. "2026-05")
transactionsarray–Array of transactions to analyze. If omitted, fetches from freee API for the given month.
use_freeeboolean–Fetch transactions from freee API instead of providing them

No output schema declared.

No examples provided.

import_csv ~242

Import CSV from 弥生会計/freee/MoneyForward or generic format. Auto-detects source format from headers. Runs each transaction through the full classification pipeline (Stage 0 exclusion → Stage 1+2 classification → confidence routing). Returns categorized results + review queue + Markdown report. 弥生 users: export 仕訳日記帳 as UTF-8 CSV.

NameTypeReqDescription
amount_columnstring–Column name for amount (generic CSV only)
company_idnumber–顧問先ID。会社限定の修正を適用する場合は必須
csv_contentstringyesRaw CSV text (UTF-8). Paste the full CSV content.
date_columnstring–Column name for date (generic CSV only)
include_csv_outputboolean–Return the full classified CSV (set false for very large imports)
memo_columnstring–Column name for memo/description (generic CSV only)
partner_columnstring–Column name for partner name (generic CSV only, optional)
sourcestring–Force source format (default: auto-detect from headers)

No output schema declared.

No examples provided.

list_freee_companies ~41

List all companies (事業所) accessible by the configured freee OAuth token. Returns company IDs + names. Used for multi-company batch processing.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_freee_deals ~84

List transactions (取引) from freee API for the configured company. Useful for sync + classification dogfood.

NameTypeReqDescription
end_issue_datestring–YYYY-MM-DD
limitnumber––
offsetnumber––
start_issue_datestring–YYYY-MM-DD
typestring–Filter by income or expense

No output schema declared.

No examples provided.

nightly_run ~190

Nightly batch pipeline. Processes ALL companies accessible by the token (= multi-company batch). Pipeline per company: fetch unprocessed (status=unsettled) → Stage 0 exclusion → Stage 1+2 classify → confidence routing (high=auto, medium=auto+log, low=human_review) → aggregate summary. Currently dry-run only (write-back pending Phase 1.B).

NameTypeReqDescription
company_idsarray–Override: process only these company IDs (default: all accessible)
concurrencynumber–Max parallel companies (default: 3, freee rate limit safe)
deals_per_companynumber–Max deals fetched per company
dry_runboolean–Currently always dry_run (= write-back pending Phase 1.B)
period_endstring–YYYY-MM-DD end date filter
period_startstring–YYYY-MM-DD start date filter

No output schema declared.

No examples provided.

recall_memory ~147

過去の分類パターン・修正履歴を検索。取引の摘要/取引先から過去パターンを参照し、分類結果の根拠を確認。Memory stats(pattern hit率等)の確認にも使用。

NameTypeReqDescription
amountnumber–金額(±5% 範囲でマッチ)
memostring–取引摘要(パターン検索用)
partner_namestring–取引先名(optional)
show_correctionsboolean–全修正履歴を表示
show_statsboolean–Memory 全体統計を表示

No output schema declared.

No examples provided.

reconcile_cross_saas ~60

Cross-SaaS reconciliation (= freee ↔ MF). Currently freee-only mode (= MF connector pending Phase 1.B). Detects duplicate fingerprints within freee.

NameTypeReqDescription
period_endstringyes–
period_startstringyes–

No output schema declared.

No examples provided.

upsert_partner ~46

取引先マスタ auto-creation in freee. Fuzzy match against existing partners; if new, create. Returns partner_id.

NameTypeReqDescription
partner_namestringyes–

No output schema declared.

No examples provided.

Common questions

What is the io.github.michielinksee/bantou MCP server?

io.github.michielinksee/bantou is an MCP server listed in the public MCP registry as io.github.michielinksee/bantou. AI bookkeeping agent for Japanese accountants, auto-classifies freee/Yayoi/MF/TKC transactions. This page covers its npm package (@kansei-link/bantou).

Is the io.github.michielinksee/bantou MCP server safe to use?

io.github.michielinksee/bantou scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 27 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.michielinksee/bantou MCP server expose?

io.github.michielinksee/bantou exposes 13 tools: classify_transaction, check_exclusion, import_csv, generate_monthly_report, list_freee_deals, and 8 more. Their descriptions and schemas cost roughly 1,719 tokens of context every time the server is loaded.

Is the io.github.michielinksee/bantou MCP server still maintained?

io.github.michielinksee/bantou is still listed as active in the MCP registry. We last reached this channel on 27 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.michielinksee/bantou MCP server under?

io.github.michielinksee/bantou declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.