io.github.WillHeadlee/lgl-mcp-server
NPM · LGL-MCP-SERVER · SCANNED SEP 20
MCP server for Little Green Light CRM. Search donors, log gifts, manage groups and contacts.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 122 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 4558 tokens (~33/item across 137 items; 137 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage75
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 24% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 25 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_constituent" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 137 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.WillHeadlee/lgl-mcp-server server?
io.github.WillHeadlee/lgl-mcp-server runs locally as an npm package, launched with npx -y lgl-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · lgl-mcp-server
claude mcp add willheadlee-lgl-mcp-server -- npx -y lgl-mcp-server
{
"mcpServers": {
"willheadlee-lgl-mcp-server": {
"command": "npx",
"args": [
"-y",
"lgl-mcp-server"
]
}
}
} {
"servers": {
"willheadlee-lgl-mcp-server": {
"command": "npx",
"args": [
"-y",
"lgl-mcp-server"
]
}
}
} codex mcp add willheadlee-lgl-mcp-server -- npx -y lgl-mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"willheadlee-lgl-mcp-server": {
"type": "local",
"command": [
"npx",
"-y",
"lgl-mcp-server"
],
"enabled": true
}
}
} openclaw mcp add willheadlee-lgl-mcp-server --command npx --arg -y --arg lgl-mcp-server
mcp_servers:
willheadlee-lgl-mcp-server:
command: "npx"
args: ["-y", "lgl-mcp-server"] {
"McpServers": {
"willheadlee-lgl-mcp-server": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"lgl-mcp-server"
]
}
}
} assistant mcp add willheadlee-lgl-mcp-server -t stdio -c npx -a -y lgl-mcp-server
{
"mcpServers": {
"willheadlee-lgl-mcp-server": {
"command": "npx",
"args": [
"-y",
"lgl-mcp-server"
]
}
}
} 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.
- 20 Sept 26 +1
- Security disclosure: unverified → fail ▼ functional
- 19 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
- 15 Sept 26 +1
- Security disclosure: unverified → fail ▼ functional
- 14 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 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 20 Sept 2026 · Analysed npm/lgl-mcp-server@1.0.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
add_constituent_to_group ~40
Add a constituent to a group (creates a group membership)
| Name | Type | Req | Description |
|---|---|---|---|
| constituent_id | number | yes | – |
| group_id | number | yes | – |
No output schema declared.
No examples provided.
add_keyword_to_constituent ~39
Assign a keyword (attribute/tag) to a constituent
| Name | Type | Req | Description |
|---|---|---|---|
| constituent_id | number | yes | – |
| keyword_id | number | yes | – |
No output schema declared.
No examples provided.
call_lgl_api ~90
Execute a custom LGL REST API request directly to any of the 141 supported endpoints. Use this as a complete backup tool.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | – | Optional JSON payload body for POST/PATCH |
| method | string | yes | HTTP Method |
| path | string | yes | Endpoint path (e.g. /constituents/1/memberships or /types/constituent_types) |
No output schema declared.
No examples provided.
constituents_missing_info ~30
Find constituents missing key contact information
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | – |
| missing | array | yes | – |
No output schema declared.
No examples provided.
create_address ~87
Add a street address to a constituent
| Name | Type | Req | Description |
|---|---|---|---|
| address_type | string | – | e.g. Home, Work, Seasonal |
| city | string | – | – |
| constituent_id | number | yes | – |
| country | string | – | – |
| is_primary | boolean | – | – |
| state | string | – | – |
| street | string | yes | – |
| zip | string | – | Postal / ZIP Code |
No output schema declared.
No examples provided.
create_appeal ~29
Create a new appeal
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| name | string | yes | – |
No output schema declared.
No examples provided.
create_appeal_request ~57
Create a new appeal request, either linked to an appeal or constituent
| Name | Type | Req | Description |
|---|---|---|---|
| appeal_id | number | yes | – |
| ask_amount | number | – | – |
| constituent_id | number | yes | – |
| segment_name | string | – | – |
No output schema declared.
No examples provided.
create_campaign ~28
Create a new fundraising campaign
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| name | string | yes | – |
No output schema declared.
No examples provided.
create_category ~21
Create a new custom category
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
No output schema declared.
No examples provided.
create_class_affiliation ~45
Add a class affiliation to a constituent
| Name | Type | Req | Description |
|---|---|---|---|
| class_affiliation_type_id | number | yes | – |
| class_year | number | – | – |
| constituent_id | number | yes | – |
No output schema declared.
No examples provided.
create_constituent ~98
Create a new constituent in LGL
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | – |
| constituent_type | string | – | – |
| string | – | Primary email address | |
| first_name | string | – | – |
| last_name | string | – | – |
| organization_name | string | – | – |
| phone | string | – | Primary phone number |
| state | string | – | – |
| street | string | – | – |
| zip | string | – | – |
No output schema declared.
No examples provided.
create_constituent_invitation ~58
Add a constituent to an event (creates an invitation record)
| Name | Type | Req | Description |
|---|---|---|---|
| constituent_id | number | yes | – |
| event_id | number | yes | – |
| invitation_status | string | – | e.g. Invited, RSVP, Attended |
No output schema declared.
No examples provided.
create_contact_report ~72
Create a new contact report nested under a constituent
| Name | Type | Req | Description |
|---|---|---|---|
| constituent_id | number | yes | – |
| contact_date | string | – | YYYY-MM-DD |
| contact_type | string | – | e.g. Phone, In Person, Email |
| subject | string | – | – |
| text | string | yes | Content of report |
No output schema declared.
No examples provided.
create_email_address ~54
Add an email address to a constituent
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
| constituent_id | number | yes | – |
| email_type | string | – | e.g. Personal, Work |
| is_primary | boolean | – | – |
No output schema declared.
No examples provided.
create_event ~38
Create a new event
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| event_date | string | – | YYYY-MM-DD |
| name | string | yes | – |
No output schema declared.
No examples provided.
create_event_invitation ~43
Add a constituent invitation directly inside an event
| Name | Type | Req | Description |
|---|---|---|---|
| constituent_id | number | yes | – |
| event_id | number | yes | – |
| invitation_status | string | – | – |
No output schema declared.
No examples provided.
create_fund ~28
Create a new fund
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| name | string | yes | – |
No output schema declared.
No examples provided.
create_group ~21
Create a new constituent group
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
No output schema declared.
No examples provided.
create_keyword ~32
Create a new keyword nested under a category
| Name | Type | Req | Description |
|---|---|---|---|
| category_id | number | yes | – |
| name | string | yes | – |
No output schema declared.
No examples provided.
create_membership ~56
Add a membership record to a constituent
| Name | Type | Req | Description |
|---|---|---|---|
| constituent_id | number | yes | – |
| end_date | string | – | YYYY-MM-DD |
| membership_level_id | number | yes | – |
| start_date | string | – | YYYY-MM-DD |
No output schema declared.
No examples provided.
create_membership_level ~23
Create a new membership level
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
No output schema declared.
No examples provided.
create_note ~71
Log a new note nested under a specific constituent
| Name | Type | Req | Description |
|---|---|---|---|
| constituent_id | number | yes | – |
| note_date | string | – | YYYY-MM-DD |
| note_type | string | – | e.g. Interaction, Email, Alert |
| subject | string | – | – |
| text | string | yes | Content of the note |
No output schema declared.
No examples provided.
create_phone_number ~58
Add a phone number to a constituent
| Name | Type | Req | Description |
|---|---|---|---|
| constituent_id | number | yes | – |
| is_primary | boolean | – | – |
| number | string | yes | – |
| phone_type | string | – | e.g. Mobile, Home, Work, Fax |
No output schema declared.
No examples provided.
create_relationship ~66
Create a relationship between two constituents (nested under the parent constituent)
| Name | Type | Req | Description |
|---|---|---|---|
| constituent_id | number | yes | The parent constituent |
| related_constituent_id | number | yes | The related constituent |
| relationship_type | string | yes | e.g. Spouse, Sibling, Child, Parent |
No output schema declared.
No examples provided.
create_volunteer_time ~53
Record volunteer hours nested under a constituent
| Name | Type | Req | Description |
|---|---|---|---|
| constituent_id | number | yes | – |
| description | string | – | – |
| hours | number | yes | Hours volunteered |
| volunteer_date | string | – | YYYY-MM-DD |
No output schema declared.
No examples provided.
create_web_address ~54
Add a web address to a constituent
| Name | Type | Req | Description |
|---|---|---|---|
| constituent_id | number | yes | – |
| url | string | yes | Website URL |
| web_address_type | string | – | e.g. Personal, Blog, LinkedIn, Twitter |
No output schema declared.
No examples provided.
delete_address ~26
Delete a street address record by Address ID
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | Address ID |
No output schema declared.
No examples provided.
delete_appeal ~23
Delete an appeal by ID
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | – |
No output schema declared.
No examples provided.
delete_appeal_request ~25
Delete an appeal request by ID
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | – |
No output schema declared.
No examples provided.
delete_campaign ~21
Delete a campaign by ID
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | – |
No output schema declared.
No examples provided.
delete_category ~22
Delete a custom category by ID
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | – |
No output schema declared.
No examples provided.
delete_class_affiliation ~25
Delete a class affiliation record by ID
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | – |
No output schema declared.
No examples provided.
delete_constituent ~24
Delete an existing constituent by ID
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | – |
No output schema declared.
No examples provided.
delete_contact_report ~23
Delete a contact report by ID
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | – |
No output schema declared.
No examples provided.
delete_email_address ~27
Delete an email address record by Email ID
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | Email ID |
No output schema declared.
No examples provided.
delete_event ~21
Delete an event by ID
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | – |
No output schema declared.
No examples provided.
delete_fund ~22
Delete a fund by ID
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | – |
No output schema declared.
No examples provided.
delete_gift ~27
Delete a specific gift record by Gift ID
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | Gift ID |
No output schema declared.
No examples provided.
delete_group ~20
Delete a constituent group
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | – |
No output schema declared.
No examples provided.
delete_invitation ~24
Delete an event invitation record by ID
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | – |
No output schema declared.
No examples provided.
delete_keyword ~22
Delete a keyword record by ID
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | – |
No output schema declared.
No examples provided.
delete_membership ~23
Delete a membership record by ID
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | – |
No output schema declared.
No examples provided.
delete_membership_level ~23
Delete membership level by ID
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | – |
No output schema declared.
No examples provided.
delete_note ~23
Delete a note record by Note ID
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | – |
No output schema declared.
No examples provided.
delete_phone_number ~27
Delete a phone number record by Phone ID
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | Phone ID |
No output schema declared.
No examples provided.
delete_relationship ~23
Delete a constituent relationship by Relationship ID
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | – |
No output schema declared.
No examples provided.
delete_volunteer_time ~25
Delete a volunteer time record by ID
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | – |
No output schema declared.
No examples provided.
delete_web_address ~29
Delete a web address record by Web Address ID
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | Web Address ID |
No output schema declared.
No examples provided.
get_appeal ~23
Get appeal details by ID
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | – |
No output schema declared.
No examples provided.
get_appeal_request ~27
Get details for an appeal request by ID
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | – |
No output schema declared.
No examples provided.
What is the io.github.WillHeadlee/lgl-mcp-server server?
io.github.WillHeadlee/lgl-mcp-server is listed in the public MCP registry as io.github.WillHeadlee/lgl-mcp-server. MCP server for Little Green Light CRM. Search donors, log gifts, manage groups and contacts. This page covers its npm package (lgl-mcp-server).
Is the io.github.WillHeadlee/lgl-mcp-server server safe to use?
io.github.WillHeadlee/lgl-mcp-server scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. 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 io.github.WillHeadlee/lgl-mcp-server server expose?
io.github.WillHeadlee/lgl-mcp-server exposes 137 tools: search_constituents, list_constituents, get_constituent, create_constituent, update_constituent, and 132 more. Their descriptions and schemas cost roughly 4,558 tokens of context every time the server is loaded.
Is the io.github.WillHeadlee/lgl-mcp-server server still maintained?
io.github.WillHeadlee/lgl-mcp-server is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.