Marketing

whatsolarcosts.com

Provides residential solar cost and savings estimates, solar installer lead economics, and homeowner quote requests.

1 endpoint3 known toolsFirst detected October 25, 2026Last detected October 25, 2026

ENDPOINT 1

https://whatsolarcosts.com/mcp

No auth detected

MCP server metadata

Name: com.whatsolarcosts/solar-cost-estimate
Version: 1.1.0

Capabilities

tools

Server instructions

This server serves both sides of the US residential solar market. Pick the tool by who is asking. Use get_solar_estimate for a homeowner pricing rooftop solar. It needs only a two-letter state code and an average monthly electricity bill. Results are educational modelling from published state-level averages — not an installation quote, not a savings guarantee and not tax advice — so present them as a range and keep the limitations the tool returns. Two things are easy to get wrong: no federal tax credit applies to purchased residential systems installed in 2026, and state and local incentives are not subtracted from the cost shown. Share the results_url with the homeowner; it reproduces the estimate. To request installer quotes for them, use request_installer_quotes — but only after the homeowner has asked for quotes and agreed to the disclosure that tool returns. It emails them a confirmation link; no installer is contacted until they confirm. Never request quotes on your own initiative, and never use contact details the homeowner did not give you for this. Use get_lead_economics for a solar installer or contractor deciding whether to buy leads, what to pay for one, or whether a market is worth entering. Every input is optional, but the answer is only as good as the close_rate supplied: ask for the installer's own lead-to-sale rate before calling, and if you fall back to the benchmark, say so — the result carries close_rate_source for exactly that reason. Cost per install, not cost per lead, is the number that decides this, and close rate moves it far more than lead price does. No tool here can sign an installer up: an installer partnership is applied for by a human at the partner_url the result returns.

Known tools 3

get_solar_estimate

Estimate the cost, size, savings and payback of a residential rooftop solar system for a US state and an average monthly electricity bill.

Inferred read-only

get_lead_economics

For a solar installer or contractor: what a bought residential solar lead actually costs them.

Inferred read-only

request_installer_quotes

Ask for solar installer quotes on a homeowner's behalf, after they have asked for them.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.com-whatsolarcosts-solar-cost-estimate]
url = "https://whatsolarcosts.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "com-whatsolarcosts-solar-cost-estimate": {
      "type": "http",
      "url": "https://whatsolarcosts.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: com-whatsolarcosts-solar-cost-estimate
Remote MCP URL: https://whatsolarcosts.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "com-whatsolarcosts-solar-cost-estimate": {
      "url": "https://whatsolarcosts.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "com-whatsolarcosts-solar-cost-estimate": {
      "type": "http",
      "url": "https://whatsolarcosts.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "com-whatsolarcosts-solar-cost-estimate",
  "transport": "streamable-http",
  "url": "https://whatsolarcosts.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.