VoiceDesk AI
REMOTE · VOICEDESKAI.ORG
AI voice receptionist for US service businesses: services, pricing, fit checks, demo requests.
Available components
Last scanned (18 hours ago)
Scores higher than 58% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Communication
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- 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 Usability62
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 636 tokens (~106/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 29 Oct 26 69
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 5 Nov 2026 · Probed https://voicedeskai.org/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=voicedeskai.org | CN=YR1,O=Let's Encrypt,C=US | 15 Oct 2026 | 13 Jan 2027 | RSA 2048 | SHA256-RSA | 6f37bc2d9b94ff513a0b547bc4993e2d8f7 |
| SANs: voicedeskai.org | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| 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 voicedeskai.org. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| org. | DS published | 725, 26974 | 8, 8 | Verified |
| voicedeskai.org. | No DS | 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; preload |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(self), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://voicedeskai.org/api/mcp | Verified | 200 | |
| http (plaintext) | http://voicedeskai.org/api/mcp | HTTPS enforced | 308 | https://voicedeskai.org/api/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 →
check_compatibility Check compatibility ~80
Check whether VoiceDesk AI fits a business: country, industry template, required capabilities (use capability ids from get_services) and, given expected monthly call minutes, the smallest suitable plan.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | – |
| expected_monthly_minutes | integer | – | – |
| industry | string | – | – |
| required_capabilities | array | – | – |
No output schema declared.
No examples provided.
create_demo_request Request a demo or partnership call ~160
Ask VoiceDesk AI to contact a US business for a receptionist demo (interest=receptionist_demo) or a partnership conversation (interest=partnership). Only with the owner's consent. Returns a tracking reference and a one-time status_token. Creates no account and no charge. Send an idempotency_key to make retries safe.
| Name | Type | Req | Description |
|---|---|---|---|
| best_time | string | – | – |
| business_name | string | yes | – |
| consent_to_contact | boolean | yes | – |
| contact_name | string | yes | – |
| string | – | – | |
| idempotency_key | string | – | – |
| industry | string | – | – |
| interest | string | – | – |
| message | string | – | – |
| partner_type | string | – | – |
| phone | string | yes | – |
No output schema declared.
No examples provided.
create_onboarding_request Prepare an onboarding request ~166
Prepare onboarding for a US business that wants VoiceDesk AI, with its owner's consent. VoiceDesk reviews it and sends the owner a signup link; the owner chooses and pays for a plan themselves. Creates no account, subscription, phone number or charge. Returns a tracking reference and a one-time status_token.
| Name | Type | Req | Description |
|---|---|---|---|
| business_name | string | yes | – |
| consent_to_contact | boolean | yes | – |
| contact_name | string | yes | – |
| string | yes | – | |
| expected_monthly_minutes | integer | – | – |
| idempotency_key | string | – | – |
| industry | string | – | – |
| message | string | – | – |
| phone | string | yes | – |
| plan_code | string | – | – |
| timezone | string | – | – |
| website | string | – | – |
No output schema declared.
No examples provided.
get_demo_status Get request status ~48
Current status of a demo, partnership or onboarding request, given its reference and the status_token returned when it was created.
| Name | Type | Req | Description |
|---|---|---|---|
| reference | string | yes | – |
| status_token | string | yes | – |
No output schema declared.
No examples provided.
get_pricing Get current pricing ~49
Current monthly plans from VoiceDesk AI's live plan catalog (USD): monthly price, one-time setup fee and included call minutes. Purchases happen only on voicedeskai.org by the business owner.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_services Get VoiceDesk AI services ~38
What VoiceDesk AI does: capabilities (available / guided / not available), supported industries, how onboarding works and what agents may and may not do.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the VoiceDesk AI MCP server?
VoiceDesk AI is a hosted endpoint at https://voicedeskai.org/api/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 · voicedeskai.org
claude mcp add --transport http mrronaldlewisjrre-voicedesk-ai-mcp 'https://voicedeskai.org/api/mcp'
What is the VoiceDesk AI MCP server?
VoiceDesk AI is an MCP server listed in the public MCP registry as io.github.mrronaldlewisjrRE/voicedesk-ai-mcp. AI voice receptionist for US service businesses: services, pricing, fit checks, demo requests. This page covers its hosted endpoint (https://voicedeskai.org/api/mcp).
Is the VoiceDesk AI MCP server safe to use?
VoiceDesk AI scores 72 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 VoiceDesk AI MCP server expose?
VoiceDesk AI exposes 6 tools: get_services, get_pricing, check_compatibility, create_demo_request, get_demo_status, create_onboarding_request. Their descriptions and schemas cost roughly 541 tokens of context every time the server is loaded.
Does the VoiceDesk AI MCP server require authentication?
No. We connected to VoiceDesk AI without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the VoiceDesk AI MCP server still maintained?
VoiceDesk AI is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the VoiceDesk AI MCP server?
VerifyMCP ran 13 checks on VoiceDesk AI, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.