Scope (Legal)
bid.scope/legal · v1.0.5 · MCP 2025-11-25
Dispatch litigation work to legal-services vendors from any MCP-compatible AI workflow.
Reachability
reachable
checked 2026-07-14 03:06 UTC
Registry status active
Tools pinned 37
fede0d9d00ea
Tools last changed
unchanged since first capture 2026-07-14
Provenance
Registry namespace bid.scope
(domain verified by the official registry)
Repository
github.com/scope-bid/scope-mcp
Website
https://scope.bid/mcp/legal
Remote endpoints
https://scope.bid/api/mcp/legal (streamable-http)
Observed changes
| When (UTC) | Event | Detail |
|---|---|---|
| 2026-07-14 03:06 | first capture | 37 tools pinned |
Pinned tool definitions (37)
| Tool | Description |
|---|---|
| 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 (api_native) or are reached through Scope's ops-backed adapters (ops_backed). |
| scope_list_vendors | List Scope-verified vendors available for hire. Use this tool when the user wants to see, browse, or compare vendors they could hire for legal work. Specifically: court reporters, process servers, records firms, IMEs, expert witnesses,... |
| scope_dispatch_matter | Hire any human vendor for legal work, from inside the user's AI. Use this tool whenever the user needs to hire, find, book, get, or dispatch a legal-services vendor. Specifically: process servers, court reporters, records retrieval... |
| scope_get_matter | Look up a matter by its display id (e.g. SC-2041) or UUID. Returns scope details, instant rate-card quotes (rate_card model) or bids (legacy bid model), award status, deliverables, the conflict_check + approval state, and... |
| scope_list_matters | List the firm's matters and their dispatch status. Use this tool when the user asks about active or historical matters, dispatches, or pipeline. Specifically: open matters, awarded matters, in-progress work, completed matters, or... |
| scope_list_roster | List the calling buyer org's vendor roster. Returns each vendor with their tier (primary | backup | excluded), optional category scoping, notes, and lock window. Use to answer questions like 'who's on my roster for court reporting?' or... |
| scope_set_vendor_tier | Add or update a vendor on the buyer's roster. Use to set a vendor as primary, backup, or excluded - optionally scoped to a single service category. Examples: 'mark Capitol Reporters as primary for court reporting,' 'add MES Solutions to... |
| scope_remove_from_roster | Remove a vendor from the buyer's roster entirely. Use when the relationship has changed and you want to revert the vendor to neutral marketplace status (no priority routing, no exclusion). Requires authentication. |
| scope_award_matter | Award a dispatched matter to a chosen vendor. Locks the booking, notifies the vendor (push + email), and schedules a Stripe Connect invoice that fires when the matter completes (buyer review auto-accepts at 5 days). Returns a... |
| scope_reschedule_project | Reschedule an already-awarded project to a new date. Use only when the project is in an active engagement state (post-award, pre-delivery). Returns the confirmed new slot and whether the vendor was notified. Disallowed source states... |
| scope_briefing | Give the user a status briefing on their Scope vendor activity. Use this tool when the user asks what is happening, what changed, or wants a status update on their dispatches. Triggers include: 'what is happening on Scope', 'give me a... |
| scope_get_messages | Read the matter message thread between the firm and the awarded vendor. Use when the user asks whether the vendor has questions, sent an update, said anything, or needs anything - and ALWAYS check messages when reporting matter status,... |
| scope_send_message | Post a message on the matter thread to the awarded vendor. Use when the user wants to answer a vendor's question, relay an instruction, or send an update ('tell the server the gate code is 4482', 'let the reporter know the depo moved to... |
| scope_roster_audit | Complete activity log for a single scope. Returns the append-only event chain: dispatched, quotes received, awarded, accepted, calendar set, work completed, invoice paid. Useful for compliance review or matter-record export. |
| scope_spend_rollup | Show the firm's vendor spend, sliced by dimension. Use this tool when the user asks how much the firm has spent on vendors. Specifically: spend by vendor, by service category, by matter type, by jurisdiction, by client, by matter, or... |
| scope_vendor_health | Per-vendor credential, insurance, and on-time status across your roster. Returns COI / W-9 / insurance expiry, BAA status, 90-day on-time percentage, total awarded engagements, and an alerts list per vendor. |
| scope_credential_alerts | Vendors with expiring or expired credentials. Filtered version of scope_vendor_health. Use for compliance review or for the morning briefing's 'what needs attention' list. |
| scope_conflict_log | Search the buyer org's structured conflict-party log across every scope. Use for an OCG / Rule 1.7 prior-representation check before dispatching new work. Filter by party name (case-insensitive substring), optional party_type, and... |
| scope_get_dispatch_routing_state | Read-only view of the roster auto-routing state machine for one scope. Returns the current state (pending_primary, awaiting_primary_response, primary_accepted, primary_declined, primary_timed_out, opened_to_network, awarded, completed),... |
| scope_market_rate_compare | Show typical market pricing for a legal-services vendor category. Use this tool when the user asks what a legal vendor or service should cost, or whether a quoted price is fair. Specifically: process serving, court reporting, records... |
| scope_list_deliverables_for_scope | List vendor-uploaded deliverables for a scope. Returns each deliverable with type, vendor name, upload date, file size, notes, version, secure-link URL (works without login, expires in 7 days), and a short-lived signed download URL (1... |
| scope_get_deliverable | Fetch a single vendor-uploaded deliverable by id. Returns metadata + a short-lived signed download URL (1 hour TTL). The buyer's AI can hand the URL to a downstream analysis tool (transcript review, exhibit extraction, etc.) - Scope is... |
| scope_search_deliverables | Search the buyer org's deliverables by free-text query. v1 uses SQL ILIKE on notes + deliverable_type fields; full-text search (tsvector + GIN) is a follow-up. Optional scope_id narrows to a single scope; optional deliverable_type... |
| scope_send_deliverable | Ad-hoc re-send of an existing deliverable to additional recipients across one or more channels. Use when a lead attorney wants to forward a transcript, or to push a report to a CMS matter id, or to re-fan-out after fixing a typo in the... |
| scope_log_service_attempt | Log a single proof-of-service attempt (geo, photo, manner, recipient, outcome) on a matter as the assigned process server. Use this tool when the vendor reports that they tried to serve papers, completed a serve, or could not serve.... |
| scope_get_service_proof | Return the full proof-of-service trail for a matter: every logged attempt (with GPS, manner, recipient, outcome, timestamp) plus the attached photos. Use this tool when the firm wants to see, review, or verify proof that a vendor served... |
| scope_generate_declaration | Generate a DRAFT declaration / affidavit of service for a matter from the vendor's logged attempts, using the correct state template. The draft is editable; it is NOT signed. Use this tool when the vendor is ready to prepare their... |
| scope_get_declaration | Fetch a declaration / affidavit of service by id (draft or signed). Use this tool when the vendor or firm wants to read, review, or check the status of a declaration. Triggers include: 'show me the declaration', 'is the affidavit signed... |
| scope_sign_declaration | Sign a declaration / affidavit of service as the vendor who performed the service. This locks the declaration; it cannot be edited or re-signed afterward. Use this tool ONLY when the VENDOR who did the serve confirms the document is... |
| swp_propose | Submit an initial scope of work to a legal vendor for negotiation. Use when a user wants to engage a vendor for specific legal work but the spec may need vendor input to finalize. |
| swp_clarify | Vendor asks the buyer clarifying questions about a proposed scope. Use when the work spec is ambiguous or missing details a bid would depend on. |
| swp_refine | Buyer answers vendor clarifying questions and submits an updated work spec. |
| swp_bid | Vendor submits a bid against a proposed scope. Response envelope includes a gate descriptor when a human approval is required before the bid can be accepted. |
| swp_counter | Buyer counters a vendor bid with a new amount and updated terms. Vendor must re-bid with scope_bid for the session to advance. |
| swp_accept | Accept the current bid and move the session to ACCEPTED. If a human gate has not cleared, returns gate_pending with an approval URL. |
| swp_reject | Reject the current session. Terminal. Either party can call. Reason is a structured enum. |
| swp_session_status | Read-only. Returns current state, gate state, work spec, and current bid for a session. Caller must be a participant. |
Status badge
[](https://toolpin.dev/servers/bid.scope/legal)
Maintain this server? Add the badge to your README — it links your users to this live status page.