# BRAINIAC Vendor & Contractor Compliance [Health: Active]

**Category:** ⚖️ Legal  
**Repository:** https://www.brainiac.software/mcp/vendor-compliance  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/brainiac-vendor-contractor-compliance

## Description
Vendor & Contractor Compliance: 6 pay-per-call MCP tools for agents (x402 USDC on Base, no API key). Vendor and subcontractor compliance tools for procurement and AP: onboarding precheck against buyer requirements, contractor prequalification, document completeness, subcontractor payment readiness, closeout checks and a consolidated requirements report.

## Tools
Capabilities this server exposes over MCP:

- **vendor-compliance_onboarding-precheck** — Compare a supplied vendor record, document list, and attestations with the buyer requirements before you onboard or pay a vendor. Missing, expired, failed, and unverified items are reported separately. Call with vendor; optional asOf, projectName, documents, requirements, attestations. HTTP 200 with status complete, partial, or failed is charged at the full listed price. HTTP 4xx/5xx are not charged. Keywords: before you onboard or pay a vendor, vendor, asOf, projectName, documents, requirements, attestations, checkedAt, purpose, assessment, blocksWorkflow, summary, counts, findings, Precheck vendor onboarding.
- **vendor-compliance_contractor-prequalification** — Compare buyer qualification criteria with supplied vendor facts, documents, and evidence before you onboard or pay a vendor. The result does not award eligibility or query a registry. Call with vendor and requirements; optional asOf, projectName, documents, evidence. Returns checkedAt, asOf, purpose, projectName, vendor, assessment, blocksWorkflow, summary, counts, findings. HTTP 200 with status complete, partial, or failed is charged at the full listed price. HTTP 4xx/5xx are not charged. Keywords: before you onboard or pay a vendor, vendor, requirements, asOf, projectName, documents, evidence, checkedAt, purpose, assessment, blocksWorkflow, summary, counts, findings, Prequalify a contractor.
- **vendor-compliance_subcontractor-payment-readiness** — List missing payment documents and caller-supplied open items before you onboard or pay a vendor. This check does not release a payment or rerun sanctions, wage, or certificate screens. Call with requirements; optional asOf, projectName, vendor, documents, openItems. Returns checkedAt, asOf, purpose, projectName, vendor, assessment, blocksWorkflow, summary, counts, findings. HTTP 200 with status complete, partial, or failed is charged at the full listed price. HTTP 4xx/5xx are not charged. Keywords: watchlist screen, sanctions list, denied party, before you onboard or pay a vendor, requirements, asOf, projectName, vendor, documents, openItems, checkedAt, purpose, assessment, blocksWorkflow, summary.
- **vendor-compliance_document-completeness** — Compare a supplied document inventory with a buyer requirements list before you onboard or pay a vendor. Files are not fetched, and a present document is not treated as verified content. Call with documents and requirements; optional asOf, projectName. Returns checkedAt, asOf, purpose, projectName, vendor, assessment, blocksWorkflow, summary, counts, findings. HTTP 200 with status complete, partial, or failed is charged at the full listed price. HTTP 4xx/5xx are not charged. Keywords: before you onboard or pay a vendor, documents, requirements, asOf, projectName, checkedAt, purpose, vendor, assessment, blocksWorkflow, summary, counts, findings, Check vendor document completeness, document completeness.
- **vendor-compliance_report** — Consolidate supplied vendor information, documents, attestations, evidence, and open items into one requirements report before you onboard or pay a vendor. External registries are not contacted. Call with optional asOf, projectName, vendor, documents, requirements, attestations and others. HTTP 200 with status complete, partial, or failed is charged at the full listed price. HTTP 4xx/5xx are not charged. Keywords: before you onboard or pay a vendor, asOf, projectName, vendor, documents, requirements, attestations, evidence, openItems, checkedAt, purpose, assessment, blocksWorkflow, summary, counts.
- **vendor-compliance_contractor-closeout-check** — Compare buyer closeout requirements with supplied documents and attestations before you onboard or pay a vendor. A passing result does not certify that the project is complete. Call with requirements; optional asOf, projectName, vendor, documents, attestations. Returns checkedAt, asOf, purpose, projectName, vendor, assessment, blocksWorkflow, summary, counts, findings. HTTP 200 with status complete, partial, or failed is charged at the full listed price. HTTP 4xx/5xx are not charged. Keywords: before you onboard or pay a vendor, requirements, asOf, projectName, vendor, documents, attestations, checkedAt, purpose, assessment, blocksWorkflow, summary, counts, findings, Check contractor closeout.

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: medium). Install path inferred — verify against the README before running it. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "brainiac-vendor-contractor-compliance": {
    "url": "https://www.brainiac.software/mcp/vendor-compliance"
  }
}
```

## Documentation

## What BRAINIAC Vendor & Contractor Compliance does

BRAINIAC Vendor & Contractor Compliance exposes six pay-per-call MCP tools for reviewing vendor and contractor compliance inputs before onboarding or payment.

The service is intended for procurement and accounts-payable workflows. It can identify missing, expired, failed, or unverified items, but its assessments are based on the data submitted in the request. It does not replace an eligibility decision, payment release, registry lookup, or project-completion certification.

## How it works

Connect an MCP client to `https://www.brainiac.software/mcp/vendor-compliance`. Each tool accepts structured inputs such as vendor details, requirements, documents, attestations, evidence, and open items. Optional fields can include `asOf` and `projectName`, depending on the check.

Successful HTTP responses can report `complete`, `partial`, or `failed` status and are charged at the tool's full listed price. HTTP 4xx and 5xx responses are not charged. Payment uses x402 with USDC on Base, and no API key is required.

The checks compare supplied records rather than independently gathering evidence. Document checks do not fetch files, and listing a document does not establish that its contents are verified. The consolidated report combines the supplied inputs into one requirements assessment; it does not contact external registries.

## Tools and capabilities

- `vendor-compliance_onboarding-precheck` compares a vendor record, requirements, document list, and attestations. It separates missing, expired, failed, and unverified items.
- `vendor-compliance_contractor-prequalification` compares contractor qualification criteria with supplied vendor facts, documents, and evidence. It does not award eligibility or query a registry.
- `vendor-compliance_document-completeness` compares a document inventory with a buyer requirements list without retrieving files or validating document contents.
- `vendor-compliance_subcontractor-payment-readiness` lists missing payment documents and caller-supplied open items. It does not release payment or rerun sanctions, wage, or certificate screens.
- `vendor-compliance_report` consolidates vendor information, documents, requirements, attestations, evidence, and open items into a single requirements report.
- `vendor-compliance_contractor-closeout-check` compares closeout requirements with supplied documents and attestations. A passing result does not certify that the project is complete.

## Limitations and notes

Results reflect the records and criteria included in each request. The service does not independently verify document contents, contact external registries, determine contractor eligibility, release payments, rerun screening checks, or certify project completion. Callers should treat the findings as workflow checks against supplied inputs rather than as final legal, compliance, or project decisions.

_Full upstream README: https://allmcps.com/mcp/brainiac-vendor-contractor-compliance/readme_

