Scope (Legal)

Server Details

Dispatch litigation work to legal-services vendors from any MCP-compatible AI workflow.

Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status: Unhealthy
Uptime: 0.0% over 38 days
OAuth: Works in Glama
Last Tested: 2026-09-24 02:47
Transport: Streamable HTTP
URL
Repository: scope-bid/scope-mcp
GitHub Stars: 1
Server Listing: scope-mcp

TDQS

A3.9/5.0

Scored 2026-06-30 22:50 across 35 tools

Disambiguation5/5

Each tool has a clearly distinct purpose, covering different stages of the legal vendor workflow: listing, dispatch, award, declarations, deliverables, health, etc. Overlaps are minimal and clarified by descriptions.

Naming Consistency4/5

Most tools follow a consistent verb_noun pattern (e.g., scope_list_matters, scope_get_matter). Some exceptions like scope_briefing and scope_credential_alerts are noun-like, and the swp_ group uses verbs except swp_session_status. Overall pattern is clear.

Tool Count3/5

With 35 tools, the set is large but covers a comprehensive legal dispatch ecosystem. While each tool seems justified, the count exceeds the typical 15-tool sweet spot, making it heavy for an agent to navigate.

Completeness4/5

The tool set covers the full lifecycle: vendor discovery, roster management, dispatch, negotiation (swp), proof of service, declarations, deliverables, spend, and health. Minor gaps like cancellation of matters or full billing flow are roadmap items.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

1 tool updateJul 17, 2026

Changedscope_set_vendor_tier3 fields changed

addedInput schema / properties / vendor_name

Added value: +{
+  "description": "Vendor name as the user said it (e.g. 'Capitol Reporters'). Resolved server-side; ambiguous names return candidates.",
+  "type": "string"
+}

changedInput schema / properties / vendor_org_id / description

Previous value: -"UUID of the vendor organization. Use scope_list_vendors to discover."New value: +"UUID of the vendor organization. Use scope_list_vendors to discover, or pass vendor_name instead."

changedInput schema / required

Previous value: -[
-  "vendor_org_id",
-  "tier"
-]New value: +[
+  "tier"
+]

1 tool updateJul 14, 2026

Changedscope_dispatch_matter1 field changed

changedInput schema / properties / matter_specific_approval_required / description

Previous value: -"When true, every dispatch on this matter requires approval regardless of firm-wide policy. WP2 Tier 3 rule 8."New value: +"When true, every dispatch on this matter requires approval regardless of firm-wide policy."

3 tool updatesJul 13, 2026

Changedscope_dispatch_matter4 fields changed

addedInput schema / properties / documents

Added value: +{
+  "description": "Work-order documents the user pasted or attached in chat (the papers to serve, the signed authorization). Stored on the matter for the vendor at award. If the user cannot attach documents here, dispatch anyway: the award proceeds with documents pending and returns a secure upload link.",
+  "items": {
+    "properties": {
+      "content_base64": {
+        "description": "Base64 file content (when the surface supports attachments).",
+        "type": "string"
+      },
+      "content_text": {
+        "description": "Pasted document text.",
+        "type": "string"
+      },
+      "content_type": {
+        "type": "string"
+      },
+      "file_name": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "file_name"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedInput schema / properties / form_field_values

Added value: +{
+  "additionalProperties": true,
+  "description": "Structured work-order intake fields, keyed per category. Process serving: party_to_serve, service_address, deadline_semantics ('on' | 'by'), rush (boolean), affidavit_filing (boolean). Records retrieval: subject_name, provider_name, provider_location, record_types, date_range. Depositions: location, case_caption, proceeding_date. Required at award; quotes compute without them.",
+  "type": "object"
+}

addedInput schema / properties / matter_id

Added value: +{
+  "description": "Re-dispatch an EXISTING matter after collecting missing work-order fields. Set this to the scope_id from an incomplete_intake response; the collected form_field_values and documents merge onto that matter and the award re-runs. Omit to create a new matter.",
+  "type": "string"
+}

addedInput schema / properties / timeline_deadline

Added value: +{
+  "description": "Hard deadline for the work (ISO date). For process serving this is the service deadline; pair it with form_field_values.deadline_semantics ('on' or 'by').",
+  "type": "string"
+}

Addedscope_get_messages
Addedscope_send_message

5 tool updatesJun 30, 2026
- Addedscope_generate_declaration
- Addedscope_get_declaration
- Addedscope_get_service_proof
- Addedscope_log_service_attempt
- Addedscope_sign_declaration

1 tool updateJun 12, 2026

Changedscope_dispatch_matter1 field changed

addedInput schema / properties / reporter_type

Added value: +{
+  "description": "Court-reporting categories only. Restricts the dispatch to vendors staffing this reporter type. Omit for the default: all qualified reporter types quote. Intake text trigger phrases like 'stenographer only' set this automatically.",
+  "enum": [
+    "stenographer",
+    "digital",
+    "voice"
+  ],
+  "type": "string"
+}

1 tool updateJun 5, 2026

Changedscope_spend_rollup3 fields changed

addedInput schema / properties / client_id

Added value: +{
+  "description": "Optional. Restrict the rollup to a single client (e.g. spend for one carrier). UUID of a clients row.",
+  "type": "string"
+}

changedInput schema / properties / group_by / description

Previous value: -"Aggregation dimension."New value: +"Aggregation dimension. Use 'client' to break spend out by the firm's client (carrier, corporate, individual, or internal)."

changedInput schema / properties / group_by / enum

Previous value: -[
-  "vendor",
-  "category",
-  "matter_type",
-  "jurisdiction",
-  "scope"
-]New value: +[
+  "vendor",
+  "category",
+  "matter_type",
+  "jurisdiction",
+  "scope",
+  "client"
+]

17 tool updatesMay 29, 2026

Changedscope_briefing1 field changed