Publisher · domain
MCP servers published by scope.bid
3 servers in the official MCP Registry are published under the namespace bid.scope/ and have a page in this directory: 3 remote, reached by URL, and 3 run locally from a package (3 offer both). First published 2026-07-30; latest update 2026-07-30.
What this publisher publishes
Names under bid.scope/ can only be published by someone who has proved control of the domain scope.bid to the MCP Registry, through a DNS record or a file served over HTTP. The name shows who controls that domain; it does not show that the servers were reviewed.
- Namespace
bid.scope- Servers with a page
- 3
- Categories
- other (2), data (1)
- Transports
- stdio (local process) (3), Streamable HTTP (3)
- Package registries
- npm (3)
- Remote servers declaring a header
- 0 of 3
- Packages declaring environment variables
- 1 of 3
- Websites stated
- scope.bid (3)
- First published
- 2026-07-30
- Latest update
- 2026-07-30
Source repositories
All 3 servers that state a repository name the same one.
| Repository | Servers |
|---|---|
| github.com/scope-bid/scope-mcp | 3 |
All 3 servers, A to Z
| Server | Runs |
|---|---|
| Scope (AEC) - PreviewAEC subcontractor vendor procurement plumbing layer. Preview - V3 launches 2027. | Remote & Local · HTTP, stdio |
| Scope (Claims) - PreviewInsurance claims-side vendor procurement (IMEs, IA, surveillance). Preview - V2 launches Q3 2026. | Remote & Local · HTTP, stdio |
| Scope (Legal)Dispatch litigation work to legal-services vendors from any MCP-compatible AI workflow. | Remote & Local · HTTP, stdio |
Grouped by registry namespace, as the MCP Registry states it. A page here is not an endorsement and nobody pays to be listed: editorial policy · Before you connect a server