Dispatch litigation work to legal-services vendors from any MCP-compatible AI workflow.
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
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.
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.
{
"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.
{
"mcpServers": {
"scope-legal": {
"type": "http",
"url": "https://scope.bid/api/mcp/legal",
"headers": { "Authorization": "Bearer your-token-here" }
}
}
}
HTTP endpoints:
Legal (bid.scope/legal):
scope_dispatch_matter - send a matter to professionals and get their rate-card pricesscope_briefing - daily briefing across all open mattersscope_get_matter, scope_list_matters, scope_list_categories, scope_list_vendors, scope_list_rosterscope_set_vendor_tier, scope_remove_from_roster, scope_award_matterscope_roster_audit, scope_vendor_health, scope_spend_rollup, scope_credential_alertsswp_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.
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.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
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.
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.
Scope Bid, Inc. is a Delaware C-corp founded May 2026 by Jack Gillen. San Diego, CA. Patent pending.
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y @jackgillen15-dev/scope-mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-jackgillen15-dev-scope-mcp": {
"command": "npx",
"args": [
"-y",
"@jackgillen15-dev/scope-mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referenceScope works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.