Close Crm
NPM · @PIPEWORX/MCP-CLOSE-CRM · 2 COMPONENTS
Close CRM MCP Pack — wraps the Close (close.com) API v1.
Available components
Last scanned (1 hour ago)
Scores higher than 81% 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 Security100
- 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
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-close-crm). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 5 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 880 tokens (~146/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 31 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 0.2.0 → 0.2.1 functional
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 81
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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-close-crm@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-close-crm |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-close-crm/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3612113360 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:b44105e8d2ce4a97f2bce3e7fd3e22eb78e2123a471fcc551ea6741f77729292669e72b38eb2b05a11fcff0f87dbf07ac73647d54c48e2e1853af4118 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
close_get_lead ~81
Get a single lead by its Close lead ID (format `lead_...`). Returns full detail: display name, description, status, contacts, addresses, opportunities, custom fields, and timestamps.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Close API key |
| lead_id | string | yes | Close lead ID, e.g. `lead_abc123` |
No output schema declared.
No examples provided.
close_list_activities ~149
List activities for a lead — calls, emails, notes, SMS, meetings, and status changes. Returns a `data` array (with id, _type, type, date_created, and type-specific fields) plus `has_more` / `total_results`. Requires `lead_id`. Page with `_limit` / `_skip` to walk a lead's timeline.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Close API key |
| _limit | number | – | Results per page (default 100, max 200) |
| _skip | number | – | Number of results to skip for pagination (default 0) |
| lead_id | string | yes | Lead ID whose activity timeline to fetch |
No output schema declared.
No examples provided.
close_list_contacts ~138
List contacts (people) in Close. Returns a `data` array of contacts with id, lead_id, name, title, emails, and phones, plus `has_more` / `total_results`. Optionally filter to one lead with `lead_id`. Page with `_limit` / `_skip`.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Close API key |
| _limit | number | – | Results per page (default 100, max 200) |
| _skip | number | – | Number of results to skip for pagination (default 0) |
| lead_id | string | – | Optional lead ID to filter contacts to a single lead |
No output schema declared.
No examples provided.
close_list_opportunities ~152
List opportunities (pipeline deals) in Close. Returns a `data` array of opportunities with id, lead_id, status, value, currency, confidence, and expected close date, plus `has_more` / `total_results`. Pass `lead_id` to scope to one lead, or omit to list across the organization. Page with `_limit` / `_skip`.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Close API key |
| _limit | number | – | Results per page (default 100, max 200) |
| _skip | number | – | Number of results to skip for pagination (default 0) |
| lead_id | string | – | Optional lead ID to filter opportunities to a single lead |
No output schema declared.
No examples provided.
close_me ~71
Get the current Close user and organization for the supplied API key. Returns user ID, name, email, and the organizations (with IDs) the key can access. Use this to verify the key works and discover your organization context.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Close API key (Settings → API Keys) |
No output schema declared.
No examples provided.
close_search_leads ~235
Search or list leads (companies/accounts in Close) using Close's query language. Returns a `data` array of leads (with id, display_name, contacts, status, custom fields) plus `has_more` and `total_results`. The `query` param accepts Close search syntax, e.g. `name:"Acme"`, `status_label:"Potential"`, `email_address:@example.com`, `lead_created_within:7d`, or free text. Omit `query` to list all leads. Page with `_limit` (max 200) and `_skip`.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Close API key |
| _limit | number | – | Results per page (default 100, max 200) |
| _skip | number | – | Number of results to skip for pagination (default 0) |
| query | string | – | Close query string. Examples: `name:"Acme Inc"`, `status_label:"Potential"`, `email_address:@acme.com`, `lead_created_within:30d`. Free text also works. Omit to list all leads. |
No output schema declared.
No examples provided.
How do I install the Close Crm MCP server?
Close Crm runs locally as an npm package, launched with npx -y @pipeworx/mcp-close-crm. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-close-crm
claude mcp add pipeworx-io-close-crm -- npx -y @pipeworx/mcp-close-crm
What is the Close Crm MCP server?
Close Crm is an MCP server listed in the public MCP registry as io.github.pipeworx-io/close-crm. Close CRM MCP Pack, wraps the Close (close.com) API v1. This page covers its npm package (@pipeworx/mcp-close-crm).
Is the Close Crm MCP server safe to use?
Close Crm scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Close Crm MCP server expose?
Close Crm exposes 6 tools: close_me, close_search_leads, close_get_lead, close_list_opportunities, close_list_contacts, close_list_activities. Their descriptions and schemas cost roughly 826 tokens of context every time the server is loaded.
Is the Close Crm MCP server still maintained?
Close Crm is still listed as active in the MCP registry. We last reached this channel on 5 November 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 Close Crm MCP server under?
Close 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.