Other · Remote MCP server
Scope (Claims) - Preview
Insurance claims-side vendor procurement (IMEs, IA, surveillance). Preview - V2 launches Q3 2026.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
bid.scope/claims- Version
- 1.0.9
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-07-30
- Updated
- 2026-07-30
- Publisher
- bid.scope · 3 servers with pages here
- Website
- scope.bid/mcp/claims
- Repository
- github.com/scope-bid/scope-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://scope.bid/api/mcp/claims | None |
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @scope-bid/scope-claims-mcp | 1.0.9 | stdio |
How to connect Scope (Claims) - Preview
Scope (Claims) - Preview is a remote MCP server: there is nothing to install. Its endpoint is https://scope.bid/api/mcp/claims, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from a Node.js package published to the npm registry: @scope-bid/scope-claims-mcp version 1.0.9. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx — the usual command is npx -y @scope-bid/scope-claims-mcp@1.0.9.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"claims": {
"command": "npx",
"args": [
"-y",
"@scope-bid/scope-claims-mcp@1.0.9"
]
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from bid.scope
| Server | Runs |
|---|---|
| Scope (AEC) - PreviewAEC subcontractor vendor procurement plumbing layer. Preview - V3 launches 2027. | Remote & Local · HTTP, stdio |
| Scope (Legal)Dispatch litigation work to legal-services vendors from any MCP-compatible AI workflow. | Remote & Local · HTTP, stdio |
More other servers
| Server | Runs |
|---|---|
| Scholar SidekickCatch AI-fabricated citations (real DOI + fake title). Retraction, open-access, 10,000+ CSL styles. | Remote & Local · HTTP, stdio |
| Scholium Live NeedleGET a public URL now and report whether an exact needle is still in the body. | Remote · HTTP |
| SCModelingSupply-chain network design via simulation, optimization, and greenfield analysis. | Remote · HTTP |
| Scope ChangeScope changes against a work order, each with a reason, a date and the client's approval on record. | Remote & Local · HTTP, stdio |
| ScopeGatePermission gateway for AI agents: scoped MCP endpoints over 27 services, audited and revocable. | Remote · HTTP |
| ScopeLinqReads what was agreed and answers whether a new request is Included, citing only confirmed lines. | Remote · HTTP |
| ScopeProofMachine-verifiable authorization checks for autonomous AI agents. | Remote · HTTP |