Tax Law MCP
Capped at 80: 1 of 3 real tool calls passed in our test; the tests add up to 90. Why scores are capped
Test points add up to 90; the score is capped at 80 because not every real tool call passed. Not a quality or security rating. Why scores are capped
Test points before the cap (90/100)
- Install20/20
- Handshake30/30
- Maintenance15/25
- Docs15/15
- License10/10
Tested npm tax-law-mcp 0.5.4 (MIT; repo kentaroajisaka/tax-law-mcp). Installed pinned with scripts off (npm --ignore-scripts) and launched: initialize and tools/list over stdio succeeded with no credentials and listed 7 tools (no tool annotations). Real calls: 1 of 3 real function calls passed.
Tool-call test (2026-11-19 UTC, direct MCP stdio client, no LLM): partial. 1 of 3 real function calls passed. Evidence: local test run, Nov 19, 2026 UTC.
Transport (tested 2026-11-19 UTC): stdio
Token cost (estimate): approx. 1903 tokens, cl100k estimate (7 tools, measured 2026-11-19 UTC, version 0.5.4). This is an estimate from our testing of the tool names, descriptions and input schemas, counted with cl100k_base.
Permissions: 7 read, 0 write (state-changing), 0 unclassified · Auth: none · Rate limit: unknown · Pricing unit: unknown
Auth: none. Rate limit: unknown. Pricing unit: unknown.
get_law— readget_saiketsu— readget_tsutatsu— readlist_saiketsu— readlist_tsutatsu— readsearch_law— readsearch_saiketsu— read
handshake and tools listed without a recorded key or OAuth
Score 80/100 · Tools 7 · Token cost approx. 1,903 tokens · Compare · Last tested 2026-11-19 UTC · Version tested 0.5.4 · Package tax-law-mcp · Repo kentaroajisaka/tax-law-mcp
Summary: Tax Law MCP completed an MCP handshake without credentials and exposed 7 tools.
Evidence summary
- Handshake
- pass
- Tools listed
- 7
- Context cost
- approx. 1903 tokens, cl100k estimate (7 tools, measured 2026-11-19 UTC, version 0.5.4; an estimate) ranking · add up your servers' context cost
- API key
- No key needed for the tools we called
- Tested
- 2026-11-19 UTC
Test results
| Test | Result | Points | Evidence |
|---|---|---|---|
| install | pass | 20 | npm install tax-law-mcp --ignore-scripts (Node v24.22.1, Linux) succeeded in 1s. |
| handshake | pass | 30 | MCP initialize + tools/list over stdio succeeded with no credentials; 7 tools listed in 3.3s. |
| maintenance | partial | 15 | Repo pushed 47 days before test. |
| docs | pass | 15 | README over 3,000 chars; install instructions present; mcpServers config example present. Check of the package's own README (README shipped in npm package). |
| license | pass | 10 | MIT (OSI-approved). |
Local-model readiness
Token cost (estimate): approx. 1903 tokens, cl100k estimate for 7 tools · about 23% of an 8k context. This is an estimate from our testing (counted with cl100k_base).
Small-model friendly (schema heuristic, not a model result): unknown.
Not tested
Small-model task runs: Not yet tested.
What we tested and what we didn't
Tested on 2026-11-19 UTC
- Install from the registry
- We connected with no credentials and asked for its tool list: it listed 7 tools (Method details: MCP
initializethentools/list) - Maintenance signals (last push, archived/deprecated status)
- Docs (README length, install and config example)
- License (OSI-approved or not)
- Token cost (estimate)
Not tested
- Security: not audited (no code review, no permission or data-flow analysis)
- Real tasks (no functional task runs yet)
- Behaviour with real credentials or a real account
- Performance, rate limits or load
- Correctness of results beyond the listed tasks
Methodology: how we test. A high score means it installs and responds, not that giving it access to your data carries no risk.
Known security issues
Not yet checked.
Monthly roundup: MCP security issues, October 2026.
Tool list changes
Baseline recorded from the 2026-11-19 UTC test run; changes appear after the next test.
Snapshot hash (fingerprint of the tool list)
df8ff44a5953: SHA-256 of the canonical tool names, descriptions and input schemas. If it changes, the tool list changed.
Raw test record (JSON)
{
"name": "tax-law-mcp",
"version": "0.5.4",
"registry": "npm",
"status": "working",
"tested": "2026-11-19",
"tools_count": 7,
"deprecated": false,
"archived": false,
"tests": {
"install": [
"pass",
20,
"`npm install tax-law-mcp --ignore-scripts` (Node v24.22.1, Linux) succeeded in 1s."
],
"handshake": [
"pass",
30,
"MCP `initialize` + `tools/list` over stdio succeeded with no credentials; 7 tools listed in 3.3s."
],
"maintenance": [
"partial",
15,
"Repo pushed 47 days before test."
],
"docs": [
"pass",
15,
"README over 3,000 chars; install instructions present; `mcpServers` config example present. Check of the package's own README (README shipped in npm package)."
],
"license": [
"pass",
10,
"MIT (OSI-approved)."
]
},
"testedAt": "2026-11-19T06:09:09.954Z"
}Install
npx -y tax-law-mcp
Pin the version we tested
npx -y --ignore-scripts tax-law-mcp@0.5.4
tested 2026-11-19 UTC. Newer versions may differ and were not tested by us.
{
"mcpServers": {
"tax-law-mcp": {
"command": "npx",
"args": [
"-y",
"tax-law-mcp@0.5.4"
]
}
}
}Tools listed
get_law, search_law, get_tsutatsu, list_tsutatsu, list_saiketsu, search_saiketsu, get_saiketsu
Quick config
{
"mcpServers": {
"tax-law-mcp": {
"command": "npx",
"args": [
"-y",
"tax-law-mcp"
]
}
}
}Add to config Opens the config generator with this server selected.
Setup
- Install. Run
npm install tax-law-mcp --ignore-scripts(Node v24.22.1). This is the exact command we ran on 2026-11-19 UTC. - Configure. Add the mcpServers entry below to your MCP client config.
- Verify. Restart the client and check that tools/list returns tools (7 in our test).
{
"mcpServers": {
"tax-law-mcp": {
"command": "npx",
"args": [
"-y",
"tax-law-mcp"
]
}
}
}Test history
- 2026-11-19 UTC: New
Related: Best finance and crypto MCP servers
FAQ
Is Tax Law MCP deprecated?
No. Tax Law MCP was not deprecated or archived when we last tested it on 2026-11-19 UTC.
What replaces Tax Law MCP?
Nothing; Tax Law MCP is not deprecated as of 2026-11-19 UTC.
Does Tax Law MCP need an API key?
No. It completed an MCP handshake with no credentials and listed 7 tools.
Embed the badge
Every tested server gets a free embeddable badge. It shows the current score and test date and expires after 90 days. Testing is free; payment never changes a score.