Revamp CRM MCP by usefulapi
REMOTE · REVAMP-CRM.USEFULAPI.IO
Read Revamp CRM contacts, deals, notes and orders; create and update contacts, deals and notes.
Available components
Last scanned (5 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 25 Oct 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 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 Usability75
- 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 3595 tokens (~189/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 Coverage90
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 70% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 19 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 20 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
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 +1
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.0.0 → 1.0.3 functional
- 24 Oct 26 60
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://revamp-crm.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 revamp-crm.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://revamp-crm.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://revamp-crm.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://revamp-crm.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://revamp-crm.usefulapi.io/mcp |
| Authorisation server | https://revamp-crm.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://revamp-crm.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/revamp-crm/ |
| http (plaintext) | http://revamp-crm.usefulapi.io/mcp | Inconclusive | 302 | http://revamp-crm.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 →
revampcrm_add_note Add note to a contact or deal ~97
WRITE: add a note to a contact or a deal timeline in Revamp CRM. It is an internal note: nothing is sent to the contact. Adding twice creates two notes. POST /Notes/{Contact|Deal}/{id}/Add.
| Name | Type | Req | Description |
|---|---|---|---|
| entity_id | string | yes | The contact id or deal id. |
| entity_type | string | yes | What the note is attached to. |
| text | string | yes | The note text. |
No output schema declared.
No examples provided.
revampcrm_count_orders Count e-commerce orders ~66
How many orders Revamp CRM has synced for one store. GET /Orders/Count/{provider}/{store}.
| Name | Type | Req | Description |
|---|---|---|---|
| provider | string | yes | Store provider, e.g. "Shopify". |
| store | string | yes | Store name / domain as Revamp CRM stores it. |
No output schema declared.
No examples provided.
revampcrm_create_contact Create contact ~405
WRITE: create a new contact (person or organization) in the Revamp CRM account. It does not email or message the contact. Search first (revampcrm_list_contacts with keyword/email) so you do not create a duplicate: this tool does not check. Returns Revamp CRM's import result (status, message, the new id in ImportingIntoId). POST /Contacts/New.
| Name | Type | Req | Description |
|---|---|---|---|
| address_line1 | string | – | – |
| address_line2 | string | – | – |
| assigned_user_id | string | – | Id of the Revamp CRM user who owns the contact (revampcrm_get_current_user returns your own). |
| city | string | – | – |
| contact_source | string | – | – |
| contact_stage | string | – | A contact stage name (see revampcrm_list_contact_stages). |
| contact_type | string | – | Contact type as Revamp CRM names it (see an existing contact). |
| country | string | – | Country as Revamp CRM stores it (code or name; see an existing contact). |
| custom_fields | object | – | Custom fields by Revamp property name, e.g. {"CustomField1": "Gold", "CustomField101": 42}. revampcrm_list_custom_fields explains what each one means. |
| description | string | – | About / description text. |
| gender | string | – | – |
| name | string | yes | Full name of the contact (or of the organization). |
| organization | string | – | Company name. |
| postal_code | string | – | – |
| primary_email | string | – | – |
| primary_phone | string | – | – |
| secondary_email | string | – | – |
| secondary_phone | string | – | – |
| state | string | – | – |
| subscribed | string | – | Marketing email subscription state. |
| tags | string | – | Tags, comma separated. On an update this REPLACES the contact's tags. |
| title | string | – | Job title. |
| website | string | – | – |
No output schema declared.
No examples provided.
revampcrm_create_deal Create deal ~297
WRITE: create a new deal (opportunity) in the Revamp CRM account, optionally linked to a contact. It does not message anyone. Use revampcrm_list_deals_by_stage (CurrentStages) for valid stage names and revampcrm_list_deal_currencies for currencies. POST /Deals.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | string | – | Contact the deal belongs to. |
| currency | string | – | Currency, e.g. USD. |
| deal_source | string | – | – |
| deal_stage | string | yes | Stage name in the pipeline (required by Revamp CRM; see revampcrm_list_deals_by_stage CurrentStages). |
| expected_close_date | string | – | Expected closing date, e.g. 2026-12-31. |
| name | string | yes | Deal name. |
| note | string | – | Note stored with the deal. |
| owner_user_id | string | – | Revamp CRM user id of the deal owner. |
| pipeline | string | – | Pipeline name (default pipeline if omitted). |
| probability | number | – | Win probability in percent. |
| product | string | – | – |
| sales_region | string | – | – |
| status | string | – | Deal status as existing deals show it (see revampcrm_list_deals). Default "Open". |
| tags | string | – | Tags, comma separated. |
| value | number | yes | Deal value in `currency` (required by Revamp CRM). |
No output schema declared.
No examples provided.
revampcrm_get_contact Get contact ~88
One contact by id with full details: contact info, address, tags, stage, custom fields, owner, previous/next task, deal totals (won/lost/open per currency), e-commerce order summary and order details. GET /Contacts/GetSingleContact/{id}/true.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | string | yes | Revamp CRM contact id (_id from revampcrm_list_contacts). |
No output schema declared.
No examples provided.
revampcrm_get_current_user Get current user ~50
The Revamp CRM user the credentials belong to: id, name, email and role. Use the id as owner_user_id / assigned_user_id. GET /User/WhoAmI.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
revampcrm_get_note Get note ~55
One note or timeline entry by id: text/message, type, author, related contact and deal, created date. GET /Notes/getNote/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| note_id | string | yes | Revamp CRM note id. |
No output schema declared.
No examples provided.
revampcrm_get_order Get e-commerce order ~134
One synced e-commerce order (Shopify, WooCommerce, BigCommerce ...) by the store's own order id: totals, tax, discount, shipping, financial and shipping status, line items and customer. Needs the provider name and store name exactly as Revamp CRM stores them (see ExternalProviders / Shop on a contact). GET /Orders/Get/{provider}/{store}/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | string | yes | The order id in the store. |
| provider | string | yes | Store provider, e.g. "Shopify". |
| store | string | yes | Store name / domain as Revamp CRM stores it. |
No output schema declared.
No examples provided.
revampcrm_list_contact_deals List a contact's deals ~56
All deals of one contact (name, stage, status, value, currency, expected closing date, owner). GET /Contacts/{id}/Deals.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | string | yes | Revamp CRM contact id. |
No output schema declared.
No examples provided.
revampcrm_list_contact_stages List contact stages ~44
The contact (lead) stage names configured in the account, in order. Use them as contact_stage filters and values. GET /Account/ContactStage.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
revampcrm_list_contacts List or search contacts ~394
Search and list contacts (people and organizations), newest filters first. With no filter it lists all contacts. Each item has name, organization, email/phone (ContactInfo), tags, stage, owner, last-contacted info and e-commerce order summary. resultsInfo carries totalCount and hasNext/nextIndex: pass nextIndex as `page` for the next page. GET /Contacts.
| Name | Type | Req | Description |
|---|---|---|---|
| added_from | string | – | Created on or after this date. |
| added_to | string | – | Created on or before this date. |
| assigned_user_id | string | – | Only contacts owned by this user id. |
| city | string | – | – |
| contact_source | string | – | – |
| contact_stage | string | – | Only contacts in this stage (see revampcrm_list_contact_stages). |
| contact_type | string | – | – |
| country | string | – | – |
| deal_stage | string | – | Only contacts that have a deal in this stage. |
| string | – | Only contacts with this email value. | |
| gender | string | – | – |
| has_deals | boolean | – | true = only contacts with deals. |
| is_customer | boolean | – | true = only customers (contacts with orders). |
| keyword | string | – | Free-text search (name, email, organization ...). |
| page | integer | – | Page index as in the previous reply's resultsInfo.nextIndex (default: the first page). |
| pagesize | integer | – | Contacts per page, 1-100 (default 25). |
| phone | string | – | Only contacts with this phone number. |
| sort_by | string | – | Field to sort by (e.g. name, createdon, updatedon). |
| sort_direction | string | – | – |
| state | string | – | – |
| subscribed | integer | – | Subscription filter as Revamp CRM numbers it. |
| tags | string | – | Only contacts with this tag. |
No output schema declared.
No examples provided.
revampcrm_list_custom_fields List contact custom fields ~67
The contact custom fields defined in the account: CustomFieldName (the property name, e.g. CustomField3), DisplayName, Type and list options. Read this to interpret CustomFieldN values on contacts and to set them. GET /Account/getAccountCustomFields.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
revampcrm_list_deal_currencies List deal currencies ~37
The currencies that deals in this account can use (name, value, symbol). GET /Account/DealCurrencies.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
revampcrm_list_deals List deals ~346
List deals with optional filters (status, pipeline, owner, contact, currency, created / expected-closing / closed date ranges). Each deal has name, stage, status, value, probability, forecasted sale, expected closing date, contact, owner and tags. The deal endpoints have no paging: the reply is cut to `limit` and says how many matched. GET /Deals/List.
| Name | Type | Req | Description |
|---|---|---|---|
| closed_from | string | – | Closed (won/lost) on or after this date. |
| closed_to | string | – | Closed (won/lost) on or before this date. |
| contact_id | string | – | Only deals of this contact. |
| created_from | string | – | Created on or after this date. |
| created_to | string | – | Created on or before this date. |
| currency | string | – | Currency, e.g. USD (see revampcrm_list_deal_currencies). |
| expected_close_from | string | – | Expected closing date on or after this date. |
| expected_close_to | string | – | Expected closing date on or before this date. |
| limit | integer | – | Show at most this many deals, 1-200 (default 50). The reply says how many matched in total. |
| owner_user_id | string | – | Only deals owned by this Revamp CRM user id. |
| pipeline | string | – | Pipeline name. |
| sort_by | string | – | Field to sort by (e.g. Value, CreatedOn, ExpectedClosureDate). |
| sort_direction | string | – | – |
| status | string | – | Deal status filter as existing deals show it, e.g. "Open", "Won" or "Lost". |
No output schema declared.
No examples provided.
revampcrm_list_deals_by_stage List deals grouped by stage ~308
The deal pipeline board: deals grouped by stage (with the stage names in CurrentStages). Same filters as revampcrm_list_deals. At most `limit` deals are shown per stage. GET /Deals/ByStage.
| Name | Type | Req | Description |
|---|---|---|---|
| closed_from | string | – | Closed (won/lost) on or after this date. |
| closed_to | string | – | Closed (won/lost) on or before this date. |
| contact_id | string | – | Only deals of this contact. |
| created_from | string | – | Created on or after this date. |
| created_to | string | – | Created on or before this date. |
| currency | string | – | Currency, e.g. USD (see revampcrm_list_deal_currencies). |
| expected_close_from | string | – | Expected closing date on or after this date. |
| expected_close_to | string | – | Expected closing date on or before this date. |
| limit | integer | – | Show at most this many deals per stage, 1-200 (default 50). |
| owner_user_id | string | – | Only deals owned by this Revamp CRM user id. |
| pipeline | string | – | Pipeline name. |
| sort_by | string | – | Field to sort by (e.g. Value, CreatedOn, ExpectedClosureDate). |
| sort_direction | string | – | – |
| status | string | – | Deal status filter as existing deals show it, e.g. "Open", "Won" or "Lost". |
No output schema declared.
No examples provided.
revampcrm_mark_deal_lost Mark deal lost ~112
WRITE: mark a deal as Lost in Revamp CRM with a reason (its status changes and it counts in lost-deal reports). It does not message the contact. Check the deal first with revampcrm_search_deals. POST /Deals/Lost.
| Name | Type | Req | Description |
|---|---|---|---|
| deal_id | string | yes | Revamp CRM deal id (_id or DealId of a deal). |
| note | string | – | Optional note stored with the change. |
| reason | string | yes | Why the deal was lost. |
No output schema declared.
No examples provided.
revampcrm_mark_deal_won Mark deal won ~97
WRITE: mark a deal as Won in Revamp CRM (its status changes and it counts in won-deal reports). It does not message the contact. Check the deal first with revampcrm_search_deals. POST /Deals/Won.
| Name | Type | Req | Description |
|---|---|---|---|
| deal_id | string | yes | Revamp CRM deal id (_id or DealId of a deal). |
| note | string | – | Optional note stored with the change. |
No output schema declared.
No examples provided.
revampcrm_search_deals Search deals ~247
Search deals by name, status, stage, contact, owner, pipeline, product, sales region or deal source (text match as Revamp CRM defines it). Revamp CRM applies `limit` itself and gives no total: may_have_more is true when a full page came back. GET /Deals/Search.
| Name | Type | Req | Description |
|---|---|---|---|
| contact | string | – | Contact name. |
| deal_source | string | – | – |
| deal_stage | string | – | – |
| expected_close_date | string | – | A date as Revamp CRM accepts it, e.g. 2026-10-31. |
| limit | integer | – | Show at most this many deals, 1-200 (default 50). The reply says how many matched in total. |
| name | string | – | Deal name (contains). |
| owner_name | string | – | Name of the deal owner. |
| pipeline | string | – | – |
| product | string | – | – |
| sales_region | string | – | – |
| sort_by | string | – | – |
| sort_direction | string | – | – |
| status | string | – | e.g. "Open", "Won", "Lost". |
| value | string | – | Deal value. |
No output schema declared.
No examples provided.
revampcrm_update_contact Update contact ~414
WRITE: change fields of an existing contact. Only the fields you pass change: the tool reads the stored contact first and sends it back with your changes (Revamp CRM's update replaces the whole record). `tags` replaces the contact's tags; passing a field overwrites its old value. It does not email or message the contact. PUT /Contacts/Edit.
| Name | Type | Req | Description |
|---|---|---|---|
| address_line1 | string | – | – |
| address_line2 | string | – | – |
| assigned_user_id | string | – | Id of the Revamp CRM user who owns the contact (revampcrm_get_current_user returns your own). |
| city | string | – | – |
| contact_id | string | yes | Revamp CRM contact id to update. |
| contact_source | string | – | – |
| contact_stage | string | – | A contact stage name (see revampcrm_list_contact_stages). |
| contact_type | string | – | Contact type as Revamp CRM names it (see an existing contact). |
| country | string | – | Country as Revamp CRM stores it (code or name; see an existing contact). |
| custom_fields | object | – | Custom fields by Revamp property name, e.g. {"CustomField1": "Gold", "CustomField101": 42}. revampcrm_list_custom_fields explains what each one means. |
| description | string | – | About / description text. |
| gender | string | – | – |
| name | string | – | Full name of the contact (or of the organization). |
| organization | string | – | Company name. |
| postal_code | string | – | – |
| primary_email | string | – | – |
| primary_phone | string | – | – |
| secondary_email | string | – | – |
| secondary_phone | string | – | – |
| state | string | – | – |
| subscribed | string | – | Marketing email subscription state. |
| tags | string | – | Tags, comma separated. On an update this REPLACES the contact's tags. |
| title | string | – | Job title. |
| website | string | – | – |
No output schema declared.
No examples provided.
How do I install the Revamp CRM MCP by usefulapi server?
Revamp CRM MCP by usefulapi is a hosted endpoint at https://revamp-crm.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 · revamp-crm.usefulapi.io
claude mcp add --transport http io-usefulapi-revamp-crm 'https://revamp-crm.usefulapi.io/mcp'
What is the Revamp CRM MCP by usefulapi server?
Revamp CRM MCP by usefulapi is listed in the public MCP registry as io.usefulapi/revamp-crm. Read Revamp CRM contacts, deals, notes and orders; create and update contacts, deals and notes. This page covers its hosted endpoint (https://revamp-crm.usefulapi.io/mcp).
Is the Revamp CRM MCP by usefulapi server safe to use?
Revamp CRM MCP by usefulapi scores 61 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 Revamp CRM MCP by usefulapi server expose?
Revamp CRM MCP by usefulapi exposes 19 tools: revampcrm_get_current_user, revampcrm_list_contact_stages, revampcrm_list_deal_currencies, revampcrm_list_custom_fields, revampcrm_list_contacts, and 14 more. Their descriptions and schemas cost roughly 3,314 tokens of context every time the server is loaded.
Does the Revamp CRM MCP by usefulapi server require authentication?
Yes. Revamp CRM 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 Revamp CRM MCP by usefulapi server still maintained?
Revamp CRM 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.