korean-tax-mcp@0.15.0
VERIFIED· not startedPublisher claims: "Korea (South Korea) tax law MCP server — NTS rulings, court and tax tribunal decisions, basic rules, tax treaties, point-in-time statutes. 한국 세법 근거 MCP" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
UPSTAGE_API_KEYConfiguration, not credentials: KOREAN_TAX_MCP_CACHE, KOREAN_TAX_MCP_CACHE_TTL, KOREAN_TAX_MCP_DOCS, KOREAN_TAX_MCP_MODEL, KOREAN_TAX_MCP_SOLAR_BASE_URL, KOREAN_TAX_MCP_SOLAR_KEY, KOREAN_TAX_MCP_SOLAR_VERIFY, KTM_CACHE_TTL, KTM_LAW_ARTICLE_BUDGET, KTM_RESP_MAX_CHARS, LAW_OC- Where it talks to
- no vendor host named in the codeAlso go.kr, doi.org, upstage.ai — not the publisher's domain; check what for before connecting.
- What the honeypot saw
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names go.kr, doi.org, upstage.ai as well as its own vendor. The guard injects UPSTAGE_API_KEY only into requests to the host you bind (and its subdomains) and refuses the rest.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-14 and scored it 94/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 2 scenarios · 0 deviationsStatic findings
monkeypatch.setenv("KOREAN_TAX_MCP_SOLAR_BASE_URL", "http://10.0.0.5:8000/v1/")Fix: Replace encoded or assembled strings with plain literals and remove undeclared network calls.monkeypatch.setenv("KOREAN_TAX_MCP_SOLAR_BASE_URL", "http://10.0.0.5/v1")Fix: Replace encoded or assembled strings with plain literals and remove undeclared network calls.assert base == "http://10.0.0.5:8000/v1" and onprem and solar.available() and key == ""Fix: Replace encoded or assembled strings with plain literals and remove undeclared network calls.- KOREAN_TAX_MCP_SOLAR_BASE_URL: 온프렘 Solar 주소(예: http://10.0.0.5:8000/v1). 없으면 https://api.upstage.ai/v1Fix: Replace encoded or assembled strings with plain literals and remove undeclared network calls.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
No advisories in OSV for korean-tax-mcp@0.15.0 as of 10 h ago. This is the package itself, not its dependencies.