taxlaw-mcp
Related Servers
Alternatives to taxlaw-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables searching and retrieving tax law data from the Korean National Tax Service database, including interpretations, rulings, forms, publications, and site menus via MCP tools.141MIT
- AlicenseAqualityBmaintenanceMCP server that directly queries the Korean National Tax Service tax law information system for tax law interpretations, precedents, and guidance. It supports exact document-number lookup, keyword search, and structured retrieval of ruling details and legal grounds.9MIT
- AlicenseNot gradedqualityDmaintenanceEnables searching and retrieving Korean statutes, precedents, and constitutional court decisions via MCP, using the National Law Information Center API.2,938 npm1MIT
- FlicenseAqualityCmaintenanceMCP server for Korean National Law Information. Enables searching and retrieving Korean laws, English-translated laws, administrative rules, court precedents, and constitutional decisions via 54 MCP tools.54-
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to retrieve current Korean tax statutes, judicial precedents, and tax authority interpretations via MCP, with daily-updated legislative history and full-text search.1MIT
- AlicenseBqualityCmaintenanceEnables deterministic research of Korean tax-law issues by retrieving and scoring official statutory evidence from law.go.kr and other legal sources, with citation verification and provenance, without deciding legal conclusions.8MIT
TDQS
Scored across 2 tools
The two tools have clearly distinct roles: one searches and returns metadata with IDs, the other retrieves the full text by ID. There is no overlap or ambiguity between them.
Both tool names follow the same verb_noun pattern: search_tax_interpretation and get_tax_interpretation. The naming is perfectly consistent and predictable.
With only two tools, the set is minimal and slightly below the typical 3-15 range, but it fits the server's narrow purpose well. The two tools form a complete search-then-fetch workflow without unnecessary extras.
The server fully covers its intended read-only domain: searching for tax interpretations and retrieving their full text. There are no obvious gaps or dead ends in the workflow.