sellinger-mcp

MCPcommunity

v0.1.0UnknownMITUpdated 6d agonpm GitHub

MCP server exposing Sellinger CRM operations as tools

Works in

ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →

321Downloads/wk

6d agoLast update

Needs 1 credential before it runs

SELLINGER_API_KEYAPI keyrequired
Sellinger API key (sk_live_...) from Settings → Integrations → API Keys

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package

AuthorUnknown

LicenseMIT

Version0.1.0

Sourcenpm+mcp-registry

npmsellinger-mcp

GitHubasenlevov/sellinger.ai

SBOMCycloneDX 1.6 ↓

Trust Status

B

60/100Good

✓Listed in Forge index+10/10

—Publisher identity verified+0/20

→ Publisher: run `forge publish` from the package repo to claim ownership

—Ed25519 publish signature+0/5

→ Included automatically when the publisher runs `forge publish`

—Domain verification+0/5

→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }

—npm Trusted Publishing (Sigstore)+0/5

→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo

—npm maintainer match+0/5

→ Earned once your identity is verified above and that login is an npm maintainer of this package

✓CVE scan · clean+30/30

✓Static analysis · clean+20/20

Paste into Claude Code, Cursor, or any AI assistant to fix all gaps

StatusCommunity-indexed

PublisherUnverified

SignatureUnsigned

Domain—

Provenance—

Dependencies✓ 60 resolved+ · none vulnerable

Tool surface15 tools · none privileged

Security scan✓ Cleanv0.1.0 · 1d agoHow well does this scan work?

EvalsNone

IndexedOct 6, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

15 tools · none privileged

Statically extracted from the published packagev0.1.0 · 1d ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

Filter toolsPrivileged only

list_leadsList leads from the CRM with optional filters. Returns a paginated array of leads.

List leads from the CRM with optional filters. Returns a paginated array of leads.

No input schema was published for this tool.

get_leadRetrieve a single lead by its UUID. Returns the full lead record with all fields.

Retrieve a single lead by its UUID. Returns the full lead record with all fields.

No input schema was published for this tool.

create_leadCreate a new lead in the CRM. Returns the newly created lead record.

Create a new lead in the CRM. Returns the newly created lead record.

No input schema was published for this tool.

update_leadUpdate fields on an existing lead. Only provided fields will be changed. Do NOT update the updated_at field.

Update fields on an existing lead. Only provided fields will be changed. Do NOT update the updated_at field.

No input schema was published for this tool.

opt_out_leadRecord that a person asked us to stop contacting them. This is the SUPPORTED way to honour

Record that a person asked us to stop contacting them. This is the SUPPORTED way to honour

No input schema was published for this tool.

send_messageSend a message to a lead via a specified channel (email, linkedin, whatsapp).

Send a message to a lead via a specified channel (email, linkedin, whatsapp).

No input schema was published for this tool.

list_segmentsList all segments (saved lead filters/groups) in the CRM.

List all segments (saved lead filters/groups) in the CRM.

No input schema was published for this tool.

get_analyticsRetrieve a KPI summary including total leads, conversion rate, response rate, and pipeline distribution.

Retrieve a KPI summary including total leads, conversion rate, response rate, and pipeline distribution.

No input schema was published for this tool.

search_leadsFull-text search across all lead fields. More powerful than list_leads search parameter.

Full-text search across all lead fields. More powerful than list_leads search parameter.

No input schema was published for this tool.

list_agentsList all Sellinger agents for the team.

List all Sellinger agents for the team.

No input schema was published for this tool.

get_agentGet a single agent by UUID including configs and channels.

Get a single agent by UUID including configs and channels.

No input schema was published for this tool.

list_approvalsList pending approvals (messages, actions, suggestions).

List pending approvals (messages, actions, suggestions).

No input schema was published for this tool.

get_pipeline_countsGet lead counts per pipeline stage.

Get lead counts per pipeline stage.

No input schema was published for this tool.

list_companiesList companies in the CRM.

List companies in the CRM.

No input schema was published for this tool.

get_hot_leadsGet high-intent leads from intent signals.

Get high-intent leads from intent signals.

No input schema was published for this tool.

15 of 15 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

MCP server exposing Sellinger CRM operations as tools

Keywords

mcpmodelcontextprotocolcrmsellinger

Alternatives

Comparing tool surfaces…

Tools exposed

15 tools · none privileged · observed 2026-10-10 by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

Dependency tree

What one Forge scan resolved from npm metadata on 2026-10-10 — observed resolution, not a publisher declaration.

60 packages resolved · 1 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

@modelcontextprotocol/sdk1.32.117 dependencies
- ajv8.20.04 dependencies
  - fast-deep-equal3.1.3
  - fast-uri3.1.8
  - json-schema-traverse1.0.0
  - require-from-string2.0.2
- zod4.6.5
- cors2.8.62 dependencies
  - object-assign4.1.1
  - vary1.1.2
- hono4.13.13
- jose6.2.12
- express5.3.0+27 not drawn1 dependency
  - vary1.1.2shown above
- raw-body3.0.2+4 not drawn
- ajv-formats3.0.11 dependency
  - ajv8.20.0shown above
- cross-spawn7.0.6+3 not drawn
- eventsource3.0.71 dependency
  - eventsource-parser3.1.1
- content-type1.0.5
- pkce-challenge5.0.1
- @hono/node-server2.1.4
- json-schema-typed8.0.2
- eventsource-parser3.1.1shown above
- express-rate-limit8.7.1+2 not drawn
- zod-to-json-schema3.25.2

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

54 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

package cap reached: 49
below the depth cap: 5

wrappy 1 — required by once@1.4.0package cap reached
http-errors ^2.0.1 — required by send@1.2.1package cap reached
mime-types ^3.0.2 — required by send@1.2.1package cap reached
ms ^2.1.3 — required by send@1.2.1package cap reached
on-finished ^2.4.1 — required by send@1.2.1package cap reached
range-parser ^1.2.1 — required by send@1.2.1package cap reached
statuses ^2.0.2 — required by send@1.2.1package cap reached
ms ^2.1.3 — required by debug@4.4.3package cap reached
debug ^4.4.0 — required by router@2.2.0package cap reached
depd ^2.0.0 — required by router@2.2.0package cap reached
is-promise ^4.0.0 — required by router@2.2.0package cap reached
parseurl ^1.3.3 — required by router@2.2.0package cap reached

+42 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.