# Checkmycontractorquote Contractor Quote Check MCP server

Source: https://glimind.com/server/mcp-registry%2Fcom.checkmycontractorquote%2Fcontractor-quote-check
Registry id: `mcp-registry/com.checkmycontractorquote/contractor-quote-check`
Status: unknown (checked 2026-11-21T18:59:18.414Z)

## Measurements (30 days)

- Uptime: 0%
- Checks: 59
- Outages (90 days): 0

## Install

```json
{
  "mcpServers": {
    "checkmycontractorquote-contractor-quote-": {
      "type": "http",
      "url": "https://checkmycontractorquote.com/contractorquote-mcp/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http checkmycontractorquote-contractor-quote- https://checkmycontractorquote.com/contractorquote-mcp/mcp
```

## Tools (48)

- `audit_quote`: Use this when a user wants a structured review of one contractor quote for missing or unclear sections.
- `audit_workflow_for_ai`: Use this when a user wants a workflow reviewed for AI/MCP automation opportunities.
- `build_application_checklist`: Use this when a user wants an application checklist from grant requirements.
- `build_compliance_matrix`: Use this when a user wants an RFP requirement/compliance matrix.
- `build_fire_purchase_checklist`: Use this when a user wants a purchasing checklist for fire/public-safety equipment.
- `build_firegrant_checklist`: Use this when a user wants a fire-grant application preparation checklist.
- `build_inspection_questions`: Use this when a user wants questions to verify inspection requirements.
- `build_integration_checklist`: Use this when a user wants an implementation checklist for an AI/MCP integration.
- `build_vendor_questions`: Use this when a user wants vendor clarification questions from a bid.
- `compare_quotes`: Use this when a user wants to compare two or three contractor quotes side by side.
- `compare_rfq_quotes`: Use this when a user wants public-safety RFQ quote amounts and comparison flags organized.
- `create_listing_requirements`: Use this when a user wants a checklist of information required before listing inventory.
- `create_opening_plan`: Use this when a user wants a project-opening plan from permit dependencies.
- `create_reminder_plan`: Use this when a user wants a reminder-plan outline from a compliance calendar.
- `create_tool_catalog`: Use this when a user wants a proposed AI/MCP tool catalog for a workflow.
- `draft_response_outline`: Use this when a user wants a response outline derived from RFP requirements.
- `draft_tenant_questions`: Use this when a user wants questions to ask a tenant before maintenance dispatch.
- `estimate_margin_fields`: Use this when a user wants the inputs required to assess potential listing margin.
- `explain_required_documents`: Use this when a user wants a checklist of documents likely needed for a compliance lane.
- `extract_bid_requirements`: Use this when a user wants public-safety bid requirements extracted.
- `extract_firegrant_requirements`: Use this when a user wants fire-grant requirements extracted.
- `extract_grant_requirements`: Use this when a user wants grant requirements extracted from source text.
- `extract_quote_amounts`: Use this when a user wants amounts detected from a contractor quote.
- `extract_requirements`: Use this when a user wants requirements extracted from an RFP or solicitation.
- `flag_missing_quote_sections`: Use this when a user wants missing or unclear quote sections identified.
- `flag_procurement_gaps`: Use this when a user wants missing procurement assumptions or quote-comparison gaps flagged.
- `generate_compliance_calendar`: Use this when a user wants a starter compliance calendar for a supported business vertical.
- `generate_contractor_questions`: Use this when a user wants questions to ask a contractor based on a quote.
- `generate_evidence_list`: Use this when a user wants a list of supporting evidence/documents to gather for a grant.
- `generate_mcp_package_plan`: Use this when a user wants a scoped MCP/AI implementation package plan.
- `generate_no_bid_reason`: Use this when a user wants likely reasons a solicitation may be a weak fit or no-bid.
- `generate_permit_checklist`: Use this when a user wants a starter permit/opening checklist for a supported lane.
- `generate_quote_report`: Use this when a user explicitly wants a saved Contractor Quote Check report generated from quote text.
- `generate_rfp_questions`: Use this when a user wants clarification questions derived from an RFP.
- `generate_supplier_intake`: Use this when a user wants a supplier intake checklist for inventory or travel/resort offers.
- `generate_vendor_packet`: Use this when a user wants a vendor-dispatch information packet drafted from a maintenance issue.
- `generate_vendor_questions`: Use this when a user wants questions to send vendors before comparing quotes.
- `identify_likely_forms`: Use this when a user wants likely forms or approvals identified for a project.
- `list_renewal_items`: Use this when a user wants likely renewal/checklist items from a compliance lane.
- `normalize_inventory`: Use this when a user wants inventory fields normalized into a consistent listing structure.
- `rank_urgency`: Use this when a user wants maintenance urgency categorized from issue text.
- `save_checkout_interest`: Use this only when a user explicitly asks to record checkout interest at a stated price point.
- `save_lead`: Use this only when a user explicitly asks to save their interest or contact details for this product.
- `score_bid_fit`: Use this when a user wants a checklist-style fit score for a public-safety bid.
- `score_bid_readiness`: Use this when a user wants a checklist-style bid-readiness assessment from RFP text.
- `score_firegrant_readiness`: Use this when a fire department wants a checklist-style readiness assessment for grant text.
- `score_grant_readiness`: Use this when a user wants a grant-readiness checklist from grant text and organization context.
- `triage_maintenance_issue`: Use this when a user wants a maintenance issue categorized by urgency for human review.

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.
