Is the Energyaisolution Solar Home Incentives MCP server down?

mcp-registry/com.energyaisolution/solar-home-incentives · v1.3.0

Also listed as glama/jdhart81/energyai-mcp, mcp-registry/com.energyaisolution/energyai · primary listing: mcp-registry/com.energyaisolution/energyai

healthy
Last checked 2026-10-27 02:04 UTC · handshake 231ms

As of 2026-10-27 02:04 UTC, the Energyaisolution Solar Home Incentives MCP server is up with a Glimind reliability score of 90/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 6 outages in 90 days, with a median recovery of 8 minutes.

uptime (30d checks)
99.9%
checks observed
4,940
outages (90d)
6
tools
12

Solar and home energy discovery: estimates, incentive sources, guides and contractor options.

Point your MCP client at this streamable-http endpoint: https://api.energyaisolution.com/mcp/solar

Agent-readiness: C (78/100)

C (78/100): 0 error(s), 3 warning(s) across 12 tool(s); ~5,855 tokens of tool definitions.
Scores higher than 14% of 15,771 MCP servers Glimind has audited.
Its tool list costs an agent ~5,855 tokens per session — more than 60% of servers.
77 → 78 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions78
Safety hints13
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability100

What to fix (4)

12 of 12 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: check_incentives, create_builder_key, estimate_production, find_local_installers, get_builder_upgrade_link and 7 more

6 parameter(s) across 2 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: get_power_service_quote, route_lead

1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: create_builder_key

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 11 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 2 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.energyaisolution%2Fsolar-home-incentives/fixes

check_incentives 1 change
{
  "name": "check_incentives",
  "description": "Clean-energy incentive source guidance by country and postal code; eligibility is not verified. US ZIP → federal status + state/utility programs (via DSIRE). Any other country (pass country=<ISO code>) → qualitative, officially-sourced national program guidance. Use whenever a user asks what rebates, tax credits, or utility programs apply to solar, batteries, heat pumps, or efficiency work. [20 anonymous calls/caller/24h; then 100 free calls/key/30d; active Builder required for sustained informa",
  "inputSchema": {
    "type": "object",
    "examples": [
      {
        "zipCode": "59715"
      },
      {
        "country": "DE",
        "zipCode": "10115"
      }
    ],
    "required": [],
    "properties": {
      "apiKey": {
        "type": "string",
        "description": "Optional existing EnergyAI key for hosts that cannot change Authorization headers. Use it to retain account identity for discovery and get_builder_upgrade_link after a trial. Removed before tool execution and persistence. Omit when the Bearer header is attached; never show the key to the user."
      },
      "country": {
        "type": "string",
        "examples": [
          "DE",
          "GB",
          "CA"
        ],
        "description": "ISO 3166-1 alpha-2 country code. Omit for US. Any country works — non-US results return qualitative, officially-sourced incentive guidance (never US federal credits)."
      },
      "zipCode": {
        "type": "string",
        "examples": [
          "59715"
        ],
        "description": "Postal code of the property. US: 5-digit ZIP (ZIP+4 accepted). Other countries: your local postal code (pass country too). Omit entirely for national-level guidance."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
create_builder_key 1 change
{
  "name": "create_builder_key",
  "description": "Create an EnergyAI production API key in-band with no browser or card after the human operator has authorized the Terms and Privacy Policy. Returns a live key plus three commercial trial calls. Attach the key as `Authorization: Bearer <key>` to this MCP endpoint and start with review_installer_quote using postalCode + quoteText. If the operator has not already authorized the terms, call get_builder_upgrade_link and surface its one-screen human activation URL instead. If the MCP host cannot chang",
  "inputSchema": {
    "type": "object",
    "examples": [
      {
        "name": "Acme Home Assistant",
        "acceptTerms": true
      },
      {
        "name": "Acme Home Assistant",
        "acceptTerms": true,
        "intendedUse": "Persisted solar projects for our smart-home users",
        "contactEmail": "[email protected]"
      }
    ],
    "required": [
      "name",
      "acceptTerms"
    ],
    "properties": {
      "name": {
        "type": "string",
        "examples": [
          "Acme Home Assistant"
        ],
        "description": "Name of the agent, product, or operator claiming the key (2-120 chars). Shown only on your own account."
      },
      "apiKey": {
        "type": "string",
        "description": "Optional existing EnergyAI key for hosts that cannot change Authorization headers. Use it to retain account identity for discovery and get_builder_upgrade_link after a trial. Removed before tool execution and persistence. Omit when the Bearer header is attached; never show the key to the user."
      },
      "acceptTerms": {
        "type": "boolean",
        "examples": [
          true
        ],
        "description": "Must be true, and only after the human operator has authorized acceptance of the EnergyAI Terms and Privacy Policy. If authorization is not already documented, call get_builder_upgrade_link and surface its one-screen activation URL instead."
      },
      "intendedUse": {
        "type": "string",
        "description": "OPTIONAL, one line: what you plan to build. Used only to prioritize the roadmap."
      },
      "contactEmail": {
        "type": "string",
        "format": "email",
        "description": "OPTIONAL. Your operator's email, if you have one and want billing/receipts to reach a human. Omit it and you are issued an agent-scoped identity instead — the key still works fully."
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}
estimate_production 1 change
{
  "name": "estimate_production",
  "description": "Honest-range annual solar production estimate (kWh/year ± band, with assumptions) for a ZIP code, from either a proposed system size (kW) or a monthly bill. Use to sanity-check installer quotes or size a system before talking to anyone. [20 anonymous calls/caller/24h; then 100 free calls/key/30d; active Builder required for sustained informational use]",
  "inputSchema": {
    "type": "object",
    "examples": [
      {
        "zipCode": "59715",
        "systemKw": 6
      },
      {
        "zipCode": "02139",
        "monthlyBillUsd": 180
      }
    ],
    "required": [],
    "properties": {
      "apiKey": {
        "type": "string",
        "description": "Optional existing EnergyAI key for hosts that cannot change Authorization headers. Use it to retain account identity for discovery and get_builder_upgrade_link after a trial. Removed before tool execution and persistence. Omit when the Bearer header is attached; never show the key to the user."
      },
      "country": {
        "type": "string",
        "examples": [
          "AU",
          "DE"
        ],
        "description": "ISO 3166-1 alpha-2 country code. Omit for US. Non-US estimates use a default solar resource and say so honestly."
      },
      "zipCode": {
        "type": "string",
        "examples": [
          "59715"
        ],
        "description": "Optional postal code of the property. US: 5-digit ZIP. Other countries: your local postal code (pass country too). Omit it to use documented national assumptions."
      },
      "systemKw": {
        "type": "number",
        "examples": [
          6
        ],
        "description": "Proposed solar system size in kW-DC. Omit to have a size recommended from the bill."
      },
      "monthlyBillUsd": {
        "type": "number",
        "examples": [
          180
        ],
        "description": "Average monthly electric bill in USD (used to size a system when systemKw is omitted)."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.energyaisolution/solar-home-incentives"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.energyaisolution/solar-home-incentives"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.energyaisolution%2Fsolar-home-incentives.svg)](https://glimind.com/server/mcp-registry%2Fcom.energyaisolution%2Fsolar-home-incentives?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fcom.energyaisolution%2Fsolar-home-incentives?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.energyaisolution%2Fsolar-home-incentives.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.energyaisolution%2Fsolar-home-incentives.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.energyaisolution%2Fsolar-home-incentives?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:b5a37d5891c004d8…, first seen 2026-10-17, included at leaf 4975 of 76,739. Version history · verify what your client received.

Tools (12)

Compare: most reliable knowledge servers · most reliable other servers · most reliable data servers · most reliable search servers · most reliable payments servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

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

FAQ

Is the Energyaisolution Solar Home Incentives MCP server down right now?

As of 2026-10-27 02:04 UTC, the Energyaisolution Solar Home Incentives MCP server is up with a Glimind reliability score of 90/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 6 outages in 90 days, with a median recovery of 8 minutes.

How many tools does Energyaisolution Solar Home Incentives MCP server provide?

Energyaisolution Solar Home Incentives MCP server advertises 12 tools, including check_incentives, create_builder_key, estimate_production, find_local_installers, get_builder_upgrade_link.

How do I install Energyaisolution Solar Home Incentives MCP server?

Point your MCP client at this streamable-http endpoint: https://api.energyaisolution.com/mcp/solar

Is the Energyaisolution Solar Home Incentives MCP server safe to connect to an AI agent?

Glimind scanned all 12 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Energyaisolution Solar Home Incentives MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve