GreenLight - Plug-in Solar Law Registry
REMOTE · SOLAR.AGENTLOOKUPS.AI
US plug-in solar (balcony solar) law registry with a daily UL 3700 certification watch.
Available components
Last scanned (12 hours ago)
Scores higher than 7% of remote servers
Reachable. Last reached 21 Nov 2026.
Deprecated
This server is marked deprecated in the MCP registry.
The registry records this reason: GreenLight closed on 2026-09-28 because its answers could not be kept correct; the server answers 410 Gone. Notice: https://solar.agentlookups.ai…
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 410. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (5)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (6)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Oct 26 −60
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 22 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 27 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 26 Aug 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://solar.agentlookups.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=solar.agentlookups.ai | CN=YR2,O=Let's Encrypt,C=US | 7 Oct 2026 | 5 Jan 2027 | RSA 2048 | SHA256-RSA | 6242d14211bb51c66c51d754a39537918e7 |
| SANs: solar.agentlookups.ai | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of solar.agentlookups.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | DS published | 1814 | 8 | Verified |
| agentlookups.ai. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 410 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://solar.agentlookups.ai/mcp | HTTP error | 410 | |
| http (plaintext) | http://solar.agentlookups.ai/mcp | HTTPS enforced | 301 | https://solar.agentlookups.ai/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
solar_law Look up one state's plug-in solar law record ~234
Returns the full GreenLight registry record for one state's plug-in (balcony) solar law: legal status, the law's name and dates, key provisions as recorded (power cap, certification requirement, utility notice, renter/HOA treatment), citations with official-text URLs where the verification pass attached them, and verification status with dates. Input: state, a two-letter US state or DC code or a full state name. Entries marked pending are under review: they have not passed the field-by-field check against the enrolled bill text, so every field in them counts as unconfirmed, and the record's verification_note says so. A US state not in the registry returns tracked:false, which says nothing about that state's law; input that is not a US state or DC is an error. The record is not legal advice. No certification claim is published until an independent adversarial verification pass confirms it against the certifying source.
| Name | Type | Req | Description |
|---|---|---|---|
| state | string | yes | Two-letter US state or DC code, e.g. "UT" or "md" (case-insensitive), or a full state name such as "Utah". |
No output schema declared.
No examples provided.
solar_states List plug-in solar registry states ~104
Lists every state in the GreenLight plug-in (balcony) solar registry with its legal status, law name, power cap, and verification state, plus a count of entries by verification state. Takes no input. GreenLight records enacted law only, verified field-by-field against the enrolled bill text; entries still marked pending are under review and unconfirmed. A state not listed is simply not in the registry; that says nothing about its law. The registry is not legal advice.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the GreenLight - Plug-in Solar Law Registry MCP server?
GreenLight - Plug-in Solar Law Registry is a hosted endpoint at https://solar.agentlookups.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · solar.agentlookups.ai
claude mcp add --transport http ai-agentlookups-greenlight 'https://solar.agentlookups.ai/mcp'
What is the GreenLight - Plug-in Solar Law Registry MCP server?
GreenLight - Plug-in Solar Law Registry is an MCP server listed in the public MCP registry as ai.agentlookups/greenlight. US plug-in solar (balcony solar) law registry with a daily UL 3700 certification watch. This page covers its hosted endpoint (https://solar.agentlookups.ai/mcp).
Is the GreenLight - Plug-in Solar Law Registry MCP server safe to use?
GreenLight - Plug-in Solar Law Registry scores 23 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the GreenLight - Plug-in Solar Law Registry MCP server expose?
GreenLight - Plug-in Solar Law Registry exposes 2 tools: solar_states, solar_law. Their descriptions and schemas cost roughly 338 tokens of context every time the server is loaded.
Does the GreenLight - Plug-in Solar Law Registry MCP server require authentication?
Its publisher declares no required credentials for GreenLight - Plug-in Solar Law Registry. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the GreenLight - Plug-in Solar Law Registry MCP server still maintained?
GreenLight - Plug-in Solar Law Registry is marked deprecated in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the GreenLight - Plug-in Solar Law Registry MCP server?
VerifyMCP ran 5 checks on GreenLight - Plug-in Solar Law Registry, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 1 more. 6 items could not be completed, a gap on our side rather than a finding about GreenLight - Plug-in Solar Law Registry: Authorization, Schema quality, Stability, Tool coverage and 2 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.