mcpField
S
Scope (Claims) - Preview

Scope (Claims) - Preview

Remote
scope.bidBusiness & Marketing1Updated 5d ago

About Scope (Claims) - Preview

Scope (Claims) is an MCP server for insurance claims teams to route work to credentialed professionals and retrieve prices based on their published rate cards. It covers services such as IMEs, surveillance, and medical record review.

Key features

  1. 01Route IME requests
  2. 02Coordinate surveillance
  3. 03Arrange medical record reviews
  4. 04Support life-care and vocational rehab
  5. 05Audit rosters and credentials

Use cases

  1. 01Find an IME provider for a claim
  2. 02Coordinate surveillance work
  3. 03Request defense medical record review

MCP support

Exposes claims dispatch and coordination tools to MCP clients, including roster audits and credential alerts. It can be used via an installed package or an HTTP endpoint.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://scope.bid/api/mcp/claims
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Packages
npm@scope-bid/scope-claims-mcp1.0.10

Tools

4

This tool takes no parameters.

Details

From the project README

@scope-bid/scope-mcp

Hire your next vendor through your AI.

Model Context Protocol servers for Scope.bid professional dispatch across legal, insurance claims, and AEC services.

scope.bid | MCP Registry | npm | Plugin marketplace


What this is

Three Model Context Protocol servers that let AI assistants dispatch requests to credentialed human professionals and get back each professional's price, computed from their own published rate card.

  • @scope-bid/scope-mcp - legal vertical (court reporters, IMEs, records, experts, e-discovery, translation, mediators, trial graphics, foreign-jurisdiction counsel, more)
  • @scope-bid/scope-claims-mcp - insurance claims (IMEs, surveillance, peer review, voc rehab, life-care plans, defense medical record review)
  • @scope-bid/scope-aec-mcp - AEC (subcontractor prequal, bonding, safety records, dispatch)

Scope.bid is the first vertical-services MCP platform on Anthropic's official Model Context Protocol Registry. Three namespaces are claimed under DNS-verified bid.scope/* (legal, claims, AEC). Two are reserved (healthcare, pharma).

Scope.bid is not affiliated with scope-bid.com, an unrelated laboratory equipment auction platform.

Install

npm install -g @scope-bid/scope-mcp
npm install -g @scope-bid/scope-claims-mcp
npm install -g @scope-bid/scope-aec-mcp

For most clients you do not need to install globally. Use npx -y @scope-bid/scope-mcp directly from your MCP client config.

Configure (Claude Desktop, Claude Code, Cursor)

{
  "mcpServers": {
    "scope-legal": {
      "command": "npx",
      "args": ["-y", "@scope-bid/scope-mcp"],
      "env": {
        "SCOPE_API_TOKEN": "your-token-here"
      }
    },
    "scope-claims": {
      "command": "npx",
      "args": ["-y", "@scope-bid/scope-claims-mcp"],
      "env": {
        "SCOPE_API_TOKEN": "your-token-here"
      }
    }
  }
}

For read-only demo usage the token is optional.

Or use HTTP transport (no install)

{
  "mcpServers": {
    "scope-legal": {
      "type": "http",
      "url": "https://scope.bid/api/mcp/legal",
      "headers": { "Authorization": "Bearer your-token-here" }
    }
  }
}

HTTP endpoints:

Tools

Legal (bid.scope/legal):

  • scope_dispatch_matter - send a matter to professionals and get their rate-card prices
  • scope_briefing - daily briefing across all open matters
  • scope_get_matter, scope_list_matters, scope_list_categories, scope_list_vendors, scope_list_roster
  • scope_set_vendor_tier, scope_remove_from_roster, scope_award_matter
  • scope_roster_audit, scope_vendor_health, scope_spend_rollup, scope_credential_alerts
  • swp_clarify, swp_accept, swp_reject, swp_session_status - Scope Work Protocol tools for existing negotiation sessions (the session-opening tools were retired at the rate-card cutover and are no longer served)

Claims (bid.scope/claims): IME routing, surveillance coordination, defense medical record review, life-care planning, voc rehab routing, roster audit, credential alerts.

AEC (bid.scope/aec): subcontractor dispatch, prequalification, bonding capacity, safety record pulls, AEC vendor listing.

Environment variables

  • SCOPE_API_BASE - override the default API base. Defaults to https://scope.bid.
  • SCOPE_API_TOKEN - bearer token for write operations.
  • SCOPE_ORG_SLUG - pin reads and writes to a specific buyer organization. Useful for multi-tenant deployments.

Plugin marketplace alternative

If you want bundled slash commands and skills along with the MCP server registration, install the plugin marketplace instead:

/plugin marketplace add github.com/scope-bid/scope-platform
/plugin install scope-legal

Evals

Five canonical scenarios protect against regressions in MCP tool behavior.

Run locally against mocks:

npm run eval

Run against the live Anthropic API with MCP tools attached:

npm run eval:live

Add a new scenario any time a tool or skill ships that creates a new failure mode. Fixtures live in tests/evals/fixtures/, mocked tool responses in tests/evals/mocks/, runner in tests/evals/runner.ts. CI runs the mocked harness on every PR via .github/workflows/eval.yml.

Version bumps

When updating package.json version in any package directory, also update the matching server.json version. CI auto-syncs as a safety net but committed files should stay aligned for repo hygiene and local-publish testing.

Company

Scope Bid, Inc. is a Delaware C-corp founded May 2026 by Jack Gillen. San Diego, CA. Patent pending.

LinkedIn: https://www.linkedin.com/company/scope-bid/

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.