Home / MCP registry index / io.usefulapi/little-green-light
Little Green Light MCP by usefulapi
io.usefulapi/little-green-light in the official MCP registry.
Endpoint https://little-green-light.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.
The registry describes it as: Search Little Green Light donors, gifts, notes and memberships, and add gifts and contact reports.
We read its 20 tools on 2026-10-26. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
lgl_search_constituents lgl_get_constituent lgl_list_constituent_gifts lgl_search_gifts lgl_get_gift lgl_list_constituent_notes lgl_list_constituent_contact_reports lgl_list_constituent_memberships lgl_list_appeals lgl_list_campaigns lgl_list_funds lgl_list_events lgl_list_groups lgl_list_team_members lgl_list_type_values lgl_create_constituent lgl_update_constituent lgl_create_gift lgl_create_note lgl_create_contact_report
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-usefulapi-little-green-light)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.