MCP servers › io.github.respectbarristerk-tech › keiri-files-mcp
MCP server · registry snapshot 2026-11-18 · last checked 2026-11-18
keiri-files-mcp MCP server
Registry name io.github.respectbarristerk-tech/keiri-files-mcp
Keiri Files (Japanese receipt filer) — the publisher's title
by respectbarristerk-tech · GitHub account (the registry's namespace rule)repository: same ownerSource ↗
Local-only MCP for Japanese receipts: rename by rule, CSV ledger, review queue, freee CSV export. — the publisher's description
Summary
io.github.respectbarristerk-tech/keiri-files-mcp is a local MCP server listed in the official MCP registry at version 0.4.1, under the namespace of the GitHub account respectbarristerk-tech. Its linked repository, github.com/respectbarristerk-tech/keiri-files-mcp, belongs to the same GitHub account.
Record checks
4 of 5 record checks met · 4 do not apply
- met: Registry entry is active and says how to run it
- met: Source repository link opens
- met: Repository is not archived
- met: Code pushed to the repository in the 90 days before our check
- not met: Repository publishes a security policy (SECURITY.md)
- not applicable: Package names its licence with a standard (SPDX) identifier
- not applicable: The version the registry lists can be installed and is not withdrawn
- not applicable: npm package carries build provenance (attestation)
- not applicable: No known critical or high advisory in the package or its dependencies
- Not ranked by downloads: not an npm or PyPI package
- Not ranked by stars: 0 stars (ranked from 10)
From public records, not a safety rating. Each check with its reason · Is it safe to install?
Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it
Key facts
- Runs
- local package
- Transport
- standard input/output
- Your own values
- none declared (not a guarantee)
- Package
- MCP bundle
- Repository
- public
- Last tested
- not tested
Tool list
Not read: It could be started, but has not been tested; we call no server's tools for anything we publish, except for a server whose operator has claimed it and given permission (that server's page says so). This is our limit, not the server's. So there is no tool-list size and no result from the three APIs.
How fresh this is
- Live-tested
- no
- Last tested
- not tested
- Latest version
- 0.4.1, published 2026-11-17 (registry, as of the 2026-11-18 snapshot)
- First listed version
- 2026-11-07 (earliest version still in the registry; older removed versions would be earlier)
- Version history
- 2 versions listed, 2026-11-07 to 2026-11-17; 2 in the 90 days before the 2026-11-18 snapshot.(versions still listed in the registry only)
Most recent 2 versions
0.4.1· 2026-11-170.3.1· 2026-11-07
- Registry data
- snapshot 2026-11-18
- Package and repository
- checked 2026-11-18
Dead or stale signals
None found in the records we hold
Looked for and not found: deprecated in the registry; repository link does not open; repository archived; no push in over 365 days. Does not apply: listed version cannot be installed or is withdrawn. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.
Changes since the last refresh
Version 0.3.1 (published 2026-11-07) → 0.4.1 (published 2026-11-17), between the registry lists of 2026-11-17 and 2026-11-18.
The publisher’s GitHub release note for v0.4.1, published 2026-11-17.
Read the release note (the publisher’s text, shown as plain text)
## keiri-files-mcp v0.4.1 レシート・請求書の「読めない・迷う」を推測で確定せず、確認待ちとして残す仕組みと、freee 用CSVの出力を加えた版です。v0.3.1 から 7 ツール増えて 13 ツールになりました。 ### 0.3.1 からの主な変更 **写真・スキャンPDFの読み取り(read_file)** - スマホ写真の向き(EXIF)を直し、AIが読みやすい大きさ(長辺 1568px)に縮めて返します。これまでエラーだった 3.7MB を超える写真も読めます(40MB まで) - 長いレシートは、少し重ねて上から複数の画像に分けて返します - 文字情報のないスキャンPDF(Googleドライブアプリの「ドキュメントをスキャン」など)は、中の画像を取り出して返します - 撮影の基本として「ドキュメントをスキャン」を README・SKILL.md で案内しています **確認待ちと、後から聞く仕組み(新しいツール)** - `pending_add` / `pending_list` / `pending_resolve`: 読めない・私用かもしれない・重複かもしれない等を `整理済み/確認待ち.csv` に記録し、回答を反映します。撮り直しのお願いには撮影日時と読めた範囲を添えます - `question_write` / `answers_read` / `notify_setup_text`: 利用者がチャットにいないときに、Muse(パーソナルAI)が読む質問ファイルを作り、回答ファイルを読みます。メールで知らせたい場合は Claude の Gmail 連携の手順を案内します(このツール自体はメールを送りません) - 医療関係の書類は画像を `整理済み/医療関係/` に移し、医療機関名や元のファイル名を記録・質問に書きません - これまで別に用意していた確認待ち・質問の仕組みを、このツールに統合しました **freee 用CSV(新しいツール `export_freee`)** - 台帳から freee の取引インポート用CSVを作ります(freee への登録はしません)。インボイスなし・事業割合100%以外・軽減税率の可能性などは `freee_要確認.csv` に理由付きで分けます。出力済みの行は次回出しません **カード番号を書かない** - 確認待ち・質問・回答・台帳(`ledger_append`)に、カード番号らしき文字列(16桁前後の数字、`****1234`、「下4桁」「末尾1234」などの表記)が入るとエラーにして書きません **その他(0.4.1 の修正)** - export_freee の日付範囲を検証し、不正な値ではエラーにして何も書かないようにしました - 取引先などが `=` `+` `-` `@` で始まる行は freee 出力から外し、要確認に回します - `pending_list` の日付が不正なときはエラーにしました ### 注意 - 外部通信・削除・子プロセスの実行はこれまでどおりありません。書き込むのは許可フォルダの中だけです - 新しく `整理済み/確認待ち.csv`・`確認待ち/`(連絡用)・`整理済み/医療関係/`・`整理済み/freee出力/` を作ることがあります。既存の `ledger.csv` はそのまま使えます - カード番号の検出は表記ゆれを広く拾いますが完全ではありません(例: 4-6-5桁のアメックス形式、アンダースコア区切りは対象外)。カード番号は書かないでください - 医療関係の回答は確認待ち.csv に原文のまま残ります。回答に医療機関名などを書かないでください - freee への実際の取り込みは、利用者の環境で確認してください(CSV は UTF-8 BOM付き) - 電子帳簿保存法の要件を満たすことは保証しません。税務判断はしません - 動作確認: 自動テスト52件(Linux, Node 22)。Windows の Claude Desktop で v0.4.1 の導入と各ツールの動作を確認(2026-11-17。macOS は未確認) ### 入れ方 Claude Desktop: 添付の `keiri-files-mcp-0.4.1.mcpb` を開いて入れ直してください(設定の許可フォルダはそのまま指定し直してください)。その他のクライアントは README を参照してください。 --- ### English v0.4.1 adds 7 tools (13 in total): photos and scanned PDFs are now returned to your AI as upright, downscaled images (large and tall receipts supported); unclear items go to a pending-confirmation list instead of being guessed, with question/answer files a personal AI (Muse) can relay; and `export_freee` writes a freee import CSV (no automatic registration). Text that looks like a payment card number is rejected in pending records, questions, answers and the ledger. Still local-only: no network access, no email sending, no deletion. Not a guarantee of compliance with Japanese e-bookkeeping law; no tax decisions. SHA-256 (keiri-files-mcp-0.4.1.mcpb): 1fc2c14ac12548078929814e4106ce59efb39f4c13e5c0c06a09e570f9611342
Source: the official MCP Registry list on 2026-11-17 and on 2026-11-18; release notes from the GitHub Releases API, checked 2026-11-18.
What it is
How do I add it to my client?
Config from the registry entry
- No config: the MCP bundle is a file to install in a client that supports bundles, not a command.
Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.
What do the published files and outside lists say?
Read as text · nothing run · no tool called
Package files
- Bundle platforms (MCPB). The bundle lists platforms win32, darwin and linux (manifest.json compatibility). Source: read 2026-11-18.
- MCP SDK in the package files. Not read yet: added with the next daily run.
- Build workflow. Not read yet: added with the next daily run.
Outside lists
- CVE records (NVD). No CVE record in the NVD feeds we read links this server's repository. Source: read 2026-11-18. This product uses the NVD API but is not endorsed or certified by the NVD.
- GitHub advisories. No GitHub advisory names this entry's listed package. Source: read 2026-11-18. GitHub Advisory Database, CC BY 4.0
- Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-18. Source: read 2026-11-18.
- Cline marketplace. Not in the Cline marketplace on 2026-11-18. Source: read 2026-11-18.
Read as text from published files and outside lists. Nothing was installed or run, and no tool was called. A fact, not a rating. How each fact is read
Does the registry listing match what we found?
Feature #6The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.
| Registry says | We found | Result | Source · date |
|---|---|---|---|
| Repository github.com/respectbarristerk-tech/keiri-files-mcp | Opens publicly | matches | api.github.com · 2026-11-18 |
Who made it?
Feature #7 · lineage
Facts about the publisher. We do not turn them into a trust score.
- Namespace
- io.github.respectbarristerk-tech
- GitHub owner
- a personal account (respectbarristerk-tech)
- Repository
- github.com/respectbarristerk-tech/keiri-files-mcp
- Stars
- 0
- Repository age
- 0–30 days
- Last push
- 0–30 days ago
- Archived
- no
- Security policy
- none found (we looked for SECURITY.md in the repository and in its owner’s .github repository)
Source: the registry entry and api.github.com · 2026-11-18; security policy read from GitHub · 2026-11-08.
Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.
Choosing
Record checks
Public records · not a safety rating4 of 5 record checks met · 4 do not apply
- Not ranked by downloads: not an npm or PyPI package
- Not ranked by stars: 0 stars (ranked from 10)
- MetRegistry entry is active and says how to run itActive, with a package or a remote address.
- MetSource repository link opensThe linked GitHub repository is public.
- MetRepository is not archivedNot archived.
- MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
- Not metRepository publishes a security policy (SECURITY.md)No SECURITY.md in the places GitHub reads it from.What changes this check: GitHub's documentation describes adding a SECURITY.md from the repository's security settings: under Reporting, Security policy, Start setup. GitHub: adding a security policy
- Does not applyPackage names its licence with a standard (SPDX) identifierNot an npm or PyPI package.
- Does not applyThe version the registry lists can be installed and is not withdrawnNot an npm or PyPI package.
- Does not applynpm package carries build provenance (attestation)PyPI packages have no npm-style attestation.
- Does not applyNo known critical or high advisory in the package or its dependenciesNot an npm or PyPI package.
Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-18 (security policy 2026-11-08). No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral
Common questions about io.github.respectbarristerk-tech/keiri-files-mcp
Answered from the data aboveWho publishes io.github.respectbarristerk-tech/keiri-files-mcp?
The registry ties the namespace io.github.respectbarristerk-tech to the GitHub account respectbarristerk-tech; only its owner can publish under it. Its linked repository, github.com/respectbarristerk-tech/keiri-files-mcp, belongs to the same GitHub account. These are facts from the registry and GitHub, not a rating.
Is io.github.respectbarristerk-tech/keiri-files-mcp safe to install?
We do not rate servers as safe or unsafe. 4 of its 5 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.
Has io.github.respectbarristerk-tech/keiri-files-mcp been security tested?
No. It could be started, but has not been tested; we call no server's tools for anything we publish, except for a server whose operator has claimed it and given permission (that server's page says so). This is our limit, not the server's.
Does io.github.respectbarristerk-tech/keiri-files-mcp publish a security policy?
We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.
Where is the source code of io.github.respectbarristerk-tech/keiri-files-mcp?
In github.com/respectbarristerk-tech/keiri-files-mcp, which opens publicly.
Found this page useful?
Anonymous · no sign-inA quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.
Compare with another server
Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.
Security testing
Has it been tested?
Feature #1It could be started, but has not been tested; we call no server's tools for anything we publish, except for a server whose operator has claimed it and given permission (that server's page says so). This is our limit, not the server's. — our limit
Reference
How is it classified?
18 fields
One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.
“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.
Cite or correct this page
Sources and corrections
Suggested citation
ProtocolProbe. “io.github.respectbarristerk-tech/keiri-files-mcp: MCP server record.” Data checked 2026-11-18. https://protocolprobe.com/mcp/servers/io.github.respectbarristerk-tech/keiri-files-mcp
Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.
As JSON: this record in the API · API documentation.
Badge for your README
[](https://protocolprobe.com/mcp/servers/io.github.respectbarristerk-tech/keiri-files-mcp)
It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.
Something wrong, or is this yours?
If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here, except for a server whose operator has claimed it and given permission (that server's page says so).
Write to hello@protocolprobe.com · corrections log · methodology