# @jackgillen15-dev/scope-mcp

Scope MCP server - dispatch litigation work to legal-services vendors from any MCP-compatible AI workflow.

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the package rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 0.1.1
- **Author:** Jack Gillen
- **License:** MIT
- **npm:** @jackgillen15-dev/scope-mcp
- **Source:** https://github.com/scope-bid/scope-mcp
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

60/100 (B), scored on the package rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 11 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-08-31T05:28:13.676Z
- **Version scanned:** 0.1.1
- **CVEs:** none found by OSV at scan time

## Tools

5 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `scope_list_categories` — 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 (a
- `scope_list_vendors` — List Scope-verified vendors. Each result includes verified-reputation metrics (on-time %, budget variance, rework rate, completed matters, satisfaction) and cre
- `scope_dispatch_matter` — 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 (def
- `scope_get_matter` — 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 
- `scope_list_matters` — List matters in flight for the calling buyer organization. Useful for status sweeps and pipeline reporting from inside an AI workflow.

## Install

**Verdict: review** — Installable, but 1 thing to check first: No publisher has proved control of this listing; it is indexed, not vouched for.
**Cautions** (coverage gaps and advisories — never blocking)
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"scope\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"@jackgillen15-dev/scope-mcp\"\n      ],\n      \"env\": {\n        \"SCOPE_API_TOKEN\": \"<YOUR_SCOPE_API_TOKEN>\"\n      }\n    }\n  }\n}"
```
**Credentials it will ask for** (names only — Forge never holds a value):
- `SCOPE_API_TOKEN` — Scope API Token (optional)
Placeholders only. Forge never holds, brokers, or transmits a credential value — replace each <YOUR_NAME> in your own config file. Do not send a value back to Forge; no Forge endpoint accepts one.
- This entry needs 1 credential (0 required). The generated config carries placeholders, so it will fail in the editor rather than at runtime if they are left unset.

## Blast radius

Moderate blast radius — holds an api key; runs on your machine.
- Floor 23, ceiling 23 (tier: moderate)
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/%40jackgillen15-dev%2Fscope-mcp
- Install plan: https://forgeregistry.com/api/v1/packages/%40jackgillen15-dev%2Fscope-mcp/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/%40jackgillen15-dev%2Fscope-mcp
- HTML page: https://forgeregistry.com/registry/%40jackgillen15-dev%2Fscope-mcp
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.