Scope Claims MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to Scope insurance-claims vendor procurement: Do credentialed vendor quotes still require carrier or firm approval before dispatch commitments?

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Insurance claims operations that need credentialed external vendors with explicit human approval before commitment.

What we know

Preview claims-procurement MCP from Scope. It shares Scope's core dispatch/negotiation infrastructure and routes claims work to external professionals while preserving a person-in-the-loop approval step before a commitment.

Maintenance / activity evidence

@scope-bid/scope-claims-mcp 1.0.9 published 2026-07-30T23:03:50.703Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Claims procurement and vendor-workflow authority. Writes: Dispatch vendor request; Negotiate/award approved work; Modify roster/vendor workflow state.
Scope auth/token for writes.
Sensitive access: Claim details, Medical/legal-support workflow information, Vendor credentials/pricing

Can create real professional-service commitments; preserve mandatory human approval.

Full authority, access and evidence limits are available in Review context and Access & risk.

All limitations / Review context

Do credentialed vendor quotes still require carrier or firm approval before dispatch commitments?

The bounded review of the publisher's documented Scope insurance-claims vendor procurement and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

Can create real professional-service commitments; preserve mandatory human approval.
Claims procurement and vendor-workflow authority.
Scope auth/token for writes.
Claim/vendor/request data is processed by Scope and potentially external service providers.
Reviewed write actions: Dispatch vendor request; Negotiate/award approved work; Modify roster/vendor workflow state
Sensitive access: Claim details, Medical/legal-support workflow information, Vendor credentials/pricing
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
Claims vertical is explicitly preview/limited-release rather than a mature general-availability service.
Coverage depends on available vendors and categories.
Writes can create real external vendor work once approved.
Read-only demo access does not imply production write authority.
Claims vertical is preview; do not present it as fully mature GA.
Publisher lifecycle: preview / limited release

Original activity observations

@scope-bid/scope-claims-mcp 1.0.9 published 2026-07-30T23:03:50.703Z

Technical identity

npm/@scope-bid/scope-claims-mcp

Exact implementation source: https://www.npmjs.com/package/@scope-bid/scope-claims-mcp ↗
Reviewed resource type: MCP Server
Repository identity: scope-bid/scope-platform
Package identity: npm:@scope-bid/scope-claims-mcp
Service endpoint: https://scope.bid/api/mcp/claims

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 8, 2026

Package registry ↗
@scope-bid/scope-claims-mcp
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.
Evidence source ↗
scope.bid/mcp
Source material retained for this review.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Warning

No third-party MCP installation, execution, connection, payment or mutation performed.
Official documentation may not prove currently operational service.
Publisher says preview; do not promise production write tools.
SDK `npm install` is not proof of a runnable stdio server or a connected MCP client.
Targeted 2026-10-13 re-research: npm install gives SDK layer, not verified MCP launch; official scope.bid/install guide needed. Preview lifecycle.
npm install gives SDK layer, not verified MCP launch; official scope.bid/install guide needed. Preview lifecycle.
Vendor page shows limited release/vertical variants; avoid inventing cross-package launcher and production availability.
Batch08 V3 source-specific finding: Same publisher guide but distinct claims identity.
SDK install alone does not connect MCP; preview and payment/PHI constraints must remain visible.
Recorded publisher instruction; runtime not tested.

Install / connect
Publisher instructions
npm package installation alone is not MCP client registration; publisher delegates client config to https://scope.bid/install. Without verified host-specific instructions, do not mark actionable-complete.
publisher documented install or connect · Publisher instructions
npm install @scope-bid/scope-claims-mcp
Configure / authenticate
MCP100 setup guide
Publisher documents client-specific installation at https://scope.bid/install; do not substitute the legal-services sibling package.
Check connection
Suggested check
User-side suggested check (not executed): inspect registered tools/connection and perform publisher-supported read-only status/list operations. Do not send, purchase, publish, delete, sign, trade or alter data as a smoke test.
Remove / uninstall / revoke
MCP100 setup guide
Generic client guidance (not publisher-specific uninstall): unregister MCP entry in the chosen client. If installed globally, remove the npm package separately. Revoke provider access separately through account controls, where supported. This does not erase local data or revoke funds/credentials automatically.
Unregister the named MCP entry from the actual host separately from removing a global npm install; no claim that either revokes remote credentials.
Remove local stored keys/tokens and revoke or rotate corresponding provider authorization using documented provider account controls if available; exact procedure not verified for this package. Wallet private keys cannot be revoked.

Official Documentation & Sources

What it does

Preview claims-procurement MCP from Scope. It shares Scope's core dispatch/negotiation infrastructure and routes claims work to external professionals while preserving a person-in-the-loop approval step before a commitment.

Capability: Productivity & Collaboration
Resource type: MCP Server
Industry: Insurance
Best fit: Insurance claims operations that need credentialed external vendors with explicit human approval before commitment.

Representative uses

Route IME requests
Coordinate surveillance vendors
Request defense medical record review
Route vocational rehabilitation or life-care planning
Audit vendor rosters and credential alerts

Limitations

Claims vertical is explicitly preview/limited-release rather than a mature general-availability service.
Coverage depends on available vendors and categories.
Writes can create real external vendor work once approved.
Read-only demo access does not imply production write authority.
Claims vertical is preview; do not present it as fully mature GA.
Publisher lifecycle: preview / limited release

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Scope auth/token for writes.
Permissions: Claims procurement and vendor-workflow authority.
Data handling: Claim/vendor/request data is processed by Scope and potentially external service providers.
Cost: transactional
Risk and cautions: Can create real professional-service commitments; preserve mandatory human approval.

Access scope and cautions

Write actions: Dispatch vendor request Negotiate/award approved work Modify roster/vendor workflow state
Sensitive access: Claim details Medical/legal-support workflow information Vendor credentials/pricing
Risk level: high

FAQ

Based on reviewed evidence as of 2026-10-08. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Route IME requests; Coordinate surveillance vendors; Request defense medical record review; Route vocational rehabilitation or life-care planning; Audit vendor rosters and credential alerts.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx -y @scope-bid/scope-claims-mcp. Recorded endpoint: https://scope.bid/api/mcp/claims. Recorded transport: stdio, streamable_http. Recorded environment-variable notes: SCOPE_API_TOKEN (write operations); SCOPE_API_BASE (optional); SCOPE_ORG_SLUG (optional). No configuration values are supplied here. Prerequisites: MCP client; Scope account/organization for live procurement. Client notes: Human approval is an intentional control before commitment. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: Read-only demo can work without token; write operations use Scope bearer token/marketplace auth. A demo or keyless description is not independently verified read-only authority. Check the documented tool permissions rather than inferring authority from that label.

Can it modify data or perform write operations?

Documented write actions include: Dispatch vendor request; Negotiate/award approved work; Modify roster/vendor workflow state. Recorded permission boundary: Claims procurement and vendor-workflow authority.

What data-handling boundary should I consider?

Claim/vendor/request data is processed by Scope and potentially external service providers. Recorded sensitive-access context: Claim details; Medical/legal-support workflow information; Vendor credentials/pricing.

What limitations and risks should I check before use?

Can create real professional-service commitments; mandatory human approval remains required. Claims vertical is explicitly preview/limited-release rather than a mature general-availability service. Coverage depends on available vendors and categories. Writes can create real external vendor work once approved. Read-only demo access does not imply production write authority. Claims vertical is preview, rather than fully mature general availability. Publisher lifecycle: preview / limited release. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.

What cost model is recorded?

The reviewed cost model is transactional. This classification does not establish current prices, quotas or the cost of every downstream operation. Check the applicable service terms before authorizing paid actions.