Sellinger CRM
NPM · SELLINGER-MCP
Manage Sellinger AI SDR CRM leads, conversations and pipeline from any MCP client.
Available components
Last scanned (4 hours ago)
Scores higher than 36% of npm servers
Category CRM and Sales
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 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- 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 12 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1248 tokens (~83/item across 15 items; 15 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 86% 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 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "send_message" implies "send" 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 15 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 14 Oct 26 +29
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: 0 functional
- First check of Schema quality: pass functional
- First check of Schema quality: good functional
- First check of Tool coverage: 86 functional
- 12 Oct 26 0
- Malware scan: unverified → pass ▲ security
- 11 Oct 26 +15
The score moved with no change recorded against any check. We would rather say so than guess.
- 7 Oct 26 18
First indexed and scored.
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 18 Oct 2026 · Analysed npm/sellinger-mcp@0.1.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 92 packages
| Packages resolved | 92 |
|---|---|
| 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 →
create_lead ~147
Create a new lead in the CRM. Returns the newly created lead record.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | Lead's company or organization |
| string | – | Lead's email address | |
| first_name | string | yes | Lead's first name |
| last_name | string | yes | Lead's last name |
| linkedin_url | string | – | URL to the lead's LinkedIn profile |
| notes | string | – | Free-form notes about the lead |
| phone | string | – | Lead's phone number |
| source | string | – | How the lead was acquired (e.g. "mcp", "manual", "linkedin") |
| title | string | – | Lead's job title |
No output schema declared.
No examples provided.
get_agent ~28
Get a single agent by UUID including configs and channels.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Agent UUID |
No output schema declared.
No examples provided.
get_analytics ~44
Retrieve a KPI summary including total leads, conversion rate, response rate, and pipeline distribution.
| Name | Type | Req | Description |
|---|---|---|---|
| period | string | – | Time period for analytics. Defaults to "30d". |
No output schema declared.
No examples provided.
get_hot_leads ~19
Get high-intent leads from intent signals.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_lead ~40
Retrieve a single lead by its UUID. Returns the full lead record with all fields.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The UUID of the lead to retrieve |
No output schema declared.
No examples provided.
get_pipeline_counts ~16
Get lead counts per pipeline stage.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_agents ~17
List all Sellinger agents for the team.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_approvals ~56
List pending approvals (messages, actions, suggestions).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | – |
| channel | string | – | – |
| limit | number | – | – |
| status | string | – | Filter by status (default: pending) |
No output schema declared.
No examples provided.
list_companies ~36
List companies in the CRM.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | – |
| offset | number | – | – |
| search | string | – | – |
No output schema declared.
No examples provided.
list_leads ~130
List leads from the CRM with optional filters. Returns a paginated array of leads.
| Name | Type | Req | Description |
|---|---|---|---|
| page | number | – | Page number (1-based). Defaults to 1. |
| per_page | number | – | Number of results per page (max 100). Defaults to 25. |
| search | string | – | Search query to filter leads by name, company, or email |
| stage | string | – | Filter by pipeline stage name or ID |
| status | string | – | Filter by lead status (e.g. "NEW", "ENGAGED", "CONVERTED", "IRRELEVANT") |
No output schema declared.
No examples provided.
list_segments ~40
List all segments (saved lead filters/groups) in the CRM.
| Name | Type | Req | Description |
|---|---|---|---|
| include_counts | boolean | – | Whether to include lead counts per segment. Defaults to false. |
No output schema declared.
No examples provided.
opt_out_lead ~133
Record that a person asked us to stop contacting them. This is the SUPPORTED way to honour an opt-out: it writes a person-level do-not-contact record for every identifier on the lead (email, phone, LinkedIn) AND fences the lead, in one transaction. Prefer this over update_lead(takeover_source='opt_out'), which only labels one lead row and gates nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | UUID of the lead who asked us to stop |
| reason | string | – | Optional short note for the record, e.g. the words they used. Defaults to 'unsubscribed'. |
No output schema declared.
No examples provided.
search_leads ~74
Full-text search across all lead fields. More powerful than list_leads search parameter.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum number of results to return (max 50). Defaults to 10. |
| query | string | yes | Search query. Matches against name, company, email, title, notes, and other text fields. |
No output schema declared.
No examples provided.
send_message ~74
Send a message to a lead via a specified channel (email, linkedin, whatsapp).
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | Message body / content |
| channel | string | yes | Communication channel to use |
| lead_id | string | yes | UUID of the lead to message |
| subject | string | – | Message subject (required for email) |
No output schema declared.
No examples provided.
update_lead ~394
Update fields on an existing lead. Only provided fields will be changed. Do NOT update the updated_at field. To RELEASE a lead a human took over, send human_takeover=false. To record that the person asked us to stop, prefer the opt_out tool/endpoint over setting takeover_source here — a takeover_source label is per-lead and anyone can overwrite it, whereas an opt-out must also be recorded person-level.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | Updated company |
| string | – | Updated email | |
| full_name | string | – | Updated full name |
| human_takeover | boolean | – | Whether a human owns this conversation. true fences the lead from ALL automated outbound; false RELEASES it back to the agent. This is a mute as well as a consent fence. |
| id | string | yes | UUID of the lead to update |
| notes | string | – | Updated notes |
| phone | string | – | Updated phone |
| pipeline_stage | string | – | Name of the pipeline stage to move the lead to (not a UUID) |
| status | string | – | New status (e.g. "NEW", "ENGAGED", "CONVERTED") |
| takeover_source | string|null | – | WHO raised the fence that is currently in effect: 'user' (someone on your side), 'worker' (this product's automation), 'opt_out' (the person asked us to stop). This is a LABEL and gates nothing here… |
| title | string | – | Updated job title |
No output schema declared.
No examples provided.
How do I install the Sellinger CRM MCP server?
Sellinger CRM runs locally as an npm package, launched with npx -y sellinger-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 · sellinger-mcp
claude mcp add ai-sellinger-mcp-server -- npx -y sellinger-mcp
What is the Sellinger CRM MCP server?
Sellinger CRM is an MCP server listed in the public MCP registry as ai.sellinger/mcp-server. Manage Sellinger AI SDR CRM leads, conversations and pipeline from any MCP client. This page covers its npm package (sellinger-mcp).
Is the Sellinger CRM MCP server safe to use?
Sellinger CRM scores 62 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 18 October 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 Sellinger CRM MCP server expose?
Sellinger CRM exposes 15 tools: list_leads, get_lead, create_lead, update_lead, opt_out_lead, and 10 more. Their descriptions and schemas cost roughly 1,248 tokens of context every time the server is loaded.
Is the Sellinger CRM MCP server still maintained?
Sellinger CRM is still listed as active in the MCP registry. We last reached this channel on 18 October 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 Sellinger CRM MCP server under?
Sellinger CRM declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.