Freshsales MCP by usefulapi
REMOTE · FRESHSALES.USEFULAPI.IO
Manage Freshsales contacts, accounts, deals, tasks and appointments; add notes.
Available components
Last scanned (1 hour ago)
Scores higher than 46% of remote servers
Reachable. Last reached 25 Oct 2026.
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 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 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
- 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 & 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 Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 31 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 32 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
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.
- 25 Oct 26 62
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 25 Oct 2026 · Probed https://freshsales.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 freshsales.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690, 57355 | 8, 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 | 302 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://freshsales.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://freshsales.usefulapi.io/.well-known/oauth-protected-resource/mcp" Protected resource metadata
| Document | https://freshsales.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://freshsales.usefulapi.io/mcp |
| Authorisation server | https://freshsales.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://freshsales.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/freshsales/ |
| http (plaintext) | http://freshsales.usefulapi.io/mcp | Inconclusive | 302 | http://freshsales.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 →
freshsales_create_account Create account ~297
WRITE: create an account (company). name is required. It may duplicate an existing company: search first (freshsales_search). POST /sales_accounts.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
freshsales_create_appointment Create appointment ~226
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.
| Name | Type | Req | Description |
|---|---|---|---|
| attendee_contact_ids | array | – | Contact ids attending. |
| attendee_user_ids | array | – | User ids (freshsales_list_owners) attending. |
| description | string | – | Details. |
| end_date | string | yes | End, ISO 8601 with a timezone; after from_date. |
| from_date | string | yes | 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 | yes | Appointment title. |
No output schema declared.
No examples provided.
freshsales_create_contact Create contact ~290
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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_. |
| 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. |
No output schema declared.
No examples provided.
freshsales_create_deal Create deal ~258
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.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | 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 | yes | Deal name. |
| owner_id | integer | – | Owner user id (freshsales_list_owners). |
| probability | integer | – | Win probability, 0-100. |
| sales_account_id | integer | yes | Company the deal belongs to. |
No output schema declared.
No examples provided.
freshsales_create_note Add note ~85
WRITE: add a note to a contact, account or deal. Visible to your team on the record. POST /notes.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | The note text. |
| target_id | integer | yes | Id of the contact, account or deal. |
| target_type | string | yes | What the record is attached to: Contact, SalesAccount (company) or Deal. |
No output schema declared.
No examples provided.
freshsales_create_task Create task ~159
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.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Details. |
| due_date | string | yes | Due date and time, ISO 8601 with a timezone, e.g. 2026-11-02T09:00:00Z. |
| owner_id | integer | yes | User who owns the task (freshsales_list_owners). |
| target_id | integer | yes | Id of the contact, account or deal. |
| target_type | string | yes | What the record is attached to: Contact, SalesAccount (company) or Deal. |
| title | string | yes | Task title. |
No output schema declared.
No examples provided.
freshsales_get_account Get account ~69
One account (company) by id with its fields, optionally with related records embedded (contacts, deals, tasks, appointments, owner...). GET /sales_accounts/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | integer | yes | Account (sales account) id. |
| include | array | – | Related records to embed. |
No output schema declared.
No examples provided.
freshsales_get_appointment Get appointment ~35
One appointment by id with its attendees. GET /appointments/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| appointment_id | integer | yes | Appointment id. |
No output schema declared.
No examples provided.
freshsales_get_contact Get contact ~71
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | integer | yes | Contact id. |
| include | array | – | Related records to embed. |
No output schema declared.
No examples provided.
freshsales_get_deal Get deal ~82
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| deal_id | integer | yes | Deal id. |
| include | array | – | Related records to embed. |
No output schema declared.
No examples provided.
freshsales_get_task Get task ~31
One task by id. GET /tasks/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| task_id | integer | yes | Task id. |
No output schema declared.
No examples provided.
freshsales_list_account_views List account views ~48
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
freshsales_list_accounts List accounts ~117
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Account view id (freshsales_list_account_views). |
No output schema declared.
No examples provided.
freshsales_list_appointments List appointments ~70
List appointments that are open (upcoming) or complete (one filter per call), with title, time, location and creator. GET /appointments.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | string | – | Which appointments to list. |
| page | integer | – | Page number, 1-based (25 records per page). |
No output schema declared.
No examples provided.
freshsales_list_contact_views List contact views ~60
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
freshsales_list_contacts List contacts ~128
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Contact view id (freshsales_list_contact_views). |
No output schema declared.
No examples provided.
freshsales_list_deal_pipelines List deal pipelines ~30
List the deal pipelines (id, name). GET /selector/deal_pipelines.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
freshsales_list_deal_stages List deal stages ~92
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.
| Name | Type | Req | Description |
|---|---|---|---|
| pipeline_id | integer | – | Pipeline id (freshsales_list_deal_pipelines); default pipeline when omitted. |
No output schema declared.
No examples provided.
freshsales_list_deal_views List deal views ~47
List the saved deal views of the account, e.g. 'Open Deals'. A view id is needed by freshsales_list_deals. GET /deals/filters.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
freshsales_list_deals List deals ~117
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Deal view id (freshsales_list_deal_views). |
No output schema declared.
No examples provided.
freshsales_list_options List option values ~100
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | yes | Which list of choices. |
No output schema declared.
No examples provided.
freshsales_list_owners List owners (users) ~40
List the users of the account (id and name). Use the id as owner_id when creating or updating records. GET /selector/owners.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
freshsales_list_sales_activities List sales activities ~66
List logged sales activities (calls, meetings, emails...) of the account. GET /sales_activities.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number, 1-based (25 records per page). |
| per_page | integer | – | Records per page (1-100). |
No output schema declared.
No examples provided.
freshsales_list_tasks List tasks ~78
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.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | string | – | Which tasks to list. |
| page | integer | – | Page number, 1-based (25 records per page). |
No output schema declared.
No examples provided.
freshsales_lookup Look up by exact field ~112
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.
| Name | Type | Req | Description |
|---|---|---|---|
| entity | string | – | Record type. |
| field | string | yes | Field to match: email, name, or a custom field name (cf_...). |
| value | string | yes | The exact value to find, e.g. jane@example.com. |
No output schema declared.
No examples provided.
freshsales_search Search records ~113
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.
| Name | Type | Req | Description |
|---|---|---|---|
| entity | string | – | Record type to search (singular). |
| per_page | integer | – | Results to return (1-100, default 10). |
| query | string | yes | Text to search for (name, email, ...). |
No output schema declared.
No examples provided.
freshsales_update_account Update account ~306
WRITE: change fields of an existing account (company); only the fields you pass are changed. PUT /sales_accounts/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | integer | yes | 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. |
No output schema declared.
No examples provided.
freshsales_update_contact Update contact ~292
WRITE: change fields of an existing contact; only the fields you pass are changed (passing sales_accounts replaces the associated companies). PUT /contacts/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Street address. |
| city | string | – | City. |
| contact_id | integer | yes | 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_. |
| 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. |
No output schema declared.
No examples provided.
freshsales_update_deal Update deal ~312
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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). |
No output schema declared.
No examples provided.
freshsales_update_note Update note ~47
WRITE: replace the text of an existing note. PUT /notes/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | The new note text. |
| note_id | integer | yes | Note id. |
No output schema declared.
No examples provided.
freshsales_update_task Update task ~122
WRITE: change a task: title, details, due date, owner, or mark it completed (status 1) or open (status 0). PUT /tasks/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Task id. |
| title | string | – | New title. |
No output schema declared.
No examples provided.
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.
remote · freshsales.usefulapi.io
claude mcp add --transport http io-usefulapi-freshsales 'https://freshsales.usefulapi.io/mcp'
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.