C2M NOOS MCP
The C2M NOOS MCP is a separate subscription that makes authorised C2M source-code evidence available through supported LLM chat interfaces. It is available after a C2M evidence baseline has been created.
C2M creates the evidence. The C2M NOOS MCP makes that evidence conversational.
Evidence access
Read-only · Authorised scope
Start with the evidence baseline
The C2M NOOS MCP does not scan source code independently. Before adding it, customers create a C2M evidence baseline either by running C2M in their own controlled environment or by assigning CodeWeTrust to perform a professional source-code assessment.
Purchase a C2M package, install and operate C2M in the agreed customer-controlled environment, and scan the selected source-code scope privately. C2M creates the evidence baseline across security, licences, dependencies, source-code quality, technical debt, and engineering activity.
Explore C2M packages at CodeWeTrust.comEngage CodeWeTrust to carry out the source-code assessment as a professional service. This route creates an independent C2M evidence baseline without requiring the customer to operate the scanning process directly.
Professional source-code assessment — from $5,000 per product.
Discuss a professional assessmentAdd the C2M NOOS MCP
The C2M NOOS MCP subscription is separate from C2M software packages and from any CodeWeTrust professional-service engagement used to create the initial evidence baseline.
$100per user / month
Billed annually at $1,200 per user per year.
$120per user / month
Billed monthly for teams that need a flexible subscription option.
A user is a logged-in C2M account holder with an applicable freemium or paid entitlement. Users can query only the C2M evidence within their authorised customer scope.
What the subscription provides
The Connector supports retrieval and synthesis of available C2M evidence. It does not replace C2M scanning, source-code assessment, engineering review, or human decision-making.
Retrieve available C2M findings through a governed, read-only MCP connection.
Ask diligence, portfolio, remediation, and AI-readiness questions through a supported LLM chat interface.
Produce evidence-backed answers, comparisons, and reports from the findings available in scope.
The C2M scan mode and authorised scope determine the evidence available to the Connector.
The security and governance model
Governed access is the read-only policy established by the C2M scan mode and the authorised evidence scope. It determines which products and findings a user may retrieve through the Connector.
Recommended configuration
The MCP evidence environment contains protected structured findings. No source-code lines are available through the standard Blind Audit MCP scope.
The recommended configuration makes protected structured findings available, not source-code lines.
Source-code context may be available only if the customer has explicitly selected and enabled it.
Users query only the products and C2M evidence they are permitted to access.
The assistant synthesises evidence; diligence, engineering, legal, investment, and management decisions remain human responsibilities.
Product differentiation
The distinction prevents the Connector from being mistaken for the scanner or from being confused with C2M’s separately packaged AI Assistant capability.
Try it
Create a free C2M demo account to explore a controlled, pre-scanned open-source product set.
Request demo accessScan my source code
Choose a C2M self-scan package or request a CodeWeTrust professional source-code assessment.
View C2M optionsConnect existing evidence
Connect authorised users to the existing C2M evidence scope through supported LLM chat interfaces.
Discuss the Connector