Home / MCP registry index / legal.merit/law
Merit — Ukrainian Law & Registers
legal.merit/law in the official MCP registry.
Endpoint https://law.merit.legal/mcp.
The registry describes it as: 50+ Ukrainian legal sources, 120+ tools: laws on any date, case law, courts, companies, sanctions.
We read its 43 tools on 2026-11-03. 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 about every two weeks.
Connect it
The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:
claude mcp add --transport http law https://law.merit.legal/mcp{
"mcpServers": {
"law": {
"url": "https://law.merit.legal/mcp"
}
}
}code --add-mcp '{"name":"law","type":"http","url":"https://law.merit.legal/mcp"}'Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.
Let Claude Code check servers as it adds them
With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.
claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-pluginsTools it advertises
eu_sanctions__search ua_law__search ua_law__search_units ua_law__get_document ua_law__get_unit ua_law__get_unit_in_force ua_law__get_unit_fulltext ua_law__get_units_fulltext ua_law__get_unit_editions ua_law__get_document_toc ua_edrsr__search ua_edrsr__get_document ua_edrsr__get_court_practice ua_edrsr__lookup_case ua_bankruptcy__search ua_bankruptcy__get_case ua_cpi_inflation__lookup ua_debtors__search ua_debtors__lookup ua_edr_companies__search ua_edr_companies__lookup ua_edr_companies__search_fop ua_edr_companies__lookup_fop ua_enforcement_proceedings__search ua_enforcement_proceedings__lookup ofac_sanctions__search un_sanctions__search uk_sanctions__search ua_echr__search ua_echr__get_case ua_corruption_registry__search ua_nbu_rate__rate ua_court_hearings__search ua_vs_digest__search ua_vs_digest__document ua_holidays__check_date ua_lpd__search ua_lpd__position ua_legal_indicators__get ua_legal_indicators__court_fee catalog__search catalog__describe catalog__call
Tool changes
We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.
Fingerprint of its tools at our last full read (2026-11-03):
d9cd720f106412ba. A client can hash the tools it is served the same way and compare;
the full value and a hash per tool are in this page as JSON.
Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.
Run this server? Show the check in your README
The badge reflects the latest read: 
[](https://lazaretto.dev/mcp-registry/legal-merit-law)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. How tool poisoning works. What we found across the registry. Check another server.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.