io.github.dylanc1317-create/leadcloser-mcp
NPM · @DYLANC1317/LEADCLOSER-MCP · SCANNED SEP 29
Manage leads and insights for NZ trade businesses via LeadCloser AI.
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 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- 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
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 175 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 340 tokens (~68/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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.dylanc1317-create/leadcloser-mcp server?
io.github.dylanc1317-create/leadcloser-mcp runs locally as an npm package, launched with npx -y @dylanc1317/leadcloser-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @dylanc1317/leadcloser-mcp
claude mcp add dylanc1317-create-leadcloser-mcp -- npx -y @dylanc1317/leadcloser-mcp
{
"mcpServers": {
"dylanc1317-create-leadcloser-mcp": {
"command": "npx",
"args": [
"-y",
"@dylanc1317/leadcloser-mcp"
]
}
}
} {
"servers": {
"dylanc1317-create-leadcloser-mcp": {
"command": "npx",
"args": [
"-y",
"@dylanc1317/leadcloser-mcp"
]
}
}
} codex mcp add dylanc1317-create-leadcloser-mcp -- npx -y @dylanc1317/leadcloser-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dylanc1317-create-leadcloser-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@dylanc1317/leadcloser-mcp"
],
"enabled": true
}
}
} openclaw mcp add dylanc1317-create-leadcloser-mcp --command npx --arg -y --arg @dylanc1317/leadcloser-mcp
mcp_servers:
dylanc1317-create-leadcloser-mcp:
command: "npx"
args: ["-y", "@dylanc1317/leadcloser-mcp"] {
"McpServers": {
"dylanc1317-create-leadcloser-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@dylanc1317/leadcloser-mcp"
]
}
}
} assistant mcp add dylanc1317-create-leadcloser-mcp -t stdio -c npx -a -y @dylanc1317/leadcloser-mcp
{
"mcpServers": {
"dylanc1317-create-leadcloser-mcp": {
"command": "npx",
"args": [
"-y",
"@dylanc1317/leadcloser-mcp"
]
}
}
} 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.
- 29 Sept 26 +1
- Stability: 0.97 → pass security
- 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
- 27 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 −3
- Stability: pass → 0.80 functional
- 22 Sept 26 +1
- Stability: 0.97 → pass security
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 18 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.
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 29 Sept 2026 · Analysed npm/@dylanc1317/leadcloser-mcp@1.0.1
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 93 packages
| Packages resolved | 93 |
|---|---|
| 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 →
leadcloser_add_note Add Note to Lead ~44
Add or update a private note on a lead.
| Name | Type | Req | Description |
|---|---|---|---|
| lead_id | string | yes | The lead's ID |
| note | string | yes | The note to add |
No output schema declared.
No examples provided.
leadcloser_create_lead Create Lead ~96
Manually add a new lead to LeadCloser.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | Lead's email address | |
| initial_message | string | – | Initial message or notes about the lead |
| name | string | yes | Lead's full name |
| phone | string | – | Lead's phone number |
| service_requested | string | – | Service the lead is interested in |
| source | string | – | Where the lead came from |
No output schema declared.
No examples provided.
leadcloser_get_insights Get Insights ~44
Get performance insights — total leads, close rate, average score, and best lead source.
| Name | Type | Req | Description |
|---|---|---|---|
| period_days | integer | – | Number of days to look back |
No output schema declared.
No examples provided.
leadcloser_get_leads Get Leads ~83
Get recent leads from LeadCloser. Returns lead name, phone, service, score, status and outcome.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Number of leads to return |
| outcome | string | – | Filter by outcome: won, lost, no_show, in_progress |
| status | string | – | Filter by status: new, qualifying, quoted, won |
No output schema declared.
No examples provided.
leadcloser_update_outcome Update Lead Outcome ~73
Mark a lead as won, lost, or no-show. Optionally record the job value if won.
| Name | Type | Req | Description |
|---|---|---|---|
| job_value | number | – | Job value in NZD if outcome is won |
| lead_id | string | yes | The lead's ID |
| outcome | string | yes | The outcome to set |
No output schema declared.
No examples provided.
What is the io.github.dylanc1317-create/leadcloser-mcp server?
io.github.dylanc1317-create/leadcloser-mcp is listed in the public MCP registry as io.github.dylanc1317-create/leadcloser-mcp. Manage leads and insights for NZ trade businesses via LeadCloser AI. This page covers its npm package (@dylanc1317/leadcloser-mcp).
Is the io.github.dylanc1317-create/leadcloser-mcp server safe to use?
io.github.dylanc1317-create/leadcloser-mcp scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 29 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.dylanc1317-create/leadcloser-mcp server expose?
io.github.dylanc1317-create/leadcloser-mcp exposes 5 tools: leadcloser_get_leads, leadcloser_create_lead, leadcloser_update_outcome, leadcloser_add_note, leadcloser_get_insights. Their descriptions and schemas cost roughly 340 tokens of context every time the server is loaded.
Is the io.github.dylanc1317-create/leadcloser-mcp server still maintained?
io.github.dylanc1317-create/leadcloser-mcp is still listed as active in the MCP registry. We last reached this channel on 29 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.dylanc1317-create/leadcloser-mcp server under?
io.github.dylanc1317-create/leadcloser-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.