Scope
NPM · @JACKGILLEN15-DEV/SCOPE-MCP · SCANNED AUG 7
Dispatch litigation work to legal-services vendors from any MCP-compatible AI workflow.
Available components
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 →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Known CVEs were checked across the 95 of 99 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Dependency health was assessed across the 95 of 99 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- 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 (MIT).Pass
- Actively maintained (last published 96 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 456 tokens (~91/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 13% of tool parameters carry a description.Partial
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @jackgillen15-dev/scope-mcp
claude mcp add jackgillen15-dev-scope-mcp -- npx -y @jackgillen15-dev/scope-mcp
codex mcp add jackgillen15-dev-scope-mcp -- npx -y @jackgillen15-dev/scope-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"jackgillen15-dev-scope-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@jackgillen15-dev/scope-mcp"
],
"enabled": true
}
}
} openclaw mcp add jackgillen15-dev-scope-mcp --command npx --arg -y --arg @jackgillen15-dev/scope-mcp
mcp_servers:
jackgillen15-dev-scope-mcp:
command: "npx"
args: ["-y", "@jackgillen15-dev/scope-mcp"] {
"mcpServers": {
"jackgillen15-dev-scope-mcp": {
"command": "npx",
"args": [
"-y",
"@jackgillen15-dev/scope-mcp"
]
}
}
} 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.
- 6 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Aug 26 +31
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Dependency health: unverified → partial ▲ functional
- Stability: unverified → 0.23 ▲ functional
- Schema quality: unverified → good ▲ functional
- License: unverified → pass ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Licence: MIT functional
- 1 Aug 26 +15
- Malware scan: unverified → pass ▲ security
- 31 Jul 26 −24
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 42
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 7 Aug 2026 · Analysed npm/@jackgillen15-dev/[email protected]
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Deprecated | 95 |
| Stale | 29 |
| Tree resolution | Partial |
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
scope_dispatch_matter ~175
Post a new sealed-bid matter to Scope. Returns the matter id and status. Vendors in the matching category are notified; bids close after bid_window_minutes (default 4 days). Requires SCOPE_API_TOKEN. Use this when an AI workflow needs to engage a vendor on behalf of a firm - for example when a deposition notice arrives, when records retrieval is needed, or when a social media preservation request is triggered.
| Name | Type | Req | Description |
|---|---|---|---|
| bid_window_minutes | integer | – | – |
| budget_max | number | – | – |
| budget_min | number | – | – |
| description | string | yes | – |
| jurisdictions | array | – | – |
| matter_type | string | yes | – |
| must_haves | array | – | – |
| service_category | string | yes | – |
| target_kickoff | string | – | – |
| title | string | yes | – |
No output schema declared.
No examples provided.
scope_get_matter ~71
Look up a matter by its display id (e.g. SC-2041) or UUID. Returns scope details, bids received, award status, and any deliverables. For sealed matters, vendor names are anonymized in returned bids until the matter is awarded.
| Name | Type | Req | Description |
|---|---|---|---|
| matter_id | string | yes | – |
No output schema declared.
No examples provided.
scope_list_categories ~56
List the legal-services categories Scope can dispatch matters to. Each category has a slug, human label, and an indicator of whether vendors expose REST APIs (api_native) or are reached through Scope's ops-backed adapters (ops_backed).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
scope_list_matters ~48
List matters in flight for the calling buyer organization. Useful for status sweeps and pipeline reporting from inside an AI workflow.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| status | string | – | – |
No output schema declared.
No examples provided.
scope_list_vendors ~106
List Scope-verified vendors. Each result includes verified-reputation metrics (on-time %, budget variance, rework rate, completed matters, satisfaction) and credentialing summary. Vendor names are returned only for verified callers; anonymous callers get anonymized labels.
| Name | Type | Req | Description |
|---|---|---|---|
| category_slug | string | – | Service category slug to filter by (e.g. 'court-reporting'). Omit for all. |
| jurisdiction | string | – | Federal district or state code. |
| limit | integer | – | – |
No output schema declared.
No examples provided.