Scope Legal MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to Scope legal-vendor procurement tools: Do rate-card quotes and human approval remain separate from binding legal-service engagements?

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Legal-services vendor procurement with published rate cards and mandatory human approval before commitments.

What we know

Open-source MCP/SDK layer over Scope's hosted legal-services marketplace. It can dispatch matters, get quotes/bids, manage rosters and award approved work; human approval is required before a commitment.

Maintenance / activity evidence

@scope-bid/scope-mcp 1.0.9 published 2026-07-30T23:03:45.699Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Legal vendor procurement/workflow authority. Writes: Dispatch matters; Negotiate/accept bids; Award work; Manage roster/vendor tiers.
Scope token for writes.
Sensitive access: Legal matter details, Professional/vendor data, Pricing/spend

Can create real legal-support commitments; mandatory human approval must be preserved.

Full authority, access and evidence limits are available in Review context and Access & risk.

All limitations / Review context

Do rate-card quotes and human approval remain separate from binding legal-service engagements?

The bounded review of the publisher's documented Scope legal-vendor procurement tools and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

Can create real legal-support commitments; mandatory human approval must be preserved.
Legal vendor procurement/workflow authority.
Scope token for writes.
Matter/vendor/pricing/document workflow data is processed by Scope and external professionals.
Reviewed write actions: Dispatch matters; Negotiate/accept bids; Award work; Manage roster/vendor tiers
Sensitive access: Legal matter details, Professional/vendor data, Pricing/spend
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
Limited-release marketplace with coverage varying by category/region.
Real dispatches create external professional-service commitments.
Human approval cannot be removed and is a core safety boundary.
Publisher lifecycle: limited release

Original activity observations

@scope-bid/scope-mcp 1.0.9 published 2026-07-30T23:03:45.699Z

Technical identity

npm/@scope-bid/scope-mcp

Exact implementation source: https://www.npmjs.com/package/@scope-bid/scope-mcp ↗
Reviewed resource type: MCP Server
Repository identity: scope-bid/scope-mcp
Package identity: npm:@scope-bid/scope-mcp
Service endpoint: https://scope.bid/api/mcp/legal

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 8, 2026

Package registry ↗
@scope-bid/scope-mcp
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.
Evidence source ↗
scope.bid/mcp
Source material retained for this review.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Warning

No third-party MCP installation, execution, connection, payment or mutation performed.
Official documentation may not prove currently operational service.
Package installation alone not a client connection.
SDK `npm install` is not proof of a runnable stdio server or a connected MCP client.
Targeted 2026-10-13 re-research: npm install gives SDK layer, not verified MCP launch; official scope.bid/install guide needed.
npm install gives SDK layer, not verified MCP launch; official scope.bid/install guide needed.
Vendor page shows limited release/vertical variants; avoid inventing cross-package launcher and production availability.
Batch08 V3 source-specific finding: Same publisher guide but distinct legal-services identity.
SDK distribution; no substantiated universal npx MCP registration; use publisher installation guide.
Recorded publisher instruction; runtime not tested.

Install / connect
Publisher instructions
npm package installation alone is not MCP client registration; publisher delegates client config to https://scope.bid/install. Without verified host-specific instructions, do not mark actionable-complete.
publisher documented install or connect · Publisher instructions
npm install @scope-bid/scope-mcp
Configure / authenticate
MCP100 setup guide
Publisher documentation for legal-services MCP: https://scope.bid/install. Keep separate from AEC and claims package identities.
Check connection
Suggested check
User-side suggested check (not executed): inspect registered tools/connection and perform publisher-supported read-only status/list operations. Do not send, purchase, publish, delete, sign, trade or alter data as a smoke test.
Remove / uninstall / revoke
MCP100 setup guide
Generic client guidance (not publisher-specific uninstall): unregister MCP entry in the chosen client. If installed globally, remove the npm package separately. Revoke provider access separately through account controls, where supported. This does not erase local data or revoke funds/credentials automatically.
Unregister the named MCP entry from the actual host separately from removing a global npm install; no claim that either revokes remote credentials.
Remove local stored keys/tokens and revoke or rotate corresponding provider authorization using documented provider account controls if available; exact procedure not verified for this package. Wallet private keys cannot be revoked.

Official Documentation & Sources

What it does

Open-source MCP/SDK layer over Scope's hosted legal-services marketplace. It can dispatch matters, get quotes/bids, manage rosters and award approved work; human approval is required before a commitment.

Capability: Productivity & Collaboration
Resource type: MCP Server
Industry: Legal & Compliance
Best fit: Legal-services vendor procurement with published rate cards and mandatory human approval before commitments.

Representative uses

Dispatch process serving/court reporting/records/expert work
Receive live vendor quotes
Manage vendor rosters
Track matters/spend/credentials
Award approved work

Limitations

Limited-release marketplace with coverage varying by category/region.
Real dispatches create external professional-service commitments.
Human approval cannot be removed and is a core safety boundary.
Publisher lifecycle: limited release

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Scope token for writes.
Permissions: Legal vendor procurement/workflow authority.
Data handling: Matter/vendor/pricing/document workflow data is processed by Scope and external professionals.
Cost: transactional
Risk and cautions: Can create real legal-support commitments; mandatory human approval must be preserved.

Access scope and cautions

Write actions: Dispatch matters Negotiate/accept bids Award work Manage roster/vendor tiers
Sensitive access: Legal matter details Professional/vendor data Pricing/spend
Risk level: high

FAQ

Based on reviewed evidence as of 2026-10-08. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Dispatch process serving/court reporting/records/expert work; Receive live vendor quotes; Manage vendor rosters; Track matters/spend/credentials; Award approved work.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx -y @scope-bid/scope-mcp. Recorded endpoint: https://scope.bid/api/mcp/legal. Recorded transport: stdio, streamable_http. Recorded environment-variable notes: SCOPE_API_TOKEN (writes); SCOPE_API_BASE (optional); SCOPE_ORG_SLUG (optional). No configuration values are supplied here. Prerequisites: MCP client; Scope firm/account for live work. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: Read-only demo may be keyless; writes use Scope auth/token. A demo or keyless description is not independently verified read-only authority. Check the documented tool permissions rather than inferring authority from that label.

Can it modify data or perform write operations?

Documented write actions include: Dispatch matters; Negotiate/accept bids; Award work; Manage roster/vendor tiers. Recorded permission boundary: Legal vendor procurement/workflow authority.

What data-handling boundary should I consider?

Matter/vendor/pricing/document workflow data is processed by Scope and external professionals. Recorded sensitive-access context: Legal matter details; Professional/vendor data; Pricing/spend.

What limitations and risks should I check before use?

Can create real legal-support commitments; mandatory human approval must be preserved. Limited-release marketplace with coverage varying by category/region. Real dispatches create external professional-service commitments. Human approval cannot be removed and is a core safety boundary. Publisher lifecycle: limited release. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.

What cost model is recorded?

The reviewed cost model is transactional. This classification does not establish current prices, quotas or the cost of every downstream operation. Check the applicable service terms before authorizing paid actions.