Scope AEC MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to Scope construction vendor procurement tools: Do prequalification evidence and human approval remain prerequisites before subcontractor commitments?

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

Best fit

AEC subcontractor procurement and vendor engagement with human approval before commitment.

What we know

Open-source MCP layer to Scope's hosted construction marketplace, returning qualified subcontractors and facilitating dispatch/procurement at published pricing with explicit GC-side human approval before commitments.

Maintenance / activity evidence

@scope-bid/scope-aec-mcp 1.0.9 published 2026-07-30T23:03:56.652Z

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.
Procurement search plus approved commercial commitment/payment workflows. Writes: Commit subcontractor dispatch/award after human approval; Trigger payment/contract-value fee workflow.
Authentication not yet verified.
Sensitive access: Project scope, Subcontractor qualification/safety/insurance, Commercial pricing

Construction procurement can create real obligations; preserve human approval step.

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

All limitations / Review context

Do prequalification evidence and human approval remain prerequisites before subcontractor commitments?

The bounded review of the publisher's documented Scope construction vendor procurement tools 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.

Construction procurement can create real obligations; preserve human approval step.
Procurement search plus approved commercial commitment/payment workflows.
Project/subcontractor procurement data flows to Scope and potentially partner vendors.
Reviewed write actions: Commit subcontractor dispatch/award after human approval; Trigger payment/contract-value fee workflow
Sensitive access: Project scope, Subcontractor qualification/safety/insurance, Commercial 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.
Marketplace/platform is hosted at scope.bid.
Commitments can create real commercial obligations and fees.
Some categories route to partner subs with confirmation SLA.
Human approval is part of the intended control boundary.

Original activity observations

@scope-bid/scope-aec-mcp 1.0.9 published 2026-07-30T23:03:56.652Z

Technical identity

npm/@scope-bid/scope-aec-mcp

Exact implementation source: https://www.npmjs.com/package/@scope-bid/scope-aec-mcp ↗
Reviewed resource type: MCP Server
Package identity: npm:@scope-bid/scope-aec-mcp

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-aec-mcp
Recorded package identity, distribution or download evidence.
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.
npm install is not direct MCP client registration.
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 open-source SDK layer, not verified MCP launch; official scope.bid/install guide needed. Preview features only.
npm install gives open-source SDK layer, not verified MCP launch; official scope.bid/install guide needed. Preview features only.
Vendor page shows limited release/vertical variants; avoid inventing cross-package launcher and production availability.
Batch08 V3 source-specific finding: Package install is not MCP host registration; follow publisher client-specific guide.
SDK package install is not client registration; production dispatch/write tools are slated for future V3 release.
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-aec-mcp
Configure / authenticate
MCP100 setup guide
Publisher explicitly defers client registration to https://scope.bid/install. npm installation alone is not successful MCP connection.
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

Open-source MCP layer to Scope's hosted construction marketplace, returning qualified subcontractors and facilitating dispatch/procurement at published pricing with explicit GC-side human approval before commitments.

Capability: Productivity & Collaboration
Resource type: MCP Server
Industry: Real Estate & Construction
Best fit: AEC subcontractor procurement and vendor engagement with human approval before commitment.

Representative uses

Find subcontractors by trade/project requirements
Check prequalification/bonding/safety/COI fields
Prepare dispatch/procurement workflows
Commit approved subcontractor engagement

Limitations

Marketplace/platform is hosted at scope.bid.
Commitments can create real commercial obligations and fees.
Some categories route to partner subs with confirmation SLA.
Human approval is part of the intended control boundary.

Reviewed access

Access & risk

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

Authentication: Not documented in the reviewed sources
Permissions: Procurement search plus approved commercial commitment/payment workflows.
Data handling: Project/subcontractor procurement data flows to Scope and potentially partner vendors.
Cost: transactional
Risk and cautions: Construction procurement can create real obligations; preserve human approval step.

Access scope and cautions

Write actions: Commit subcontractor dispatch/award after human approval Trigger payment/contract-value fee workflow
Sensitive access: Project scope Subcontractor qualification/safety/insurance Commercial 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: Find subcontractors by trade/project requirements; Check prequalification/bonding/safety/COI fields; Prepare dispatch/procurement workflows; Commit approved subcontractor engagement.

What setup and authentication are documented?

Recorded installation/entrypoint step: npm install @scope-bid/scope-aec-mcp. Recorded transport: stdio, registry_distributed. Prerequisites: MCP client. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: Scope platform account/auth as required by hosted marketplace.

Can it modify data or perform write operations?

Documented write actions include: Commit subcontractor dispatch/award after human approval; Trigger payment/contract-value fee workflow. Recorded permission boundary: Procurement search plus approved commercial commitment/payment workflows.

What data-handling boundary should I consider?

Project/subcontractor procurement data flows to Scope and potentially partner vendors. Recorded sensitive-access context: Project scope; Subcontractor qualification/safety/insurance; Commercial pricing.

What limitations and risks should I check before use?

Construction procurement can create real obligations; preserve human approval step. Marketplace/platform is hosted at scope.bid. Commitments can create real commercial obligations and fees. Some categories route to partner subs with confirmation SLA. Human approval is part of the intended control boundary. 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.