GreenLight - Plug-in Solar Law Registry MCP server
ai.agentlookups/greenlightagentlookups.aistreamable-httpv1.0.0Scanned
US plug-in solar (balcony solar) law registry with a daily UL 3700 certification watch.
2 tools: 2 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Sign-in required, no OAuth metadata. Remote posture
Anlyon alternative
Run the operations that matter as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the GreenLight - Plug-in Solar Law Registry MCP server can do
The GreenLight - Plug-in Solar Law Registry MCP server is published by agentlookups.ai, a domain the MCP Registry verified. It has 2 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Last scanned Oct 21, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
2 tools
Only reads 2Show 2 read-only tools
solar_lawReturns 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, certificatio…No findings
Why it is in this group
- The description's first verb is "return": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Look up one state's plug-in solar law record
solar_statesLists 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 sta…No findings
Why it is in this group
- The description's first verb is "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: List plug-in solar registry states
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:24 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 410
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
The probe stopped: initialize answered HTTP 410.
Posture changes
- Oct 29, 2026
- HTTP status of an anonymous initialize: 200 to 410
- tools/list served without credentials: yes to no
- Protocol version: 2025-06-18 to none
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 410; tools/list served without credentials: yes -> no; Protocol version: 2025-06-18 -> none.View diff
- HTTP status of an anonymous initialize: 200 to 410
- tools/list served without credentials: yes to no
- Protocol version: 2025-06-18 to none
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http greenlight https://solar.agentlookups.ai/mcpclaude mcp add --transport http greenlight https://solar.agentlookups.ai/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__greenlight__solar_states",
"mcp__greenlight__solar_law"
],
"ask": [],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as greenlight. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/ai.agentlookups/greenlight/verify?hash=fd07d22d2d8149d6bc7e51507ccaf5adaed896eb0aadd0caca386b50b42d9094" | jq -e '.changed == false'Pinned hash fd07d22d2d81, from Oct 21, 2026, 18:39 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/ai.agentlookups/greenlight/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/ai.agentlookups/greenlight)Source: MCP Registry. Synced Oct 26, 2026, 21:17 UTC.
GreenLight - Plug-in Solar Law Registry MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the GreenLight - Plug-in Solar Law Registry MCP server safe?
- No scan can promise that. What its definitions show: 2 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.
Can the GreenLight - Plug-in Solar Law Registry MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the GreenLight - Plug-in Solar Law Registry MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the GreenLight - Plug-in Solar Law Registry MCP server have?
- 2 tools: 2 read. solar_states and solar_law.
Does the GreenLight - Plug-in Solar Law Registry MCP server need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the GreenLight - Plug-in Solar Law Registry MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the GreenLight - Plug-in Solar Law Registry MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Oct 21, 2026.