# Freshsales MCP by usefulapi (remote · freshsales.usefulapi.io)

Manage Freshsales contacts, accounts, deals, tasks and appointments; add notes.

- Trust score: 62/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-25

## Components

- remote · `freshsales.usefulapi.io`: 62/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-freshsales/freshsales.md), [page](https://verifymcp.io/servers/io-usefulapi-freshsales/freshsales)

## Channel facts

- Endpoint: `https://freshsales.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-25.

- **Endpoint Security**: 78/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 80/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 4173 tokens (~134/item across 31 items; 31 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 31 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 32 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the Freshsales MCP by usefulapi server?

Freshsales MCP by usefulapi is a hosted endpoint at https://freshsales.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.

### Claude

```bash
claude mcp add --transport http io-usefulapi-freshsales 'https://freshsales.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-freshsales": {
      "url": "https://freshsales.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-freshsales": {
      "type": "http",
      "url": "https://freshsales.usefulapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usefulapi-freshsales]
url = "https://freshsales.usefulapi.io/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add io-usefulapi-freshsales --url 'https://freshsales.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-freshsales:
    url: "https://freshsales.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-freshsales": {
      "Transport": "http",
      "Url": "https://freshsales.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-freshsales -t streamable-http -u 'https://freshsales.usefulapi.io/mcp'
```

### Other

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

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-25 (score 62)

First indexed and scored.

## MCP tools (31)

### `freshsales_list_contact_views` (~60 tokens)

List contact views

List the saved contact views (filters) of the account, e.g. 'My Contacts', 'New Contacts', 'All Contacts'. A view id is needed by freshsales_list_contacts; ids differ per account. GET /contacts/filters.

### `freshsales_list_contacts` (~128 tokens)

List contacts

List the contacts in a view (get view_id from freshsales_list_contact_views), 25 per page with name, email, phone numbers, job title, lead score, open deals amount and last contacted. Pages: use next_page. GET /contacts/view/{view_id}.

Input parameters:

- `page` (integer): Page number, 1-based (25 records per page).
- `sort` (string): Sort field.
- `sort_type` (string): Sort direction (default: the view's own order).
- `view_id` (integer, required): Contact view id (freshsales_list_contact_views).

### `freshsales_get_contact` (~71 tokens)

Get contact

One contact by id with all its fields, optionally with related records embedded via include (notes, tasks, appointments, deals, sales_accounts, owner, sales_activities...). GET /contacts/{id}.

Input parameters:

- `contact_id` (integer, required): Contact id.
- `include` (array): Related records to embed.

### `freshsales_search` (~113 tokens)

Search records

Search by name/email text across one record type: contact, sales_account (company), deal or user. Returns id, type, name and email for the matches (up to per_page, default 10). Use the id with the get tools. GET /search.

Input parameters:

- `entity` (string): Record type to search (singular).
- `per_page` (integer): Results to return (1-100, default 10).
- `query` (string, required): Text to search for (name, email, ...).

### `freshsales_lookup` (~112 tokens)

Look up by exact field

Exact-match lookup of contacts, companies or deals by one field, e.g. a contact by email address. field is 'email' (contacts), 'name', or a custom field name (cf_...). Returns the full records. GET /lookup.

Input parameters:

- `entity` (string): Record type.
- `field` (string, required): Field to match: email, name, or a custom field name (cf_...).
- `value` (string, required): The exact value to find, e.g. jane@example.com.

### `freshsales_list_account_views` (~48 tokens)

List account views

List the saved account (company) views of the account, e.g. 'My Accounts'. A view id is needed by freshsales_list_accounts. GET /sales_accounts/filters.

### `freshsales_list_accounts` (~117 tokens)

List accounts

List the accounts (companies) in a view (view_id from freshsales_list_account_views), 25 per page, with name, location, open deals amount and last contacted. GET /sales_accounts/view/{view_id}.

Input parameters:

- `page` (integer): Page number, 1-based (25 records per page).
- `sort` (string): Sort field.
- `sort_type` (string): Sort direction (default: the view's own order).
- `view_id` (integer, required): Account view id (freshsales_list_account_views).

### `freshsales_get_account` (~69 tokens)

Get account

One account (company) by id with its fields, optionally with related records embedded (contacts, deals, tasks, appointments, owner...). GET /sales_accounts/{id}.

Input parameters:

- `account_id` (integer, required): Account (sales account) id.
- `include` (array): Related records to embed.

### `freshsales_list_deal_views` (~47 tokens)

List deal views

List the saved deal views of the account, e.g. 'Open Deals'. A view id is needed by freshsales_list_deals. GET /deals/filters.

### `freshsales_list_deals` (~117 tokens)

List deals

List the deals in a view (view_id from freshsales_list_deal_views), 25 per page, with name, amount, expected close, probability and age. GET /deals/view/{view_id}.

Input parameters:

- `page` (integer): Page number, 1-based (25 records per page).
- `sort` (string): Sort field.
- `sort_type` (string): Sort direction (default: the view's own order).
- `view_id` (integer, required): Deal view id (freshsales_list_deal_views).

### `freshsales_get_deal` (~82 tokens)

Get deal

One deal by id with amount, expected close, probability and ids of its stage, pipeline and owner, optionally with related records embedded (contacts, sales_account, deal_stage, owner, notes via sales_activities...). GET /deals/{id}.

Input parameters:

- `deal_id` (integer, required): Deal id.
- `include` (array): Related records to embed.

### `freshsales_list_tasks` (~78 tokens)

List tasks

List tasks by status filter: open, due_today, due_tomorrow, overdue or completed (one filter per call). Returns title, due date, owner and status. GET /tasks.

Input parameters:

- `filter` (string): Which tasks to list.
- `page` (integer): Page number, 1-based (25 records per page).

### `freshsales_get_task` (~31 tokens)

Get task

One task by id. GET /tasks/{id}.

Input parameters:

- `task_id` (integer, required): Task id.

### `freshsales_list_appointments` (~70 tokens)

List appointments

List appointments that are open (upcoming) or complete (one filter per call), with title, time, location and creator. GET /appointments.

Input parameters:

- `filter` (string): Which appointments to list.
- `page` (integer): Page number, 1-based (25 records per page).

### `freshsales_get_appointment` (~35 tokens)

Get appointment

One appointment by id with its attendees. GET /appointments/{id}.

Input parameters:

- `appointment_id` (integer, required): Appointment id.

### `freshsales_list_sales_activities` (~66 tokens)

List sales activities

List logged sales activities (calls, meetings, emails...) of the account. GET /sales_activities.

Input parameters:

- `page` (integer): Page number, 1-based (25 records per page).
- `per_page` (integer): Records per page (1-100).

### `freshsales_list_owners` (~40 tokens)

List owners (users)

List the users of the account (id and name). Use the id as owner_id when creating or updating records. GET /selector/owners.

### `freshsales_list_deal_pipelines` (~30 tokens)

List deal pipelines

List the deal pipelines (id, name). GET /selector/deal_pipelines.

### `freshsales_list_deal_stages` (~92 tokens)

List deal stages

List deal stages (id, name, deal_pipeline_id): those of the default pipeline, or of the pipeline given by pipeline_id. Use the id as deal_stage_id. GET /selector/deal_stages or /selector/deal_pipelines/{id}/deal_stages.

Input parameters:

- `pipeline_id` (integer): Pipeline id (freshsales_list_deal_pipelines); default pipeline when omitted.

### `freshsales_list_options` (~100 tokens)

List option values

List the configured choices (id and name) for a field: lead_sources, contact_statuses, lifecycle_stages, deal_types, deal_reasons, deal_products, deal_payment_statuses, territories, currencies, industry_types, business_types, campaigns, sales_activity_types, sales_activity_outcomes. Use the ids in the *_id fields of the write tools. GET /selector/{kind}.

Input parameters:

- `kind` (string, required): Which list of choices.

### `freshsales_create_contact` (~290 tokens)

Create contact

WRITE: create a contact. Freshsales requires an email or a mobile number. It may create a duplicate of an existing contact: search first (freshsales_lookup by email). POST /contacts.

Input parameters:

- `address` (string): Street address.
- `city` (string): City.
- `contact_status_id` (integer): Contact status id (freshsales_list_options contact_statuses).
- `country` (string): Country.
- `custom_field` (object): Custom field values keyed by field name, e.g. {"cf_is_active": true}. Field names start with cf_.
- `email` (string): Primary email address.
- `first_name` (string): First name.
- `job_title` (string): Job title.
- `last_name` (string): Last name.
- `lead_source_id` (integer): Lead source id (freshsales_list_options lead_sources).
- `lifecycle_stage_id` (integer): Lifecycle stage id (freshsales_list_options lifecycle_stages).
- `mobile_number` (string): Mobile number.
- `owner_id` (integer): Owner user id (freshsales_list_owners).
- `sales_accounts` (array): Companies the contact belongs to: [{id, is_primary}], at most 10, exactly one primary.
- `state` (string): State or region.
- `work_number` (string): Work phone number.
- `zipcode` (string): Postal code.

### `freshsales_update_contact` (~292 tokens)

Update contact

WRITE: change fields of an existing contact; only the fields you pass are changed (passing sales_accounts replaces the associated companies). PUT /contacts/{id}.

Input parameters:

- `address` (string): Street address.
- `city` (string): City.
- `contact_id` (integer, required): Contact id.
- `contact_status_id` (integer): Contact status id (freshsales_list_options contact_statuses).
- `country` (string): Country.
- `custom_field` (object): Custom field values keyed by field name, e.g. {"cf_is_active": true}. Field names start with cf_.
- `email` (string): Primary email address.
- `first_name` (string): First name.
- `job_title` (string): Job title.
- `last_name` (string): Last name.
- `lead_source_id` (integer): Lead source id (freshsales_list_options lead_sources).
- `lifecycle_stage_id` (integer): Lifecycle stage id (freshsales_list_options lifecycle_stages).
- `mobile_number` (string): Mobile number.
- `owner_id` (integer): Owner user id (freshsales_list_owners).
- `sales_accounts` (array): Companies the contact belongs to: [{id, is_primary}], at most 10, exactly one primary.
- `state` (string): State or region.
- `work_number` (string): Work phone number.
- `zipcode` (string): Postal code.

### `freshsales_create_account` (~297 tokens)

Create account

WRITE: create an account (company). name is required. It may duplicate an existing company: search first (freshsales_search). POST /sales_accounts.

Input parameters:

- `address` (string): Street address.
- `annual_revenue` (number): Annual revenue.
- `business_type_id` (integer): Business type id (freshsales_list_options business_types).
- `city` (string): City.
- `country` (string): Country.
- `custom_field` (object): Custom field values keyed by field name, e.g. {"cf_is_active": true}. Field names start with cf_.
- `industry_type_id` (integer): Industry id (freshsales_list_options industry_types).
- `name` (string, required): Company name.
- `number_of_employees`: Company size bucket code (not a headcount): 1 = 1-10, 11 = 11-50, 51 = 51-200, 201 = 201-500, 501 = 501-1000, 1001 = 1001-5000, 5001 = 5001-10000, 10001 = 10000+.
- `owner_id` (integer): Owner user id (freshsales_list_owners).
- `phone` (string): Phone number.
- `state` (string): State or region.
- `website` (string): Website.
- `zipcode` (string): Postal code.

### `freshsales_update_account` (~306 tokens)

Update account

WRITE: change fields of an existing account (company); only the fields you pass are changed. PUT /sales_accounts/{id}.

Input parameters:

- `account_id` (integer, required): Account (sales account) id.
- `address` (string): Street address.
- `annual_revenue` (number): Annual revenue.
- `business_type_id` (integer): Business type id (freshsales_list_options business_types).
- `city` (string): City.
- `country` (string): Country.
- `custom_field` (object): Custom field values keyed by field name, e.g. {"cf_is_active": true}. Field names start with cf_.
- `industry_type_id` (integer): Industry id (freshsales_list_options industry_types).
- `name` (string): Company name.
- `number_of_employees`: Company size bucket code (not a headcount): 1 = 1-10, 11 = 11-50, 51 = 51-200, 201 = 201-500, 501 = 501-1000, 1001 = 1001-5000, 5001 = 5001-10000, 10001 = 10000+.
- `owner_id` (integer): Owner user id (freshsales_list_owners).
- `phone` (string): Phone number.
- `state` (string): State or region.
- `website` (string): Website.
- `zipcode` (string): Postal code.

### `freshsales_create_deal` (~258 tokens)

Create deal

WRITE: create a deal. name, amount and sales_account_id are required; contact_ids attach existing contacts. Stage and pipeline default to the first of the default pipeline. POST /deals.

Input parameters:

- `amount` (number, required): Deal value in the account's default currency.
- `contact_ids` (array): Existing contact ids to attach to the deal.
- `custom_field` (object): Custom field values keyed by field name, e.g. {"cf_is_active": true}. Field names start with cf_.
- `deal_pipeline_id` (integer): Pipeline id (freshsales_list_deal_pipelines).
- `deal_stage_id` (integer): Stage id (freshsales_list_deal_stages).
- `deal_type_id` (integer): Deal type id (freshsales_list_options deal_types).
- `expected_close` (string): Expected close date, YYYY-MM-DD.
- `lead_source_id` (integer): Lead source id (freshsales_list_options lead_sources).
- `name` (string, required): Deal name.
- `owner_id` (integer): Owner user id (freshsales_list_owners).
- `probability` (integer): Win probability, 0-100.
- `sales_account_id` (integer, required): Company the deal belongs to.

### `freshsales_update_deal` (~312 tokens)

Update deal

WRITE: change fields of an existing deal, e.g. move it to another stage (deal_stage_id), change amount or expected close; only the fields you pass are changed. PUT /deals/{id}.

Input parameters:

- `add_contact_ids` (array): Existing contact ids to attach.
- `amount` (number): Deal value in the deal's own currency (a multi-currency account: freshsales_get_deal shows the deal's currency first when updating).
- `custom_field` (object): Custom field values keyed by field name, e.g. {"cf_is_active": true}. Field names start with cf_.
- `deal_id` (integer, required): Deal id.
- `deal_pipeline_id` (integer): Pipeline id (freshsales_list_deal_pipelines).
- `deal_stage_id` (integer): Stage id (freshsales_list_deal_stages).
- `deal_type_id` (integer): Deal type id (freshsales_list_options deal_types).
- `expected_close` (string): Expected close date, YYYY-MM-DD.
- `lead_source_id` (integer): Lead source id (freshsales_list_options lead_sources).
- `name` (string): Deal name.
- `owner_id` (integer): Owner user id (freshsales_list_owners).
- `probability` (integer): Win probability, 0-100.
- `remove_contact_ids` (array): Contact ids to detach from the deal.
- `sales_account_id` (integer): Company the deal belongs to (freshsales_search sales_account).

### `freshsales_create_note` (~85 tokens)

Add note

WRITE: add a note to a contact, account or deal. Visible to your team on the record. POST /notes.

Input parameters:

- `description` (string, required): The note text.
- `target_id` (integer, required): Id of the contact, account or deal.
- `target_type` (string, required): What the record is attached to: Contact, SalesAccount (company) or Deal.

### `freshsales_update_note` (~47 tokens)

Update note

WRITE: replace the text of an existing note. PUT /notes/{id}.

Input parameters:

- `description` (string, required): The new note text.
- `note_id` (integer, required): Note id.

### `freshsales_create_task` (~159 tokens)

Create task

WRITE: create a task (to-do) attached to a contact, account or deal. title, due_date, owner_id and the target are required. POST /tasks.

Input parameters:

- `description` (string): Details.
- `due_date` (string, required): Due date and time, ISO 8601 with a timezone, e.g. 2026-11-02T09:00:00Z.
- `owner_id` (integer, required): User who owns the task (freshsales_list_owners).
- `target_id` (integer, required): Id of the contact, account or deal.
- `target_type` (string, required): What the record is attached to: Contact, SalesAccount (company) or Deal.
- `title` (string, required): Task title.

### `freshsales_update_task` (~122 tokens)

Update task

WRITE: change a task: title, details, due date, owner, or mark it completed (status 1) or open (status 0). PUT /tasks/{id}.

Input parameters:

- `description` (string): New details.
- `due_date` (string): New due date and time, ISO 8601 with a timezone.
- `owner_id` (integer): New owner user id.
- `status`: 0 = open, 1 = completed.
- `task_id` (integer, required): Task id.
- `title` (string): New title.

### `freshsales_create_appointment` (~226 tokens)

Create appointment

WRITE: create an appointment (meeting) with a start and end, optionally attached to a contact, account or deal and with attendees. Attendees may be notified by Freshsales. POST /appointments.

Input parameters:

- `attendee_contact_ids` (array): Contact ids attending.
- `attendee_user_ids` (array): User ids (freshsales_list_owners) attending.
- `description` (string): Details.
- `end_date` (string, required): End, ISO 8601 with a timezone; after from_date.
- `from_date` (string, required): Start, ISO 8601 with a timezone, e.g. 2026-11-02T09:00:00Z.
- `location` (string): Location.
- `target_id` (integer): Id of the contact, account or deal (with target_type).
- `target_type` (string): What the record is attached to: Contact, SalesAccount (company) or Deal.
- `time_zone` (string): Time zone name, e.g. Europe/Prague.
- `title` (string, required): Appointment title.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-freshsales/freshsales#diagnostics

## Score history

- 2026-10-25: 62

## Common questions

### What is the Freshsales MCP by usefulapi server?

Freshsales MCP by usefulapi is listed in the public MCP registry as io.usefulapi/freshsales. Manage Freshsales contacts, accounts, deals, tasks and appointments; add notes. This page covers its hosted endpoint (https://freshsales.usefulapi.io/mcp).

### Is the Freshsales MCP by usefulapi server safe to use?

Freshsales MCP by usefulapi scores 62 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 Freshsales MCP by usefulapi server expose?

Freshsales MCP by usefulapi exposes 31 tools: freshsales_list_contact_views, freshsales_list_contacts, freshsales_get_contact, freshsales_search, freshsales_lookup, and 26 more. Their descriptions and schemas cost roughly 3,900 tokens of context every time the server is loaded.

### Does the Freshsales MCP by usefulapi server require authentication?

Yes. Freshsales MCP by usefulapi asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the Freshsales MCP by usefulapi server still maintained?

Freshsales MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 25 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://freshsales.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/freshsales/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-freshsales/freshsales.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-freshsales/freshsales.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-freshsales/freshsales