Freshsales MCP by usefulapi
MCP server · freshsales.usefulapi.io · found in a public list · checked since 2026-10-30
Live, handshake completed · latest check
Manages Freshsales CRM contacts, accounts, deals, appointments and notes.
Our summary of what its own text says it does: automated, not reviewed by a person (placement-ai/6). What this means
Placed in Manage CRM records: Read and update contacts, companies, deals, pipelines and tasks in a CRM.
https://freshsales.usefulapi.io/mcp MCP endpoint (Streamable HTTP)The name is the registry's label, not ours. Not reviewed by a person. See 496 endpoints from usefulapi.io.
Our checks
An unpaid request daily, from eastern North AmericaLast 1 checks, oldest to newest; room for 29 more
1 passed, 0 failed, 29 not run.
Checked daily. Daily: 5 to 99 payers, and every new service until it has been probed 3 times.
Response times
| Window | Checks | Timeouts | Median | 90th | 95th | 99th | Fastest | Slowest |
|---|---|---|---|---|---|---|---|---|
| 24 hourssince 2026-10-30 | 1 | 0 | — | — | — | — | — | — |
| 7 dayssince 2026-10-30 | 1 | 0 | — | — | — | — | — | — |
| 30 dayssince 2026-10-30 | 1 | 0 | — | — | — | — | — | — |
Milliseconds, from eastern North America, timing the whole MCP handshake (initialize to the tools/list answer). Timeouts count at the 10000 ms limit. A dash means too few checks for that figure. As of . Definitions and method.
Details
Tools listed by the server
freshsales_create_accountfreshsales_create_appointmentfreshsales_create_contactfreshsales_create_dealfreshsales_create_notefreshsales_create_taskfreshsales_get_accountfreshsales_get_appointmentfreshsales_get_contactfreshsales_get_dealfreshsales_get_taskfreshsales_list_account_viewsfreshsales_list_accountsfreshsales_list_appointmentsfreshsales_list_contact_viewsfreshsales_list_contactsfreshsales_list_deal_pipelinesfreshsales_list_deal_stagesfreshsales_list_deal_viewsfreshsales_list_dealsfreshsales_list_optionsfreshsales_list_ownersfreshsales_list_sales_activitiesfreshsales_list_tasksfreshsales_lookupfreshsales_searchfreshsales_update_accountfreshsales_update_contactfreshsales_update_dealfreshsales_update_notefreshsales_update_task
- Tools
- 31
- This list since
- 2026-10-30
- First listed to us
- 2026-10-30
- List changes, 90 days
- 0
Names as the server reported them at our latest completed handshake (mcp-handshake/2); a listed tool is not a tested one. Definitions
Access
- Our latest check
- Nothing asked
- Stated
- not stated
- Payment model
- not known
- Currency
- not known
"Nothing asked" describes one plain request, not every operation. Statements are claims, not our measurements. Definitions
Interface it declares
- Protocol
- MCP 2025-06-18
- Capabilities
- promptstools
- Transports
- streamable-http
As its initialize reply stated it at our check on (mcp-handshake/2): a claim, not tested. Definitions
Calls it declares
freshsales_list_contact_viewsfreshsales_list_contacts view_id* sort sort_type pagefreshsales_get_contact contact_id* includefreshsales_search query* entity per_pagefreshsales_lookup value* field* entityfreshsales_list_account_viewsfreshsales_list_accounts view_id* sort sort_type pagefreshsales_get_account account_id* includefreshsales_list_deal_viewsfreshsales_list_deals view_id* sort sort_type pagefreshsales_get_deal deal_id* includefreshsales_list_tasks filter page
From the tool list it returned to our check (request-shape/2). * marks a required parameter; after → the fields it says it returns. What it declares, not that a call works.
Listing
In the capability tree: Business and productivity / Customer records / Manage CRM records (primary). Placed by three checks by a small AI model: placed, found blind from its tasks, and verified against its own text (placement-ai/6, tree/3) on 2026-10-30. Wrong place? Tell us.
In the directory: meets our listing criteria (listing-criteria/6): ✓ says what it does; ✓ its latest check passed.
Recent probes
| When | Result | Time to headers |
|---|---|---|
cloudflare:EWR |
Live, handshake completed HTTP 200 | 986 ms |
What these figures do not show
- A passing check means the server completed the MCP handshake with us (initialize, then tools/list, with no credentials; mcp-handshake/2) or asked for credentials first (HTTP 401). It does not show that the server's tools work or what they return. Tool names are as the server listed them.
- Listed in the Official MCP Registry; this data comes from the Official MCP Registry. Its listing's description is not republished.
- Limited evidence: monitored for under 1 day (less than 30).
Something wrong here?
Operate this service and want it reviewed, corrected or removed? Email hello@agentservicedirectory.com or use the opt-out page. A wrong place in the tree? Tell us.
Machine-readable: /api/v1/services/cand_0116f2f3aebd1c47