mcpdirectory.dev
9,129 servers · updated 23 Sept

Legal MCP server

community Active last commit 54 d
{
  "mcpServers": {
    "scope-legal": {
      "command": "npx",
      "args": [
        "-y",
        "@scope-bid/scope-mcp@latest"
      ],
      "env": {
        "SCOPE_API_TOKEN": "<scope_api_token>"
      }
    }
  }
}
file .mcp.json (in your project root)install npx -y @scope-bid/scope-mcpversion 1.0.9

What it does

Exposes tools to dispatch litigation work to credentialed legal vendors (court reporters, IMEs, experts, mediators, translation, and others) and receive bids within ten minutes. Designed for AI assistants in legal workflows that need vendor sourcing and vendor management.

  • Send a litigation matter to multiple vendors and receive competitive quotes in real time.
  • Maintain a roster of pre-vetted legal vendors and audit their credentials and performance.
  • Track spending across open matters and manage vendor tier assignments.

Tools this server exposes

ToolDoes
scope_dispatch_matterSend a matter to vendors and receive live quotes.
scope_briefingGet a daily briefing across all open matters.
scope_get_matterRetrieve details for a specific matter.
scope_list_mattersList all matters.
scope_list_categoriesList available service categories.
scope_list_vendorsList available vendors.
scope_list_rosterList vendors on your roster.
scope_set_vendor_tierAssign a vendor to a tier.
scope_remove_from_rosterRemove a vendor from your roster.
scope_award_matterAward a matter to a vendor.
scope_roster_auditAudit your vendor roster.
scope_vendor_healthCheck the health and status of a vendor.
scope_spend_rollupView spending across matters.
scope_credential_alertsReceive alerts about vendor credential changes.
swp_clarifyClarify terms in an existing negotiation session.
swp_acceptAccept terms in an existing negotiation session.
swp_rejectReject terms in an existing negotiation session.
swp_session_statusCheck the status of a negotiation session.

This entry comes from the registry but points to no public repository, so there is nothing to check: no commit history, no source, no tool list. It is listed for completeness and left out of search engines.

Before you enable it

An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.