MCP servers for legal work with required secrets
Of the 391 MCP servers in the measured field of use Legal work, 52 have required secrets declared – markedly fewer than the 86 the comparison group would lead one to expect.
52 servers 0.2% of 26,983 in the directory
This category in numbers
- 25 48 % Delivery form (raw): remote
- 27 52 % Execution location: local
- 39 75 % Repository URL listed: yes
- 39 75 % Repository platform (raw): github
The most frequent value per property, counted across the entries of this category. The full distribution is further down.
Entries
Filter further
- Execution location: local
- Execution location: remote
- Repository URL listed: yes
- Repository URL listed: no
- recently updated first
Entries 51 to 52 of 52
| mcp-trademarks | io.github.atomno-mcp/mcp-trademarks |
|---|---|
| pro.tvarka/due-diligence | pro.tvarka/due-diligence |
All 52 entries in the list, with filters and pagination
What this category selects
| Field of use, derived from the vendor description | Legal derived from: Description (raw) |
|---|---|
| Required secrets declared | yes derived from: Required secret variables (raw) |
A derived value carries its original data beside it; the derivation rule is published, with a version, on the methodology page.
Caveats, distribution and query
What this category does not say
- Field of use, derived from the vendor description is not declared but computed: from Description (raw). The rule is published, with a version, on the methodology page.
- Required secrets declared is not declared but computed: from Required secret variables (raw), Required secret headers (raw). The rule is published, with a version, on the methodology page.
What is measured is what a manifest declares, not what a piece of software does. This registry fetches no repository URL, no endpoint and no package index; nothing here is verified. Which value comes from which source, and by which rule it was formed, is set out in the Methodology.
Every sentence here follows from the condition above, not from an assessment.
How this category is distributed
Delivery form (raw)
52| remote | 25 48 % |
|---|---|
| package | 23 44 % |
| package and remote | 4 7.7 % |
Execution location
52| local | 27 52 % |
|---|---|
| remote | 25 48 % |
Repository URL listed
52| yes | 39 75 % |
|---|---|
| no | 13 25 % |
Repository platform (raw)
52| github | 39 75 % |
|---|---|
| nothing declared | 13 25 % |
Schema version of the raw record (raw)
52| https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json | 47 90 % |
|---|---|
| https://static.modelcontextprotocol.io/schemas/2025-09-29/server.schema.json | 3 5.8 % |
| https://static.modelcontextprotocol.io/schemas/2025-10-17/server.schema.json | 2 3.8 % |
Path argument present
52| no | 51 98 % |
|---|---|
| yes | 1 1.9 % |
Per property, the measured values inside this category. The share refers to the 52 entries of the category, not to the registry. Shown are 6 of 7 properties: those whose values spread the most inside this category.
The same category through the interface
curl -s "https://api.tracevero.com/v1/eintraege?art=mcp_server&einsatzgebiet=recht&zugangsdaten_erforderlich=true&grenze=200"
The command carries exactly the condition of this page. 52 entries at 200 each are a single request; the total is in the X-Gesamt header.
Changes to these entries
https://tracevero.com/aenderungen.atom?thema=einsatz-recht-mit-zugangsdaten
Both addresses narrow the change stream to exactly the entries in this category. The feed carries an identifier of its own, so a feed reader keeps it apart from the full stream.
Categories sharing entries with this one
Per neighbour its own size and the counted number of shared entries. An category without a single shared entry is not listed here.
tracevero · https://tracevero.com/themen/einsatz-recht-mit-zugangsdaten?seite=2