io.github.QuestLaw/questlaw-library
NPM · QUESTLAW-MCP
Access your QuestLaw library in GenAI Tools.
Available components
Last scanned (22 hours ago)
Scores higher than 62% of npm servers
Category Education and Research
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (GPL-3.0-or-later).Pass
- Actively maintained (last published 26 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1559 tokens (~155/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 97% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +4
- Stability: unverified → 0.27 ▲ functional
- 14 Oct 26 +29
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- MCP protocol: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 97 functional
- First check of Schema quality: excellent functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: fail functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed npm/questlaw-mcp@0.5.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
find_citation_mentions Check a draft against the library ~141
Given draft text, report every place it cites an authority already in the library, in order. Citations match in any spelling (603 U.S. 369 = 603 US 369), with or without a pincite or year, and a citation used twice is reported twice. Use it to check a draft against the research behind it -- and to find the citations in it that the library does not have.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max mentions, default 25, max 50. |
| offset | integer | – | Skip this many mentions; use the nextOffset from the previous call. |
| text | string | yes | Draft text to scan. |
No output schema declared.
No examples provided.
get_case Read one authority ~101
One authority in full: the user's notes and analysis, every saved quotation with its pincite, the projects it is filed under, how they connected it to other authorities (related), and any captured source text available for it. Search and list rows already carry a summary, so reach for this when you need the whole note, the quotations, or those connections -- not to identify a case.
| Name | Type | Req | Description |
|---|---|---|---|
| guid | string | yes | Case guid from a search or list result. |
No output schema declared.
No examples provided.
get_source_text Read captured source text ~243
The captured text of a statute, regulation, court rule, or opinion. Document ids come from get_case (capturedSources) or a search_library source hit. It does not have to arrive whole: outline lists the sections and their sizes, query returns only the sections matching it, maxChars caps how much text comes back, and offset pages through the rest. Reach for one of those first on an opinion -- a full one runs to tens of thousands of characters.
| Name | Type | Req | Description |
|---|---|---|---|
| documentId | string | yes | – |
| limit | integer | – | Max sections, default 50. |
| maxChars | integer | – | Cap the text returned across all sections; the last one is clipped and says so. An excerpt, rather than all-or-nothing. |
| offset | integer | – | First section to return, default 0. |
| outline | boolean | – | Structure only: every section's index, label, heading, and length, with no text. The cheapest way to find the part worth reading. |
| query | string | – | Return only the sections that match these words, most matching first. Use it for "the part about X" instead of reading the whole document. |
No output schema declared.
No examples provided.
library_overview What is in this library ~68
What this library contains: how many authorities, which projects, tags and courts they are filed under, how much captured source text there is, and how old the snapshot is. Call this first. It costs one call and tells you which of the other tools can actually reach what you are after.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_cases List authorities ~244
Every authority in the library, with no query and no filter required. This is how you enumerate the library: what is in here, how big is it, summarise all of it. Optionally narrow by project ("none" for the unfiled ones), court, or tag, and sort by title, recency, year, or quote count. Pages through offset, and every row carries a one-line summary drawn from the user's own notes.
| Name | Type | Req | Description |
|---|---|---|---|
| court | string | – | Keep only authorities whose court contains this text, case-insensitive. |
| limit | integer | – | Rows per call, default 25, max 50. |
| offset | integer | – | Skip this many rows; use the nextOffset from the previous call. |
| project | string|number | – | Project id or uid, or "none" for authorities filed under no project. Omit for all of them. |
| sort | string | – | title (default), recent (when it was saved), year (of decision), or quotes (how much language is saved from it). |
| tag | string | – | Keep only authorities carrying this exact tag, ignoring case. library_overview lists the tags. |
No output schema declared.
No examples provided.
list_project_cases List the authorities on a project ~109
Every authority filed under one project or matter. Project ids come from library_overview. Authorities filed under no project are unreachable here: use list_cases, with project "none" for exactly those.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Rows per call, default 25, max 50. |
| offset | integer | – | Skip this many rows; use the nextOffset from the previous call. |
| projectId | string|number | yes | Project id or uid. |
| sort | string | – | Default title. |
No output schema declared.
No examples provided.
reload_snapshot Re-read the export ~33
Re-read the newest export from disk. Use after the user exports a fresh backup, or to retry after a load failure.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_cases Search authorities ~283
Find saved authorities, ranked by relevance across title, citation, tags, notes, analysis, and quote text. Multi-word queries work; so do "quoted phrases", which are required rather than preferred. Citations match in any spelling (603 U.S. 369 = 603 US 369). Narrow by project, court, or tag rather than by putting a court name in the query. Each result carries a summary and the passage that matched, so you can usually judge relevance without calling get_case. Omit query to browse; page with offset. To walk the whole library, use list_cases.
| Name | Type | Req | Description |
|---|---|---|---|
| court | string | – | Keep only authorities whose court contains this text, e.g. "Ninth Circuit" or "Mass". Case-insensitive. |
| limit | integer | – | Max results, default 25, max 50. |
| offset | integer | – | Skip this many ranked results; use the nextOffset from the previous call. |
| project | string|number | – | Project id or uid to search within, or "none" for authorities filed under no project. |
| query | string | – | What to look for. Natural wording is fine. Omit it to browse instead of rank; wildcards are not supported and do nothing. |
| tag | string | – | Keep only authorities carrying this exact tag, ignoring case. library_overview lists the tags. |
No output schema declared.
No examples provided.
search_library Search everything ~195
One ranked search across everything: saved authorities, saved quotations, and the full captured text of statutes, regulations, rules, and opinions. Start here when you do not already know which of those holds the answer -- captured source text is reachable no other way except by a document id you would have to know in advance. One row per authority or captured document: its other matching quotations or sections are listed under the row as alsoMatched. Pages with offset. Omit query to browse what exists of each kind.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results, default 25, max 50. |
| offset | integer | – | Skip this many ranked results; use the nextOffset from the previous call. |
| query | string | – | What to look for. "Quoted phrases" are required verbatim. Optional: omitting it browses rather than ranks. |
| types | array | – | Restrict to these kinds. Default: all three. |
No output schema declared.
No examples provided.
search_quotes Search saved quotations ~142
Search the text of every saved quotation, ranked. Use this when the user wants language to quote rather than an authority to cite: each hit carries the passage, the authority it came from, and its pincite. Quote a phrase to require it verbatim. This searches only what the user chose to save; to search the full text of captured opinions and statutes, use search_library.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results, default 25, max 50. |
| offset | integer | – | Skip this many results; use the nextOffset from the previous call. |
| query | string | – | Language to find. Omit it to list every saved quotation instead. |
No output schema declared.
No examples provided.
How do I install the io.github.QuestLaw/questlaw-library MCP server?
io.github.QuestLaw/questlaw-library runs locally as an npm package, launched with npx -y questlaw-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · questlaw-mcp
claude mcp add questlaw-questlaw-library -- npx -y questlaw-mcp
What is the io.github.QuestLaw/questlaw-library MCP server?
io.github.QuestLaw/questlaw-library is an MCP server listed in the public MCP registry as io.github.QuestLaw/questlaw-library. Access your QuestLaw library in GenAI Tools. This page covers its npm package (questlaw-mcp).
Is the io.github.QuestLaw/questlaw-library MCP server safe to use?
io.github.QuestLaw/questlaw-library scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.QuestLaw/questlaw-library MCP server expose?
io.github.QuestLaw/questlaw-library exposes 10 tools: library_overview, list_cases, search_cases, get_case, search_quotes, and 5 more. Their descriptions and schemas cost roughly 1,559 tokens of context every time the server is loaded.
Is the io.github.QuestLaw/questlaw-library MCP server still maintained?
io.github.QuestLaw/questlaw-library is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.QuestLaw/questlaw-library MCP server under?
io.github.QuestLaw/questlaw-library declares the GPL-3.0-or-later licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.