Skip to content
Colorado Roof Replacement Cost logo

Colorado Roof Replacement Cost MCP server

Which servers in the official MCP registry are Colorado Roof Replacement Cost's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-15

← Back to Colorado Roof Replacement Cost

Whose server it is
  • Registry namecom.coloradoroofreplacementcost/siteverified in the MCP registry

The registry name sits under coloradoroofreplacementcost.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-15
  • Stateanswerschecked 2026-10-15
  • Tools3
  • Server calls itselfColorado Roof Replacement Cost (coloradoroofreplacementcost.com)
  • Server version1.0.0
  • Protocol version2025-06-18

On 2026-10-15 the server answered initialize and tools/list without a sign-in. First answer in 920 ms.

Tools it offers3 tools · read 2026-10-15
  • enquiry_describe

    Read first. States plainly what submit_enquiry does on Colorado Roof Replacement Cost: it starts an enquiry with human providers who quote directly. Nothing is bought, ordered or paid; no quote is guaranteed; it is free. Also returns who…

  • enquiry_fields

    Every field of the Colorado Roof Replacement Cost enquiry: key, label, type, whether required, help text and the allowed options where there are any. Pass answers to submit_enquiry keyed by field key.

  • submit_enquiry

    Submits an enquiry to Colorado Roof Replacement Cost — NOT a purchase, NOT a guaranteed quote. Step 1: call with the answers (keyed by field key from enquiry_fields) and consent=true; it validates and returns a summary, the consent line…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "site": {
      "type": "http",
      "url": "https://coloradoroofreplacementcost.com/mcp"
    }
  }
}

OpenAPI spec

4 paths, read 2026-10-15. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.