# RevDesk Product MCP (remote · mcp.revdesk.com)

Give AI agents secure access to RevDesk calling, SMS, phone numbers, caller IDs, and usage.

- Trust score: 81/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

> **Recent critical change**: Authorization (2026-08-24). See the changelog below before you install this server.

## Components

- remote · `mcp.revdesk.com`: 81/100 (this document), [markdown](https://verifymcp.io/servers/cell-labs-inc-revdesk-product/mcp.md), [page](https://verifymcp.io/servers/cell-labs-inc-revdesk-product/mcp)

## Channel facts

- Endpoint: `https://mcp.revdesk.com/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.1.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-09-21.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (send_sms).
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 84/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).
  - Tool/resource definitions use about 639 tokens (~58/item across 11 items; 10 tools + 1 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 93/100
  - Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).
  - Supports UI / widget rendering.

## Install

### How do I install the RevDesk Product MCP server?

RevDesk Product MCP is a hosted endpoint at https://mcp.revdesk.com/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 cell-labs-inc-revdesk-product 'https://mcp.revdesk.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "cell-labs-inc-revdesk-product": {
      "url": "https://mcp.revdesk.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cell-labs-inc-revdesk-product": {
      "type": "http",
      "url": "https://mcp.revdesk.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.cell-labs-inc-revdesk-product]
url = "https://mcp.revdesk.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cell-labs-inc-revdesk-product": {
      "type": "remote",
      "url": "https://mcp.revdesk.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add cell-labs-inc-revdesk-product --url 'https://mcp.revdesk.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  cell-labs-inc-revdesk-product:
    url: "https://mcp.revdesk.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "cell-labs-inc-revdesk-product": {
      "Transport": "http",
      "Url": "https://mcp.revdesk.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add cell-labs-inc-revdesk-product -t streamable-http -u 'https://mcp.revdesk.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "cell-labs-inc-revdesk-product": {
      "type": "http",
      "url": "https://mcp.revdesk.com/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-09-19 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-13 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-11 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-09 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-07 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-04 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (10)

### `send_sms` (~91 tokens)

Send SMS

Send a text message from one of the account's RevDesk phone numbers. Both numbers must be E.164 (+14155550123). Use list_phone_numbers to find a valid 'from' number.

Input parameters:

- `from` (string, required): One of the account's RevDesk numbers, E.164
- `message` (string, required): Message body
- `to` (string, required): Destination number in E.164 format

### `place_call` (~97 tokens)

Place a call

Place an outbound phone call from one of the account's RevDesk numbers to a destination. The call is bridged server-side (no audio flows through the AI). Returns a call id for status checks.

Input parameters:

- `from_number` (string, required): One of the account's RevDesk numbers, E.164
- `record` (boolean): Record the call (default true)
- `to_number` (string, required): Destination number in E.164 format

### `list_calls` (~58 tokens)

List call history

List recent calls with status, duration, and cost. Most recent first.

Input parameters:

- `limit` (integer): Max results (default 20)
- `status` (string): Filter by status, e.g. COMPLETED, FAILED, NO_ANSWER

### `get_call` (~37 tokens)

Get call details

Get the current status and details of a single call by id.

Input parameters:

- `call_id` (string, required): Call id from place_call or list_calls

### `hangup_call` (~32 tokens)

Hang up a call

Hang up an in-progress call by id.

Input parameters:

- `call_id` (string, required): Call id of an active call

### `list_phone_numbers` (~25 tokens)

List phone numbers

List the phone numbers owned by this account (usable as 'from' numbers).

### `search_available_numbers` (~76 tokens)

Search available numbers

Search phone numbers available for purchase, by area code or digit pattern.

Input parameters:

- `area_code` (string): 3-digit US area code
- `contains` (string): Digit pattern the number should contain
- `country` (string): ISO country code (default US)
- `limit` (integer): Max results (default 10)

### `buy_phone_number` (~88 tokens)

Buy a phone number

Purchase a phone number for this account. Provide an exact number from search_available_numbers, or just an area code to auto-pick. Billing applies to the RevDesk account.

Input parameters:

- `area_code` (string): 3-digit area code to pick from
- `name` (string): Display name for the number
- `phone_number` (string): Exact number to purchase, E.164

### `list_caller_ids` (~21 tokens)

List caller IDs

List verified caller IDs and their CNAM display names.

### `get_usage` (~25 tokens)

Get usage

Current-month usage rollup: calls placed, minutes used, active numbers, spend.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/cell-labs-inc-revdesk-product/mcp#diagnostics

## Score history

- 2026-09-21: 81
- 2026-09-20: 81
- 2026-09-19: 81
- 2026-09-18: 80
- 2026-09-17: 80
- 2026-09-16: 79
- 2026-09-15: 79
- 2026-09-14: 78
- 2026-09-13: 78
- 2026-09-12: 77
- 2026-09-11: 77
- 2026-09-10: 76
- 2026-09-09: 76
- 2026-09-08: 75
- 2026-09-07: 75
- 2026-09-06: 74
- 2026-09-05: 74
- 2026-09-04: 74
- 2026-09-03: 73
- 2026-09-02: 73
- 2026-09-01: 72
- 2026-08-31: 72
- 2026-08-30: 71
- 2026-08-29: 71
- 2026-08-28: 70
- 2026-08-27: 70
- 2026-08-26: 69
- 2026-08-25: 67
- 2026-08-24: 67
- 2026-08-23: 36

## Common questions

### What is the RevDesk Product MCP server?

RevDesk Product MCP is listed in the public MCP registry as io.github.cell-labs-inc/revdesk-product. Give AI agents secure access to RevDesk calling, SMS, phone numbers, caller IDs, and usage. This page covers its hosted endpoint (https://mcp.revdesk.com/mcp).

### Is the RevDesk Product MCP server safe to use?

RevDesk Product MCP scores 81 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 RevDesk Product MCP server expose?

RevDesk Product MCP exposes 10 tools: send_sms, place_call, list_calls, get_call, hangup_call, and 5 more. Their descriptions and schemas cost roughly 550 tokens of context every time the server is loaded.

### Does the RevDesk Product MCP server require authentication?

No. We connected to RevDesk Product MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the RevDesk Product MCP server still maintained?

RevDesk Product MCP is still listed as active in the MCP registry. We last reached this channel on 21 September 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://mcp.revdesk.com/mcp
- Authorisation metadata: https://mcp.revdesk.com/.well-known/oauth-protected-resource/mcp
- Website: https://www.revdesk.com/developers
- Changelog RSS feed: https://verifymcp.io/servers/cell-labs-inc-revdesk-product/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/cell-labs-inc-revdesk-product/mcp.json
- HTML version of this page: https://verifymcp.io/servers/cell-labs-inc-revdesk-product/mcp