Publisher portfolio
scope.bid
Explore the MCP servers published by scope.bid, with independent connection checks, performance measurements, and setup instructions for each project.
- Listed servers
- 5
Active projects in this portfolio. Deleted and deprecated registry rows are excluded.
- Sampled servers
- 3
Active servers with a recorded connection probe
- Latest probe connected
- 0
Latest stored probe connected. This is not a live guarantee.
- Repositories
- 1
Distinct source repositories linked by the active listings
Portfolio overview
MCP servers
Compare connection status and measurements. Open a server for its tools, check results, and client configuration.
| Server / capability | Last probe | Median latency | Checks passed | Last checked |
|---|---|---|---|---|
Scope (AEC) - Preview AEC subcontractor procurement layer. Preview - V3 launches 2027. | Requires auth | Not measured | 5 / 22 | |
Scope (Claims) - Preview Claims-side professional procurement (IMEs, independent adjusters, surveillance). Preview. | Requires auth | Not measured | 5 / 22 | |
Scope (Legal) Dispatch litigation work to legal-services professionals from any MCP-compatible AI workflow. | Requires auth | Not measured | 5 / 22 | |
bid.scope/pharma Pharma vendor-services MCP. Preview. Available after legal, claims, and AEC are live. | Not measured | Not measured | 3 / 6 | Not checked yet |
bid.scope/healthcare Healthcare vendor-services MCP. Preview. Available after legal, claims, and AEC are live. | Not measured | Not measured | 3 / 6 | Not checked yet |
Company & identity
About scope.bid
scope.bid publishes MCP servers under the bid.scope namespace. This namespace uses a reverse-domain identity in the directory.
Namespace verification connects the publisher to its registry identity. It does not certify the security of individual servers.