MCP servers › legal.merit › law
MCP server · registry snapshot 2026-11-03 · last tested 2026-11-03
legal.merit/law
Merit — Ukrainian Law & Registers — the publisher's title
by merit.legal · domain (the registry's namespace rule)Website ↗
50+ Ukrainian legal sources, 120+ tools: laws on any date, case law, courts, companies, sanctions. — the publisher's description
Summary
legal.merit/law is a remote MCP server listed in the official MCP registry at version 1.0.2, under the namespace of the domain merit.legal. On 2026-11-03 ProtocolProbe connected to it in read-only mode and read its inventory: 43 tools, 0 resources and 0 prompts.
Record checks
1 of 2 record checks met · 7 do not apply
- met: Registry entry is active and says how to run it
- not met: Source repository link opens
- not applicable: Repository is not archived
- not applicable: Code pushed to the repository in the 90 days before our check
- not applicable: Repository publishes a security policy (SECURITY.md)
- not applicable: Package names its licence with a standard (SPDX) identifier
- not applicable: The version the registry lists can be installed and is not withdrawn
- not applicable: npm package carries build provenance (attestation)
- not applicable: No known critical or high advisory in the package or its dependencies
- Not ranked by downloads: a remote server publishes no download figure
- Not ranked by stars: no public GitHub repository
From public records, not a safety rating. Each check with its reason
Operate this server? Correct a fact · README badge · Run the checks yourself
Key facts
- Runs
- remote (hosted by the publisher)
- Transport
- streamable HTTP
- Your own values
- none declared (not a guarantee)
- Sign-in
- none needed to open a session
- Tools
- 43
- Last tested
- 2026-11-03
Tool list size
16,124 tokens on Claude Opus 5.5
Added to every request that loads this server's tools (43 tools). Counted with Anthropic's token counter on 2026-11-03, from the tool list we read on 2026-11-03. Median across 25,738 counted servers: 2,858 tokens. How it is counted
How a client gets in
Connects without signing in
Read from the server's public metadata on 2026-11-03 (law.merit.legal), in our read-only connection; no tool was called. It may have changed since. How it is read
Tool list at the three APIs
Not sent yet for this version (1.0.2).
How fresh this is
- Live-tested
- yes, a real session (not a text-only review)
- Last tested
- 2026-11-03
- Mode
- read-only (no tool calls)
- Latest version
- 1.0.2, published 2026-11-03 (registry, as of the 2026-11-03 snapshot)
- First listed version
- 2026-11-03 (earliest version still in the registry; older removed versions would be earlier)
- Version history
- 3 versions listed, all on 2026-11-03; 3 in the 90 days before the 2026-11-03 snapshot.(versions still listed in the registry only)
Most recent 3 versions
1.0.2· 2026-11-031.0.1· 2026-11-031.0.0· 2026-11-03
- Registry data
- snapshot 2026-11-03
- Package and repository
- checked 2026-11-03
- Engine
- mcp-runtime-engine@0.1.0 · sdk@1.32.0
Dead or stale signals
None found in the records we hold
Looked for and not found: deprecated in the registry. Does not apply: listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.
Changes since the last refresh
New in the registry: not in the list of 2026-11-02, listed on 2026-11-03 with version 1.0.2 (published 2026-11-03).
Source: the official MCP Registry list on 2026-11-02 and on 2026-11-03.
What it is
What does this server offer?
Observed inventoryNone of its 43 tools are described as changing anything. For 43 the reading was uncertain, so no mark is shown.
- eu_sanctions__search
“Search the EU consolidated financial sanctions list (persons and enterprises) by name or alias.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs, 1 required
querystringrequired“Name, alias or exact ID number.”limitintegersubject_typestring“Restrict to 'person' or 'enterprise'.”
- ua_law__search
“Search Ukrainian legislation by free text and/or metadata filters.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
8 inputs
textstring“Free text over document titles.”statusinteger or array“Status id; see list_dict_values.”type_idinteger or array“Type id; see list_dict_values.”topicinteger or array“Topic id; see list_dict_values.”in_scopeboolean“Only legislation the corpus treats as in scope.”in_force_on_datestring“In force on this day.”limitintegeroffsetinteger
- ua_law__search_units
“Find provisions by their text: which articles, points or clauses say X.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
7 inputs, 1 required
textstringrequired“Words to find.”nregarray“Only these acts.”on_datestring“Text as published that day.”per_actinteger“Hits per act, 0: all (default 3; 1 act: all).”amending_actsboolean“False: no amending laws.”limitintegeroffsetinteger
- ua_law__get_document
“One act's card, by registration number.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs, 1 required
nregstringrequired“Registration number, e.g.”relationstring“A `relation_counts` name: list those acts, 50 a page.”offsetinteger
- ua_law__get_unit
“Metadata for one structural unit, addressed by its URN.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
urnstringrequired“Unit URN, from get_document_toc.”
- ua_law__get_unit_in_force
“Whether one unit was legally in force on a given date.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs, 2 required
urnstringrequired“Unit URN, from get_document_toc.”datestringrequired“Day to test.”
- ua_law__get_unit_fulltext
“Unit text, paged.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
4 inputs, 1 required
urnstringrequired“Unit URN, from get_document_toc.”cursorstring“A `next_cursor`.”max_charsinteger“Page size; 0: `parts` only.”parts_offsetinteger“Start of `parts`.”
- ua_law__get_units_fulltext
“Several units' text in one call: a norm and what it relies on.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs, 1 required
urnsarrayrequired“Unit URNs, answered in this order.”max_charsinteger“Page size; 0: `parts` only.”
- ua_law__get_unit_editions
“The editions on which one unit's text changed, and what changed it.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
4 inputs, 1 required
urnstringrequired“Unit URN, from get_document_toc.”from_datestring“Earliest edition, inclusive.”to_datestring“Latest edition, inclusive.”limitinteger“Editions to read text for, newest first.”
- ua_law__get_document_toc
“One document's units in reading order -- and the article resolver: `kind='article'` with `number='626'` returns that article alone, `urn` included.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
6 inputs, 1 required
nregstringrequired“Registration number, e.g.”edition_datestring“Edition id from a URN's @suffix.”kindstring“One unit kind: annex, article, chapter, clause, document, par_group, part, sub_clause, sub_point, subpart.”numberstring“Unit's printed number, e.g.”limitintegeroffsetinteger
- ua_edrsr__search
“Faceted full-text search over Ukrainian court decisions (ЄДРСР).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
15 inputs
qstring“Free-text query, in the user's own words.”court_codearray“Court codes.”category_codearray“Case-category codes.”judgment_codearray“Judgment-form codes; see list_dict_values.”exclude_judgment_codearray“Codes to drop; 5 is Ухвала, the procedural ruling.”justice_kindarray“Justice-kind codes.”instancearray“1 cassation, 2 appellate, 3 first instance.”statusarray“Decision status codes.”judgestring“Exact judge name; Cyrillic case is folded.”date_fromstring“Inclusive ISO date.”date_tostring“Inclusive ISO date.”resolution_deptharray“Document-level rollup: none, article, clause.”cited_dokidarray“Only decisions citing these ua_law document ids.”limitinteger“Max rows to return (0-200); 0 returns the count alone.”offsetinteger
- ua_edrsr__get_document
“One decision: its text, its citations, its structural parts.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
5 inputs, 1 required
doc_idintegerrequired“Document id.”sectionarray“Parts to return text for: preamble, reasoning (what the court found), operative (what it ordered).”offsetinteger“Characters to skip, for paging.”max_charsinteger“Cap on returned text characters; text_window.next_offset continues.”include_htmlboolean“Also return canonical HTML (tables, emphasis, superscripts the text flattens).”
Show 31 more tools
- ua_edrsr__get_court_practice
“Court practice on one statute article: which cases cite it, by court and year, ranked highest authority first.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
5 inputs, 2 required
abbreviationstringrequired“Code abbreviation (ККУ), or act nreg or title.”article_numberstringrequired“Article number as written, e.g.”clause_componentstring“Частина/пункт; narrows to clause-depth citations.”limitinteger“Max rows to return (0-200); 0 returns the count alone.”facet_sizeinteger“Max facet buckets to return (1-1000).”
- ua_edrsr__lookup_case
“One case by document id or case number, with the cases related to it.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
6 inputs
doc_idinteger“Document id.”cause_numstring“Case number.”related_limitinteger“Max rows to return (0-200); 0 returns the count alone.”match_limitinteger“Max decisions per case to return (1-25).”max_charsinteger“Cap on response characters; related-case evidence fits it.”offsetinteger
- ua_bankruptcy__search
“Ukrainian bankruptcy and insolvency announcements (ДСА registry).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
7 inputs
querystring“Debtor name, matched anywhere in the string.”debtor_codestring“Exact ЄДРПОУ (company) or РНОКПП (individual).”case_numberstring“Exact case number.”announcement_typestring“Exact announcement type, in Ukrainian.”courtstring“Court name fragment.”limitintegeroffsetinteger
- ua_bankruptcy__get_case
“One bankruptcy case's announcement history and current procedural stage, newest first.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs, 1 required
case_numberstringrequired“Exact case number, slashes included.”limitinteger
- ua_cpi_inflation__lookup
“One consumer price index figure by period.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs, 1 required
periodstringrequired“ISO period: 2026-07 or 2025.”base_periodstring“Derzhstat BASE_PERIOD code, e.g.”freqstring“'M' monthly or 'A' annual.”
- ua_debtors__search
“Ukraine's Unified Register of Debtors (Єдиний реєстр боржників, ЄРБ): persons with an open, unsatisfied enforcement proceeding.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
6 inputs
qstring“Word search over debtor name, code and proceeding number.”debtor_codestring“Exact ЄДРПОУ or РНОКПП.”debtor_kindstring“фізична особа, юридична особа or невідомо.”categorystring“Exact claim category.”limitintegeroffsetinteger
- ua_debtors__lookup
“Every debtor listed under one enforcement-proceeding number.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
proceeding_numberstringrequired“Enforcement-proceeding number, e.g.”
- ua_edr_companies__search
“Ukrainian legal entities in the open ЄДР extract (Єдиний державний реєстр юридичних осіб).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
4 inputs
qstring“Free text over the ЄДРПОУ code and the names.”statusstring“Canonical registration status.”limitintegeroffsetinteger
- ua_edr_companies__lookup
“One legal entity by ЄДРПОУ code or `record`, with its people.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
4 inputs
edrpoustring“ЄДРПОУ code, e.g.”recordinteger“ЄДР subject id, from a hit.”historyboolean“Add the change log.”on_datestring“Add people as of this date.”
- ua_edr_companies__search_fop
“ФОП (фізичні особи-підприємці) in the open ЄДР extract, by name (ПІБ), status and registration/termination date.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
8 inputs
qstring“Words of the ПІБ; each a prefix, all required.”statusstring“Canonical registration status.”registered_fromstring“YYYY-MM-DD, inclusive.”registered_tostringterminated_fromstringterminated_tostringlimitintegeroffsetinteger
- ua_edr_companies__lookup_fop
“One ФОП by `record`: termination entry and reason, annulled termination, farm-household flag, property manager, tax/ЄСВ registration.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs, 1 required
recordintegerrequired“ЄДР subject id, from a search_fop hit.”historyboolean“Add the change log.”
- ua_enforcement_proceedings__search
“АСВП, Ukraine's register of enforcement proceedings (виконавчі провадження).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
8 inputs
qstring“Prefix of the debtor's name.”vp_numstring“Exact proceeding number.”debtor_codestring“Exact ЄДРПОУ; legal entities only.”proceeding_statestring“Exact state string as published.”opened_fromstring“Inclusive ISO date.”opened_tostring“Inclusive ISO date.”limitintegeroffsetinteger
- ua_enforcement_proceedings__lookup
“Every row published under one enforcement-proceeding number.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
vp_numstringrequired“Proceeding number, e.g.”
- ofac_sanctions__search
“Search the US Treasury OFAC Specially Designated Nationals (SDN) list (individuals, entities, vessels, and aircraft) by name or alias.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs, 1 required
querystringrequired“Name, alias or exact ID number.”limitintegersubject_typestring“Restrict to 'individual', 'entity', 'vessel', or 'aircraft'.”
- un_sanctions__search
“Search the UN Security Council Consolidated Sanctions List (individuals and entities) by name or alias.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
4 inputs, 1 required
querystringrequired“Name, alias or exact ID number.”limitintegerun_list_typestring“Restrict to a UN sanctions regime, e.g.”record_typestring“Restrict to 'individual' or 'entity'.”
- uk_sanctions__search
“Search the UK Sanctions List (HM Treasury / FCDO consolidated financial sanctions designations) by name or alias.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs, 1 required
querystringrequired“Name, alias or exact ID number.”limitintegerregimestring“Restrict to designations under this regime name.”
- ua_echr__search
“Search ECHR (European Court of Human Rights) case law via HUDOC, scoped to cases against Ukraine: judgments, decisions and communicated cases with application number(s), engaged articles, importance …”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
5 inputs, 1 required
querystringrequired“Words from the case name or judgment text.”articlestring“Restrict to a Convention article, e.g.”languagestring“Restrict to 'ENG' or 'UKR'.”limitintegerstartinteger“Offset into the result set.”
- ua_echr__get_case
“One HUDOC document by `itemid`, adding cited Strasbourg case law, domestic law at issue, judges.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
1 input, 1 required
itemidstringrequired“HUDOC item id from a search hit, e.g.”
- ua_corruption_registry__search
“Ukraine's register of persons who committed corruption or corruption-related offences (НАЗК).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
7 inputs
qstring“Free text over name, offence, article, court and case.”entity_typestring“Фізична особа or Юридична особа.”punishment_typestring“Судове рішення or Дисциплінарне стягнення.”date_fromstring“Inclusive ISO date.”date_tostring“Inclusive ISO date.”limitintegeroffsetinteger
- ua_nbu_rate__rate
“Look up the National Bank of Ukraine's official exchange rate (UAH per unit) for a currency, as of a given date or today if none is given.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
2 inputs, 1 required
currencystringrequired“ISO 4217 alphabetic code, e.g.”datestring“YYYY-MM-DD.”
- ua_court_hearings__search
“Hearings scheduled in Ukrainian courts (Список справ, призначених до розгляду), every court, read daily from court.gov.ua (a court listing on its own portal instead: source=courtportal).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
8 inputs
case_numberstring“Exact case number, e.g.”court_codestring“EDRSR court code, e.g.”qstring“Words in parties, subject or judge.”date_fromstring“On or after.”date_tostring“On or before.”include_removedboolean“Also hearings dropped before their date (moved/cancelled).”limitintegeroffsetinteger
- ua_vs_digest__search
“The Supreme Court's analytical publications: дайджести, огляди and узагальнення судової практики, plus the наукові висновки НКР при ВС.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
8 inputs
qstring“Free text over title and full document text.”court_bodystring“vp_vs, kgs, kcs, kks, kas, echr or vs.”doc_kindstring“digest, review, generalization, nkr_opinion or publication.”sectionstring“case_law, commentary or nkr.”year_frominteger“Earliest period year, inclusive.”year_tointeger“Latest period year, inclusive.”limitintegeroffsetinteger
- ua_vs_digest__document
“One Supreme Court publication's extracted text, `document_url`, cited case numbers and linked ЄДРСР `edrsr_ids` -- only this tool returns them.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
4 inputs, 1 required
document_idstringrequired“From a search result.”text_offsetinteger“0-based character offset into the text.”text_limitinteger“Characters to return.”text_querystring“Open the window at this term, searching from `text_offset`; pass the last window's end for the next hit.”
- ua_holidays__check_date
“Whether one date is a public holiday or non-working day in Ukraine.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
datestringrequired“ISO date, YYYY-MM-DD.”
- ua_lpd__search
“The Supreme Court's legal positions (правові позиції).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
9 inputs
qstring“Words over the position's title and text; each must occur, any order or form.”jurisdictionstring“kas, kks, kcs, kgs or vp (Grand Chamber).”category_idinteger“Classifier node; matches its whole subtree.”case_numberstring“Case number, e.g.”doc_idinteger“ЄДРСР document id.”court_codeinteger or array“ЄДРСР court codes of the decisions a position cites, OR-ed: 9911 КГС, 9921 КАС, 9931 КЦС, 9941 ККС, 9951 Велика Палата.”full_textboolean“Carry every hit's position text (off by default).”limitintegeroffsetinteger
- ua_lpd__position
“One legal position, with its text and published markup.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
position_idintegerrequired“From a search result.”
- ua_legal_indicators__get
“Value of a legal indicator in force on a date, with the act and article that set it.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs, 1 required
indicatorstringrequired“Indicator name, see the tool description.”on_datestring“Default today (Kyiv).”
- ua_legal_indicators__court_fee
“Судовий збір for a claim, or an appeal/cassation against the judgment, in a civil, commercial or administrative court (ст.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
7 inputs, 3 required
courtstringrequired“civil | commercial | administrative.”claim_kindstringrequired“property | non_property.”filerstringrequired“legal_entity | individual | fop | authority (administrative).”filingstring“claim | appeal | cassation.”claim_amountnumber“UAH; required for property claims.”filing_datestring“Picks the year's base.”electronicboolean“Filed electronically (×0.8).”
- catalog__search
“Find tools left out of this list (the catalog) by topic.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs
qstring“Words to find in tool names and descriptions, e.g.”sourcestring“Only this source's tools, e.g.”
- catalog__describe
“A catalog tool's full description and input schema, as tools/list would publish it.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
toolstringrequired“Tool name, from catalog__search.”
- catalog__call
“Run a catalog tool with its arguments.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
2 inputs, 1 required
toolstringrequired“Tool name, from catalog__search.”argumentsobject“That tool's arguments, per catalog__describe.”
Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-11-03.
How well are its tools described?
Features #4 and #5
How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.
Descriptions
AI reading of each description
No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).
Counted from the listing
- Parameters with a description
- 81% of 187
- Tools with a description
- 100% of 43
- Typical description length
- 385 characters
The tool set
Counted from the listing
- Tools
- 43
- Size of the list
- about 12,186 tokens for an agent to load (characters ÷ 4)
- Naming
- 43 of 43 names use mixed or other styles
AI reading: easy to mix up
No pair found.
The AI items cover 0 of 43 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none, comparing tools within groups of 40. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.
How do I add it to my client?
Config from the registry entry
From the remote endpoint (Streamable HTTP)
We connected to this URL on 2026-11-03 (a read-only session: no tool was called).
Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.
Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste: https://law.merit.legal/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
"mcpServers": {
"law": {
"url": "https://law.merit.legal/mcp"
}
}
}VS Code · .vscode/mcp.json
{
"servers": {
"law": {
"type": "http",
"url": "https://law.merit.legal/mcp"
}
}
}VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"law","type":"http","url":"https://law.merit.legal/mcp"}'Claude Code
claude mcp add --transport http law https://law.merit.legal/mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
"mcpServers": {
"law": {
"type": "streamableHttp",
"url": "https://law.merit.legal/mcp",
"disabled": false,
"autoApprove": []
}
}
}Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
"mcpServers": {
"law": {
"httpUrl": "https://law.merit.legal/mcp"
}
}
}OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.law] url = "https://law.merit.legal/mcp"
Zed · Zed settings file (command: zed: open settings file)
{
"context_servers": {
"law": {
"url": "https://law.merit.legal/mcp"
}
}
}Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://law.merit.legal/mcp --transport http
- The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
- Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
- The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.
Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.
Does the registry listing match what we found?
Feature #6The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.
| Registry says | We found | Result | Source · date |
|---|---|---|---|
| Remote endpoint law.merit.legal/mcp | Session opened | matches | our test · 2026-11-03 |
| No credential declared as required | Opened a session without any credential | matches | our test · 2026-11-03 |
Choosing
Record checks
Public records · not a safety rating1 of 2 record checks met · 7 do not apply
- Not ranked by downloads: a remote server publishes no download figure
- Not ranked by stars: no public GitHub repository
- MetRegistry entry is active and says how to run itActive, with a package or a remote address.
- Not metSource repository link opensThe registry entry gives no repository link.What changes this check: This check opens the repository link in the registry entry. GitHub's documentation describes changing a repository's visibility in its Settings, under Danger Zone, Change visibility. GitHub: setting repository visibility
- Does not applyRepository is not archivedNo public GitHub repository to read.
- Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
- Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
- Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
- Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
- Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
- Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.
Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-03. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral
Common questions about legal.merit/law
Answered from the data aboveWho publishes legal.merit/law?
The registry ties the namespace legal.merit to the domain merit.legal; only its owner can publish under it. These are facts from the registry and GitHub, not a rating.
Does legal.merit/law need an API key or sign-in?
It opened a session without any credential on 2026-11-03. The registry entry declares no required credential; no declaration is not a guarantee.
Has legal.merit/law been security tested?
Partly. 3 of the 15 checks that apply to it were exercised. We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. ProtocolProbe publishes no security verdict for a named server.
Found this page useful?
Anonymous · no sign-inA quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.
Compare with another server
Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.
Security testing
What did we test, and what did we leave out?
18 checks · features #1, #2
Not probed (we call no server's tools)
We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. No security score is given; a check we did not run is never counted as passed.
- Inventory: exercised
- Hidden instructions: exercised
- Real execution: not run · our policy
- Secret leak: not run · nothing to check it against
- Internal addresses: not run · our policy
- Unconfirmed changes: not run · our policy
- Bad input: not run · our policy
- Model requests: not run · nothing to check it against
- Sensitive questions: not run · nothing to check it against
- Folder boundary: not run · our policy
- Log leaks: not run · nothing to check it against
- Hidden content: not run · nothing to check it against
- Fake assistant turns: not applicable
- Token passthrough: not applicable
- Token audience: not applicable
- Sign-in redirect: not run · our policy
- Consent handling: not testable from outside
- Sign-in metadata: exercised
3 exercised12 not run (reason given)3 not applicable
Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 3 of the 15 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.
- 1Inventory
tool-listReads the declared tools, resources and prompts.exercised - 2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised - 18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.exercised
- 3Real execution
real-executionCalls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 12Hidden content
audience-hidingChecks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against - 16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy - 17Consent handling
confused-deputyChecks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
- 13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable - 14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable - 15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable
Source: our own test, 2026-11-03, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.
What happened during the test?
Feature #8
The steps in order, as the test record holds them.
- 0 msStarted a read-only session with the server's remote endpoint
- 1,370 msConnected after 0 redirects. No credential was sent or needed.
- Read the inventory: 43 tools, 0 resources, 0 prompts.
- 4,930 msFinished: 3 checks exercised.
Reference
How is it classified?
18 fields
One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.
“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.
Cite or correct this page
Sources and corrections
Suggested citation
ProtocolProbe. “legal.merit/law: MCP server record.” Data checked 2026-11-03. https://protocolprobe.com/mcp/servers/legal.merit/law
Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.
As JSON: this record in the API · API documentation.
Badge for your README
[](https://protocolprobe.com/mcp/servers/legal.merit/law)
It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.
Something wrong, or is this yours?
If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.
Write to hello@protocolprobe.com · corrections log · methodology