Scope (Claims) - Preview
NPM · @SCOPE-BID/SCOPE-CLAIMS-MCP · 2 COMPONENTS
Claims-side professional procurement (IMEs, independent adjusters, surveillance). Preview.
Available components
Last scanned (12 hours ago)
Scores higher than 87% of npm servers
Category CRM and Sales
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 94 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to scope-bid/scope-mcp). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability67
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 432 tokens (~108/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage70
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 11% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 3 Nov 26 −5
- Malware scan: pass → unverified ▼ security
- Provenance: fail → pass ▲ security
- The attested source repository moved: scope-bid/scope-mcp security
- Package version: 1.0.10 → 1.0.11 functional
- 2 Nov 26 0
- Stability: 0.97 → pass security
- 1 Nov 26 0
- Stability: pass → 0.97 functional
- 26 Oct 26 0
- Stability: 0.97 → pass security
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 −6
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- Stability: pass → 0.93 functional
- 18 Oct 26 0
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@scope-bid/scope-claims-mcp@1.0.11
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | scope-bid/scope-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/scope-bid/scope-mcp/.github/workflows/publish.yml@refs/tags/v1.0.11 |
| Rekor log index | 3679152191 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:e72a10ac458252d9bb4c44123403cba7e51af8abc08584fe37b1cb500cc3d8529e0ca86767bf71a4fa7715fa6bdfd66defafa5945e104db9247c1603a |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 94 packages
| Packages resolved | 94 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
scope_claims_categories ~37
List planned V2 service categories for Scope's claims-side professional dispatch. These are the categories professionals can register for in the founding cohort.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
scope_claims_join_waitlist ~121
Register interest in Scope's V2 (insurance claims). For professionals who want to be in the founding cohort, or carriers / TPAs / corporate risk teams who want early access. Captured to the Scope waitlist.
| Name | Type | Req | Description |
|---|---|---|---|
| category_interest | string | – | One of: independent-medical-exam, independent-adjuster, surveillance, vocational-expert, life-care-planner, subrogation-recovery |
| string | yes | – | |
| notes | string | – | – |
| organization | string | – | – |
| role | string | yes | – |
No output schema declared.
No examples provided.
scope_claims_status ~46
Returns the status and roadmap for Scope's claims-side professional procurement (V2). Useful for AI workflows that want to know whether IME / IA / surveillance dispatch is live yet.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
scope_reschedule_project ~87
Reschedule an already-awarded claims 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 professional was notified.
| Name | Type | Req | Description |
|---|---|---|---|
| new_date | string | yes | – |
| new_duration_minutes | integer | – | – |
| project_id | string | yes | – |
| reason | string | – | – |
No output schema declared.
No examples provided.
How do I install the Scope (Claims) - Preview MCP server?
Scope (Claims) - Preview runs locally as an npm package, launched with npx -y @scope-bid/scope-claims-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @scope-bid/scope-claims-mcp
claude mcp add bid-scope-claims -- npx -y @scope-bid/scope-claims-mcp
What is the Scope (Claims) - Preview MCP server?
Scope (Claims) - Preview is an MCP server listed in the public MCP registry as bid.scope/claims. Claims-side professional procurement (IMEs, independent adjusters, surveillance). Preview. This page covers its npm package (@scope-bid/scope-claims-mcp).
Is the Scope (Claims) - Preview MCP server safe to use?
Scope (Claims) - Preview scores 85 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Scope (Claims) - Preview MCP server expose?
Scope (Claims) - Preview exposes 4 tools: scope_claims_status, scope_claims_categories, scope_claims_join_waitlist, scope_reschedule_project. Their descriptions and schemas cost roughly 291 tokens of context every time the server is loaded.
Is the Scope (Claims) - Preview MCP server still maintained?
Scope (Claims) - Preview is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Scope (Claims) - Preview MCP server under?
Scope (Claims) - Preview declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.