Pipedrive MCP by usefulapi
REMOTE · PIPEDRIVE.USEFULAPI.IO
Read deals, persons, organizations, activities and pipelines; create and update CRM records.
Available components
Last scanned (57 minutes ago)
Scores higher than 4% of remote servers
Reachable. Last reached 5 Nov 2026.
Category CRM and Sales
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. 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.
- 1 Nov 26 −61
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 31 Oct 26 +3
- Authorization: partial → pass ▲ security
- MCP protocol: fail → pass ▲ functional
- New prompt “add_a_new_deal_or_contact” functional
- New prompt “find_unfinished_activities_and_due_dates” functional
- New prompt “get_the_full_picture_of_a_customer” functional
- New prompt “log_a_note_or_schedule_an_activity” functional
- New prompt “review_open_deals_by_pipeline_stage” functional
- New prompt “search_across_deals_people_and_more” functional
- MCP protocol version: 2025-06-18 → 2025-11-25 functional
- Server version: 1.31.0 → 1.33.0 functional
- Server version: 1.30.0 → 1.31.0 functional
- Server version: 1.29.2 → 1.30.0 functional
- 30 Oct 26 0
- Server version: 1.29.1 → 1.29.2 functional
- Server version: 1.29.0 → 1.29.1 functional
- 29 Oct 26 0
- Server version: 1.28.0 → 1.29.0 functional
- Server version: 1.27.0 → 1.28.0 functional
- 28 Oct 26 0
- Server version: 1.25.0 → 1.27.0 functional
- 27 Oct 26 0
- Stability: 0.97 → pass security
- Server version: 1.24.0 → 1.25.0 functional
- 26 Oct 26 0
- Stability: pass → 0.97 functional
- 25 Oct 26 0
- Server version: 1.23.0 → 1.24.0 functional
- Server version: 1.22.0 → 1.23.0 functional
- Server version: 1.21.3 → 1.22.0 functional
- Server version: 1.21.1 → 1.21.3 functional
- Server version: 1.21.0 → 1.21.1 functional
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 · Probed https://pipedrive.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of pipedrive.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 302 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://pipedrive.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/pipedrive/ |
| http (plaintext) | http://pipedrive.usefulapi.io/mcp | Inconclusive | 302 | http://pipedrive.usefulapi.io/mcp |
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 →
pipedrive_add_note Add note ~136
Add a note, linked to at least one of a deal/person/organization/lead. `content` is required (HTML or plain text). Uses v1 (v2 has no notes endpoint). Pipedrive REST: POST /api/v1/notes.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | Note body — HTML or plain text (required). |
| deal_id | integer | – | Attach to this deal id. |
| lead_id | string | – | Attach to this lead id (a UUID string). |
| org_id | integer | – | Attach to this organization id. |
| person_id | integer | – | Attach to this person id. |
No output schema declared.
No examples provided.
pipedrive_create_activity Create activity ~216
Create a new activity (task/event). `subject` is required; link it to a deal/person/org and set type/date/time as needed. Pipedrive REST: POST /api/v2/activities.
| Name | Type | Req | Description |
|---|---|---|---|
| deal_id | integer | – | Link to this deal id. |
| done | boolean | – | Whether the activity is already marked done. |
| due_date | string | – | Due date, yyyy-mm-dd. |
| due_time | string | – | Due time, HH:MM (24h). |
| duration | string | – | Duration, HH:MM. |
| note | string | – | Free-text note attached to the activity. |
| org_id | integer | – | Link to this organization id. |
| owner_id | integer | – | Assign to this owner (user) id. |
| person_id | integer | – | Link to this person id. |
| subject | string | yes | Activity subject/title (required). |
| type | string | – | Activity type key, e.g. 'call', 'meeting', 'task', 'email'. |
No output schema declared.
No examples provided.
pipedrive_create_deal Create deal ~213
Create a new deal. `title` is required; link it to a person/org/pipeline/stage/owner as needed. Pipedrive REST: POST /api/v2/deals.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | Currency code for `value`, e.g. 'USD'. |
| expected_close_date | string | – | Expected close date, yyyy-mm-dd. |
| org_id | integer | – | Link to this organization id. |
| owner_id | integer | – | Assign to this owner (user) id. |
| person_id | integer | – | Link to this person id. |
| pipeline_id | integer | – | Place in this pipeline id. |
| stage_id | integer | – | Place in this stage id. |
| status | string | – | Deal status — 'open' (default), 'won' or 'lost'. |
| title | string | yes | Deal title (required). |
| value | number | – | Deal monetary value. |
| visible_to | integer | – | Visibility group id (Pipedrive visibility setting). |
No output schema declared.
No examples provided.
pipedrive_create_person Create person ~149
Create a new person (contact). `name` is required; `email`/`phone` are convenience strings mapped to Pipedrive's structured emails/phones arrays. Pipedrive REST: POST /api/v2/persons.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | Primary email address (mapped to the emails array). | |
| name | string | yes | Person full name (required). |
| org_id | integer | – | Link to this organization id. |
| owner_id | integer | – | Assign to this owner (user) id. |
| phone | string | – | Primary phone number (mapped to the phones array). |
| visible_to | integer | – | Visibility group id (Pipedrive visibility setting). |
No output schema declared.
No examples provided.
pipedrive_get_current_user Get current user ~41
Get the authenticated user's profile (name, email, company, locale, timezone). Pipedrive REST: GET /api/v1/users/me.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
pipedrive_get_deal Get deal ~46
Get a single deal by its id. Pipedrive REST: GET /api/v2/deals/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | Deal id (required). |
No output schema declared.
No examples provided.
pipedrive_get_organization Get organization ~46
Get a single organization by its id. Pipedrive REST: GET /api/v2/organizations/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | Organization id (required). |
No output schema declared.
No examples provided.
pipedrive_get_person Get person ~48
Get a single person (contact) by its id. Pipedrive REST: GET /api/v2/persons/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | Person id (required). |
No output schema declared.
No examples provided.
pipedrive_list_activities List activities ~208
List activities (tasks/events), optionally filtered by filter/owner/deal/person/org/done/updated_since. Pipedrive REST: GET /api/v2/activities.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Opaque pagination cursor from a previous response's `next_cursor`. |
| deal_id | integer | – | Filter by linked deal id. |
| done | boolean | – | Filter by completion — true for done, false for not done. |
| filter_id | integer | – | Filter by a saved filter id. |
| limit | integer | – | Max results to return (1–500, default 100). |
| org_id | integer | – | Filter by linked organization id. |
| owner_id | integer | – | Filter by owner (user) id. |
| person_id | integer | – | Filter by linked person id. |
| updated_since | string | – | Only activities updated after this RFC 3339 timestamp, e.g. '2024-01-01T00:00:00Z'. |
No output schema declared.
No examples provided.
pipedrive_list_deals List deals ~226
List deals, optionally filtered by filter/owner/person/org/pipeline/stage/status and sorted. Pipedrive REST: GET /api/v2/deals.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Opaque pagination cursor from a previous response's `next_cursor`. |
| filter_id | integer | – | Filter by a saved filter id. |
| limit | integer | – | Max results to return (1–500, default 100). |
| org_id | integer | – | Filter by linked organization id. |
| owner_id | integer | – | Filter by owner (user) id. |
| person_id | integer | – | Filter by linked person id. |
| pipeline_id | integer | – | Filter by pipeline id. |
| sort_by | string | – | Field to sort by — 'id', 'update_time' or 'add_time'. |
| sort_direction | string | – | Sort direction — 'asc' or 'desc'. |
| stage_id | integer | – | Filter by stage id. |
| status | string | – | Filter by deal status — 'open', 'won', 'lost' or 'deleted'. |
No output schema declared.
No examples provided.
pipedrive_list_notes List notes ~177
List notes, optionally filtered by user/deal/person/org/lead. Uses v1 (v2 has no notes endpoint) with start+limit pagination. Pipedrive REST: GET /api/v1/notes.
| Name | Type | Req | Description |
|---|---|---|---|
| deal_id | integer | – | Filter by linked deal id. |
| lead_id | string | – | Filter by linked lead id (a UUID string). |
| limit | integer | – | Max results to return (v1 limit). |
| org_id | integer | – | Filter by linked organization id. |
| person_id | integer | – | Filter by linked person id. |
| sort | string | – | Sort expression, e.g. 'add_time DESC'. |
| start | integer | – | Pagination offset (v1 start; default 0). |
| user_id | integer | – | Filter by the note author (user) id. |
No output schema declared.
No examples provided.
pipedrive_list_organizations List organizations ~145
List organizations, optionally filtered by filter/owner and sorted. Pipedrive REST: GET /api/v2/organizations.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Opaque pagination cursor from a previous response's `next_cursor`. |
| filter_id | integer | – | Filter by a saved filter id. |
| limit | integer | – | Max results to return (1–500, default 100). |
| owner_id | integer | – | Filter by owner (user) id. |
| sort_by | string | – | Field to sort by — 'id', 'update_time' or 'add_time'. |
| sort_direction | string | – | Sort direction — 'asc' or 'desc'. |
No output schema declared.
No examples provided.
pipedrive_list_persons List persons ~161
List persons (contacts), optionally filtered by filter/owner/org and sorted. Pipedrive REST: GET /api/v2/persons.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Opaque pagination cursor from a previous response's `next_cursor`. |
| filter_id | integer | – | Filter by a saved filter id. |
| limit | integer | – | Max results to return (1–500, default 100). |
| org_id | integer | – | Filter by linked organization id. |
| owner_id | integer | – | Filter by owner (user) id. |
| sort_by | string | – | Field to sort by — 'id', 'update_time' or 'add_time'. |
| sort_direction | string | – | Sort direction — 'asc' or 'desc'. |
No output schema declared.
No examples provided.
pipedrive_list_pipelines List pipelines ~108
List all pipelines. Pipedrive REST: GET /api/v2/pipelines.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Opaque pagination cursor from a previous response's `next_cursor`. |
| limit | integer | – | Max results to return (1–500, default 100). |
| sort_by | string | – | Field to sort by — 'id', 'update_time' or 'add_time'. |
| sort_direction | string | – | Sort direction — 'asc' or 'desc'. |
No output schema declared.
No examples provided.
pipedrive_list_stages List stages ~89
List stages, optionally restricted to a single pipeline. Pipedrive REST: GET /api/v2/stages.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Opaque pagination cursor from a previous response's `next_cursor`. |
| limit | integer | – | Max results to return (1–500, default 100). |
| pipeline_id | integer | – | Restrict to stages of this pipeline id. |
No output schema declared.
No examples provided.
pipedrive_search_deals Search deals ~193
Search deals by term across selected fields. Pipedrive REST: GET /api/v2/deals/search.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Opaque pagination cursor from a previous response's `next_cursor`. |
| exact_match | boolean | – | If true, only exact matches (case-insensitive) are returned. |
| fields | string | – | Comma-separated fields to search — any of 'custom_fields', 'notes', 'title'. |
| limit | integer | – | Max results to return (1–500, default 100). |
| organization_id | integer | – | Restrict to deals linked to this organization id. |
| person_id | integer | – | Restrict to deals linked to this person id. |
| status | string | – | Restrict to deals with this status — 'open', 'won' or 'lost'. |
| term | string | yes | Search term (at least 2 characters, required). |
No output schema declared.
No examples provided.
pipedrive_search_items Search items ~212
Global search across multiple item types (deals, persons, organizations, products, leads, files, etc.). Pipedrive REST: GET /api/v2/itemSearch.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Opaque pagination cursor from a previous response's `next_cursor`. |
| exact_match | boolean | – | If true, only exact matches (case-insensitive) are returned. |
| fields | string | – | Comma-separated fields to search within (depends on item types). |
| item_types | string | – | Comma-separated item types to search — any of 'deal', 'person', 'organization', 'product', 'lead', 'file', 'mail_attachment', 'project'. |
| limit | integer | – | Max results to return (1–500, default 100). |
| search_for_related_items | boolean | – | If true, also return items related to the matches (e.g. deals of a matched person). |
| term | string | yes | Search term (at least 2 characters, required). |
No output schema declared.
No examples provided.
pipedrive_search_organizations Search organizations ~138
Search organizations by term across selected fields. Pipedrive REST: GET /api/v2/organizations/search.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Opaque pagination cursor from a previous response's `next_cursor`. |
| exact_match | boolean | – | If true, only exact matches (case-insensitive) are returned. |
| fields | string | – | Comma-separated fields to search — any of 'address', 'custom_fields', 'name', 'notes'. |
| limit | integer | – | Max results to return (1–500, default 100). |
| term | string | yes | Search term (at least 2 characters, required). |
No output schema declared.
No examples provided.
pipedrive_search_persons Search persons ~161
Search persons (contacts) by term across selected fields. Pipedrive REST: GET /api/v2/persons/search.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Opaque pagination cursor from a previous response's `next_cursor`. |
| exact_match | boolean | – | If true, only exact matches (case-insensitive) are returned. |
| fields | string | – | Comma-separated fields to search — any of 'name', 'email', 'phone', 'notes', 'custom_fields'. |
| limit | integer | – | Max results to return (1–500, default 100). |
| organization_id | integer | – | Restrict to persons linked to this organization id. |
| term | string | yes | Search term (at least 2 characters, required). |
No output schema declared.
No examples provided.
How do I install the Pipedrive MCP by usefulapi server?
Pipedrive MCP by usefulapi is a hosted endpoint at https://pipedrive.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · pipedrive.usefulapi.io
claude mcp add --transport http io-usefulapi-pipedrive 'https://pipedrive.usefulapi.io/mcp'
What is the Pipedrive MCP by usefulapi server?
Pipedrive MCP by usefulapi is listed in the public MCP registry as io.usefulapi/pipedrive. Read deals, persons, organizations, activities and pipelines; create and update CRM records. This page covers its hosted endpoint (https://pipedrive.usefulapi.io/mcp).
Is the Pipedrive MCP by usefulapi server safe to use?
Pipedrive MCP by usefulapi scores 18 out of 100 on VerifyMCP. 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 Pipedrive MCP by usefulapi server expose?
Pipedrive MCP by usefulapi exposes 19 tools: pipedrive_list_deals, pipedrive_get_deal, pipedrive_search_deals, pipedrive_list_persons, pipedrive_get_person, and 14 more. Their descriptions and schemas cost roughly 2,713 tokens of context every time the server is loaded.
Does the Pipedrive MCP by usefulapi server require authentication?
Its publisher declares no required credentials for Pipedrive MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Pipedrive MCP by usefulapi server still maintained?
Pipedrive MCP by usefulapi 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.