io.usefulapi/pipedrive

REMOTE · PIPEDRIVE.USEFULAPI.IO · SCANNED AUG 3

Read deals, persons, organizations, activities and pipelines; create and update CRM records.

Available components

69 69 Trust /100

Trust breakdown (6 categories)

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 →

Endpoint Security78

The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
HTTPS not yet verified: we couldn't determine whether a plaintext access path exists. 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
The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial

Transport & Reachability100

Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass

Schema Quality & AI Usability70

AI-judged instruction clarity (excellent).Pass
Context-footprint check failed: tool/resource definitions use about 2713 tokens (~142/item across 19 items; 19 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 Management3

Stability observed for 1 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

Capabilities60

Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · pipedrive.usefulapi.io

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add --transport http io-usefulapi-pipedrive https://pipedrive.usefulapi.io/mcp

# ~/.codex/config.toml

[mcp_servers.io-usefulapi-pipedrive]
url = "https://pipedrive.usefulapi.io/mcp"

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-pipedrive": {
      "type": "remote",
      "url": "https://pipedrive.usefulapi.io/mcp",
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add io-usefulapi-pipedrive --url https://pipedrive.usefulapi.io/mcp --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  io-usefulapi-pipedrive:
    url: "https://pipedrive.usefulapi.io/mcp"

// mcp.json

{
  "mcpServers": {
    "io-usefulapi-pipedrive": {
      "type": "http",
      "url": "https://pipedrive.usefulapi.io/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

3 Aug 26 +1
- Stability: unverified → 0.03 ▲ functional
2 Aug 26 +50
- Authorization: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- First check of Authorization: partial security
- MCP protocol: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: excellent functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 100 functional
- First check of Schema quality: fail functional
1 Aug 26 18

First indexed and scored.

Show 1 earlier entry Hide earlier entries

Diagnostics

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 3 Aug 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	1 Aug 2026	30 Oct 2026	ECDSA 256	ECDSA-SHA256	3d45e7a3262544ea138d84a55a9e7c39
SANs: usefulapi.io, pipedrive.usefulapi.io, *.pipedrive.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

DNSSEC insecure

Validation of pipedrive.usefulapi.io. — Not signed

Zone	DS	Keys	Algorithms	Outcome
.	trust_anchor	20326, 38696	8, 8	Verified
io.	present	57355	8	Verified
usefulapi.io.	absent			Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation

Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result	Enforced and verified
Enforced	On tool calls
HTTP status	200

WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://pipedrive.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"

Bearer realm="OAuth", resource_metadata="https://pipedrive.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"

Protected resource metadata

Document	https://pipedrive.usefulapi.io/.well-known/oauth-protected-resource/mcp
Retrieved	Yes
Resource	https://pipedrive.usefulapi.io/mcp
Authorisation server	https://pipedrive.usefulapi.io

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://pipedrive.usefulapi.io/mcp	Verified	200
http (plaintext)	http://pipedrive.usefulapi.io/mcp	Inconclusive	401

MCP tools — 19 exposed · ~2,713 tokens

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.

Tool Tokens

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

Name	Type	Req	Description
email	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 Output Examples

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}.

Input Output Examples

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}.

Input Output Examples

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}.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

1 Aug 3 Aug