GreenLight - Plug-in Solar Law Registry
REMOTE · SOLAR.AGENTLOOKUPS.AI · SCANNED SEP 21
US plug-in solar (balcony solar) law registry with a daily UL 3700 certification watch.
Available components
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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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 & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 332 tokens (~166/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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'
{
"mcpServers": {
"ai-agentlookups-greenlight": {
"url": "https://solar.agentlookups.ai/mcp"
}
}
} {
"servers": {
"ai-agentlookups-greenlight": {
"type": "http",
"url": "https://solar.agentlookups.ai/mcp"
}
}
} [mcp_servers.ai-agentlookups-greenlight] url = "https://solar.agentlookups.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-agentlookups-greenlight": {
"type": "remote",
"url": "https://solar.agentlookups.ai/mcp",
"enabled": true
}
}
} openclaw mcp add ai-agentlookups-greenlight --url 'https://solar.agentlookups.ai/mcp' --transport streamable-http
mcp_servers:
ai-agentlookups-greenlight:
url: "https://solar.agentlookups.ai/mcp" {
"McpServers": {
"ai-agentlookups-greenlight": {
"Transport": "http",
"Url": "https://solar.agentlookups.ai/mcp"
}
}
} assistant mcp add ai-agentlookups-greenlight -t streamable-http -u 'https://solar.agentlookups.ai/mcp'
{
"mcpServers": {
"ai-agentlookups-greenlight": {
"type": "http",
"url": "https://solar.agentlookups.ai/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
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 Sept 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=YR1,O=Let's Encrypt,C=US | 3 Aug 2026 | 1 Nov 2026 | RSA 2048 | SHA256-RSA | 6e6fd97dc1e78c321b1f1959de227bfe1a1 |
| SANs: solar.agentlookups.ai | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| 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. | present | 3799 | 8 | Verified |
| agentlookups.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
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 | Verified | 200 | |
| 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 ~160
Fetch 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. Entries marked pending are under review: unconfirmed against the enrolled bill text, so treat every field as unconfirmed and say so. A state not in the registry returns tracked:false, which says nothing about that state's law. Never legal advice; certification claims are only published after human confirmation.
| Name | Type | Req | Description |
|---|---|---|---|
| state | string | yes | Two-letter US state code, e.g. "UT" or "md" (case-insensitive). |
No output schema declared.
No examples provided.
solar_states ~88
List every state in the GreenLight plug-in (balcony) solar registry with its legal status, law name, power cap, and verification state. 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. Not legal advice.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
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 83 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 248 tokens of context every time the server is loaded.
Does the GreenLight - Plug-in Solar Law Registry MCP server require authentication?
No. We connected to GreenLight - Plug-in Solar Law Registry without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the GreenLight - Plug-in Solar Law Registry MCP server still maintained?
GreenLight - Plug-in Solar Law Registry is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.