RevDesk Product MCP
REMOTE · MCP.REVDESK.COM · SCANNED SEP 20
Give AI agents secure access to RevDesk calling, SMS, phone numbers, caller IDs, and usage.
Available components
Recent critical change
Authorization (24 Aug 2026). See the changelog before you install this server.
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (send_sms). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability84
- 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
- Tool/resource definitions use about 639 tokens (~58/item across 11 items; 10 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
- Supports UI / widget rendering.Pass
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.
remote · mcp.revdesk.com
claude mcp add --transport http cell-labs-inc-revdesk-product 'https://mcp.revdesk.com/mcp'
{
"mcpServers": {
"cell-labs-inc-revdesk-product": {
"url": "https://mcp.revdesk.com/mcp"
}
}
} {
"servers": {
"cell-labs-inc-revdesk-product": {
"type": "http",
"url": "https://mcp.revdesk.com/mcp"
}
}
} [mcp_servers.cell-labs-inc-revdesk-product] url = "https://mcp.revdesk.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"cell-labs-inc-revdesk-product": {
"type": "remote",
"url": "https://mcp.revdesk.com/mcp",
"enabled": true
}
}
} openclaw mcp add cell-labs-inc-revdesk-product --url 'https://mcp.revdesk.com/mcp' --transport streamable-http
mcp_servers:
cell-labs-inc-revdesk-product:
url: "https://mcp.revdesk.com/mcp" {
"McpServers": {
"cell-labs-inc-revdesk-product": {
"Transport": "http",
"Url": "https://mcp.revdesk.com/mcp"
}
}
} assistant mcp add cell-labs-inc-revdesk-product -t streamable-http -u 'https://mcp.revdesk.com/mcp'
{
"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.
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.
- 19 Sept 26 +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.
- 17 Sept 26 +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.
- 15 Sept 26 +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.
- 13 Sept 26 +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.
- 11 Sept 26 +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.
- 9 Sept 26 +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.
- 7 Sept 26 +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.
- 4 Sept 26 +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.
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 20 Sept 2026 · Probed https://mcp.revdesk.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.revdesk.com | CN=YR2,O=Let's Encrypt,C=US | 29 Aug 2026 | 27 Nov 2026 | RSA 2048 | SHA256-RSA | 6e67b789b53a50b0f057f06d3105c9c3f02 |
| SANs: *.revdesk.com, revdesk.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.revdesk.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| revdesk.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.revdesk.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.revdesk.com/mcp | HTTPS enforced | 308 | https://mcp.revdesk.com/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 →
buy_phone_number Buy a phone number ~88
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
get_call Get call details ~37
Get the current status and details of a single call by id.
| Name | Type | Req | Description |
|---|---|---|---|
| call_id | string | yes | Call id from place_call or list_calls |
No output schema declared.
No examples provided.
get_usage Get usage ~25
Current-month usage rollup: calls placed, minutes used, active numbers, spend.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
hangup_call Hang up a call ~32
Hang up an in-progress call by id.
| Name | Type | Req | Description |
|---|---|---|---|
| call_id | string | yes | Call id of an active call |
No output schema declared.
No examples provided.
list_caller_ids List caller IDs ~21
List verified caller IDs and their CNAM display names.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_calls List call history ~58
List recent calls with status, duration, and cost. Most recent first.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results (default 20) |
| status | string | – | Filter by status, e.g. COMPLETED, FAILED, NO_ANSWER |
No output schema declared.
No examples provided.
list_phone_numbers List phone numbers ~25
List the phone numbers owned by this account (usable as 'from' numbers).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
place_call Place a call ~97
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.
| Name | Type | Req | Description |
|---|---|---|---|
| from_number | string | yes | One of the account's RevDesk numbers, E.164 |
| record | boolean | – | Record the call (default true) |
| to_number | string | yes | Destination number in E.164 format |
No output schema declared.
No examples provided.
search_available_numbers Search available numbers ~76
Search phone numbers available for purchase, by area code or digit pattern.
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
No output schema declared.
No examples provided.
send_sms Send SMS ~91
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.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | One of the account's RevDesk numbers, E.164 |
| message | string | yes | Message body |
| to | string | yes | Destination number in E.164 format |
No output schema declared.
No examples provided.
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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.