Scotcourts
NPM · @PIPEWORX/MCP-SCOTCOURTS · 2 COMPONENTS
Scottish Courts and Tribunals Service (SCTS) — judgment search.
Available components
Last scanned (8 hours ago)
Scores higher than 58% 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 & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-scotcourts). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability58
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 707 tokens (~353/item across 2 items; 2 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 Management0
- Stability observed for 0 of 30 days with no destabilising changes; credit accrues until the full window elapses.Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 5 Nov 26 78
First indexed and scored.
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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-scotcourts@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-scotcourts |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-scotcourts/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3692338356 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:83105d10c796b9b659f3f7138e0f580d32d11441e555995bc9a8ab850bb84af0e89083f967a2df7a14e05d7896ff291bb043e0e27235e21ffca2c1717 |
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 →
get_scottish_judgment ~217
Resolve a Scottish Courts judgment PDF and confirm it is actually reachable. Pass document_link exactly as returned by search_scottish_judgments (a relative /media/... path or absolute URL), or a case name / citation to look one up first. SCTS judgments are PDF-only — this tool returns the verified PDF URL, HTTP status, content-type and size, and text_extracted: false; it does NOT extract or return the judgment text (no PDF-text pipeline exists in this catalog). Fetch pdf_url to read the actual judgment.
| Name | Type | Req | Description |
|---|---|---|---|
| document_link | string | – | The documentLink / document_link value from search_scottish_judgments, e.g. "/media/id5nvoe1/court-of-session-judgement-appeal-by-sca-against-mma-27-october-2020.pdf". |
| query | string | – | Alternative to document_link: a case name or distinctive phrase to look up the judgment by, if you do not already have its document_link. |
No output schema declared.
No examples provided.
search_scottish_judgments ~434
Search Scottish court and tribunal judgments from the Scottish Courts and Tribunals Service (SCTS), published at scotcourts.gov.uk/judgments/ from 1999 onward: Court of Session, High Court of Justiciary, the National Personal Injury Court, Sheriff Appeal Courts, Sheriff Court civil/criminal, and the Scottish Upper Tribunal chambers. Returns title, court, judges, date and a document_link to the judgment PDF (fetch it with get_scottish_judgment). The `total` field is the true corpus match count (pagination.count.total upstream) — it is not the number of rows in this response, which is capped by `limit`. Coverage is whatever SCTS itself has chosen to publish on this index, not every decision ever made — sheriff court and tribunal coverage in particular is thin next to the higher courts. This is SCOTS law; England & Wales, UK Supreme Court and UK tribunal decisions are a different corpus (search_uk_caselaw).
| Name | Type | Req | Description |
|---|---|---|---|
| court | string | – | Court or Chamber to narrow to. Must match one of: Court of Session, High Court of Justiciary, National Personal Injury Court, Sheriff Appeal Court Civil, Sheriff Appeal Court Criminal, Sheriff Court… |
| from_date | string | – | Earliest date of opinion/decision, YYYY-MM-DD. |
| limit | number | – | Judgments per page, 1-50 (default 20). |
| page | number | – | Page number, 1-based (default 1). |
| query | string | – | Free-text search over the judgment (e.g. a party name, a distinctive phrase, "negligence"). Optional — omit to browse by court/date alone. |
| to_date | string | – | Latest date of opinion/decision, YYYY-MM-DD. |
No output schema declared.
No examples provided.
How do I install the Scotcourts MCP server?
Scotcourts runs locally as an npm package, launched with npx -y @pipeworx/mcp-scotcourts. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-scotcourts
claude mcp add pipeworx-io-scotcourts -- npx -y @pipeworx/mcp-scotcourts
What is the Scotcourts MCP server?
Scotcourts is an MCP server listed in the public MCP registry as io.github.pipeworx-io/scotcourts. Scottish Courts and Tribunals Service (SCTS), judgment search. This page covers its npm package (@pipeworx/mcp-scotcourts).
Is the Scotcourts MCP server safe to use?
Scotcourts scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Scotcourts MCP server expose?
Scotcourts exposes 2 tools: search_scottish_judgments, get_scottish_judgment. Their descriptions and schemas cost roughly 651 tokens of context every time the server is loaded.
Is the Scotcourts MCP server still maintained?
Scotcourts is still listed as active in the MCP registry. We last reached this channel on 5 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 Scotcourts MCP server under?
Scotcourts declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.