Scope MCP server - dispatch litigation work to legal-services vendors from any MCP-compatible AI workflow.
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
SCOPE_API_TOKENAPI keyoptionalBearer token from scope-bid.vercel.app/settings. Required for write tools (scope_dispatch_matter). Read-only tools work without it on demo matters.
Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.
scope_list_categoriesList 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).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).
No input schema was published for this tool.
scope_list_vendorsList 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.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.
No input schema was published for this tool.
scope_dispatch_matterPost 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 depo…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 depo…
No input schema was published for this tool.
scope_get_matterLook 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.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.
No input schema was published for this tool.
scope_list_mattersList matters in flight for the calling buyer organization. Useful for status sweeps and pipeline reporting from inside an AI workflow.List matters in flight for the calling buyer organization. Useful for status sweeps and pipeline reporting from inside an AI workflow.
No input schema was published for this tool.
5 of 5 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
Scope MCP server - dispatch litigation work to legal-services vendors from any MCP-compatible AI workflow.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
The crawl stopped at the depth-4 limit. Anything below that level was never resolved.
The crawl stopped at the 60-package limit. The rest of the tree was never resolved.
36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)
54 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.
+42 more not listed. The counts by reason above cover all of them.
Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.