stdict-mcp-server
Related Servers
Alternatives to stdict-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceProvides Korean Sign Language (KSL) data through MCP, enabling search and retrieval of sign language terms and details.MIT
- FlicenseAqualityDmaintenanceMCP 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.454-
- AlicenseNot gradedqualityCmaintenanceEnables full-text search and retrieval of Korean FSS/FSC accounting supervision and disclosure documents, including attachment bodies, summaries, and metadata, via a remote MCP server.MIT
- AlicenseAqualityCmaintenanceEnables 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
- AlicenseAqualityDmaintenanceMCP server to search and retrieve regulations from 14 Korean universities' regulation management systems. Supports querying, listing, and viewing full text or specific articles.411 npm2MIT
- FlicenseNot gradedqualityDmaintenanceMCP server for querying a database of 1 million Korean personas with full-text search, enabling AI agents to retrieve detailed demographic, professional, and personal profiles.24-
TDQS
Scored across 2 tools
The two tools target clearly different steps of a lookup workflow: search_dictionary finds headwords, while get_dictionary_entry retrieves full detail by headword or targetCode. There is no plausible way to confuse them, and the descriptions reinforce the dependency order.
Both names use a consistent snake_case verb_noun pattern (search_/get_ + dictionary resource). The convention is predictable and readable.
Two tools is on the thin side, though the search-then-retrieve pair is exactly the minimum needed for a lookup service. A small amount of additional surface (e.g. suggestions or sense listing) would make it feel less minimal.
The read-only lifecycle is fully covered: search to find headwords, then fetch definitions, parts of speech, and usage examples. Gaps are minor for a dictionary API (no fuzzy/spelling-suggestion or thesaurus navigation), and agents can work around them by re-searching.