Home / MCP registry index / com.valksor/hub
com.valksor/hub
com.valksor/hub in the official MCP registry.
Endpoint https://mcp.valksor.com/mcp.
The registry describes it as: One MCP endpoint over every Valksor dictionary: namespaced tools plus a JSON passthrough.
We read its 27 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
dictionaries livonian_search livonian_get_inflections livonian_romanize livonian_deromanize latin_search latin_get_inflections latin_lemmatize slavonic_search slavonic_get_inflections slavonic_transliterate slavonic_detransliterate scythian_search scythian_get_descendants norse_search norse_get_inflections latgalian_search latgalian_get_inflections latgalian_romanize latgalian_deromanize anglo_search anglo_get_inflections anglo_romanize anglo_deromanize interslavic_search interslavic_get_inflections interslavic_transliterate
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-valksor-hub)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.