Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Assistable

REMOTE · API.ASSISTABLE.AI

Give any AI agent a phone: make and answer calls, get through phone menus, and send texts.

+1 this week 60 Trust /100

Last scanned (23 hours ago)

Scores higher than 43% of remote servers

Reachable. Last reached 4 Nov 2026.

Category Communication

Trust breakdown (7 categories)

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 Security57
Transport & Reachability100
Schema Quality & AI Usability55
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 1336 tokens (~83/item across 16 items; 16 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management12
  • Stability check failed: schema churn in the 7 days we've observed: 2 tool removals, 0 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage69
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 8% 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
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

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.

  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 8 to 12.

  • 1 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 0 to 2.

  • 30 Oct 26 −2
    • Stability: 0.03 → fail ▼ security
    • A breaking change shipped without a version bump: still 0.4.0 ▼ security
    • Tool “assistable_connect” was removed ▼ security
    • Tool “assistable_connect_finish” was removed ▼ security
    • Tool “assistable_signup” was removed ▼ security
    • Tool “assistable_signup_finish” was removed ▼ security
    • Tool coverage: 23% → 8% ▼ functional
    • Schema quality: 95 → 83 ▲ functional
  • 29 Oct 26 +1
    • Schema quality: 85 → 95 ▼ functional
    • Tool coverage: 11% → 23% ▲ functional
    • Stability: unverified → 0.03 ▲ functional
    • New tool “assistable_signup” functional
    • New tool “assistable_signup_finish” functional
  • 28 Oct 26 59

    First indexed and scored.

Diagnostics

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 4 Nov 2026 · Probed https://api.assistable.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=assistable.ai CN=YE2,O=Let's Encrypt,C=US 23 Oct 2026 21 Jan 2027 ECDSA 256 ECDSA-SHA384 56e95088ebf91b56b5a5b97ab214e6eae57
SANs: *.assistable.ai, assistable.ai
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.assistable.ai. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 1814, 3799 8, 8 Verified
assistable.ai. 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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.assistable.ai/mcp Verified 200
http (plaintext) http://api.assistable.ai/mcp HTTPS enforced 301 https://api.assistable.ai:443/mcp
MCP tools · 16 exposed · ~1,187 tokens

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 →

Tool Tokens
appointments_list ~59

List appointments in a subaccount within an optional date range.

NameTypeReqDescription
cursorstring––
endDatestring––
limitinteger––
startDatestring––
subAccountIdstringyes–

No output schema declared.

No examples provided.

assistants_archive ~24

Archive (soft-delete) an assistant.

NameTypeReqDescription
assistantIdstringyes–

No output schema declared.

No examples provided.

assistants_create ~236

Create an assistant. Required: subAccountId, name. Optional config blocks (llmConfig, voiceConfig, chatConfig) mirror the dashboard create dialog. voice_settings configures call greeting mode, opening messages, and voicemail behavior; platform_tools attaches platform-catalog tools (declarative full-replace — see the field description).

NameTypeReqDescription
assistantTypestring––
chatConfigobject––
descriptionstring––
llmConfigobject––
namestringyes–
platform_toolsarray–Platform tool names to attach, e.g. ["book_appointment", "send_email"]. Declarative within the platform catalog: tools in the list are attached, catalog tools missing from the list are detached, cust…
subAccountIdstringyes–
voiceConfigobject––
voiceId–––
voice_settingsobject––

No output schema declared.

No examples provided.

assistants_get ~51

Fetch an assistant's full configuration by ID. The response includes voice_settings (greeting mode, opening messages, voicemail) and platform_tools (attached platform-catalog tool names).

NameTypeReqDescription
assistantIdstringyes–

No output schema declared.

No examples provided.

assistants_list ~71

List assistants in a subaccount (excludes archived by default). Note: voice_settings and platform_tools are returned only by assistants_get, not in the list.

NameTypeReqDescription
cursorstring––
includeArchivedboolean––
limitinteger––
subAccountIdstringyes–

No output schema declared.

No examples provided.

assistants_update ~213

Patch an assistant. Only supplied fields change; nested config blocks are upserted. voice_settings updates call greeting mode, opening messages, and voicemail behavior; platform_tools declaratively replaces the attached platform-catalog tools (an empty array detaches all — see the field description).

NameTypeReqDescription
assistantIdstringyes–
chatConfigobject––
description–––
llmConfigobject––
namestring––
platform_toolsarray–Platform tool names to attach, e.g. ["book_appointment", "send_email"]. Declarative within the platform catalog: tools in the list are attached, catalog tools missing from the list are detached, cust…
voiceConfigobject––
voiceId–––
voice_settingsobject––

No output schema declared.

No examples provided.

calls_get ~42

Fetch a call (status, recording, transcript) by ID.

NameTypeReqDescription
callIdstring–Legacy alias for call_id.
call_idstring––

No output schema declared.

No examples provided.

contacts_get ~22

Fetch a contact by ID.

NameTypeReqDescription
contactIdstringyes–

No output schema declared.

No examples provided.

contacts_list ~65

List contacts in a subaccount. meta.total is the number of matching contacts, so use it to answer how many contacts there are.

NameTypeReqDescription
cursorstring––
limitinteger––
searchstring––
subAccountIdstringyes–

No output schema declared.

No examples provided.

conversations_list ~38

List conversations in a subaccount.

NameTypeReqDescription
cursorstring––
limitinteger––
subAccountIdstringyes–

No output schema declared.

No examples provided.

search_tools ~93

Search Assistable's registered MCP tools by the task the user wants to do. Returns up to 5 exact tool definitions with JSON input schemas and annotations. Use this first when you need to choose a tool; the result is not authorization to call it.

NameTypeReqDescription
limitinteger–How many matching tools to return. Defaults to 5.
querystringyesA short description of the task or capability needed.

No output schema declared.

No examples provided.

tools_create_custom ~93

Create a custom tool (toolType=CUSTOM). Name must match /^[a-zA-Z0-9_-]+$/ and be unique in the subaccount.

NameTypeReqDescription
descriptionstring––
headersobject––
httpMethodstring––
namestringyes–
parametersarray––
subAccountIdstringyes–
urlstring––

No output schema declared.

No examples provided.

tools_delete ~22

Soft-delete a custom tool.

NameTypeReqDescription
toolIdstringyes–

No output schema declared.

No examples provided.

tools_get ~23

Fetch a tool's full configuration.

NameTypeReqDescription
toolIdstringyes–

No output schema declared.

No examples provided.

tools_list ~65

List tools visible to a subaccount. Pass includePrebuilt=false for only custom tools.

NameTypeReqDescription
cursorstring––
includePrebuiltboolean––
limitinteger––
searchstring––
subAccountIdstringyes–

No output schema declared.

No examples provided.

tools_update ~70

Patch a custom tool. Supplying parameters/headers replaces those rows; omit to leave them.

NameTypeReqDescription
description–––
headers–––
httpMethodstring––
namestring––
parameters–––
toolIdstringyes–
url–––

No output schema declared.

No examples provided.

Install

How do I install the Assistable MCP server?

Assistable is a hosted endpoint at https://api.assistable.ai/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 · api.assistable.ai

# add to Claude Code
claude mcp add --transport http ai-assistable-assistable 'https://api.assistable.ai/mcp'
Common questions

What is the Assistable MCP server?

Assistable is an MCP server listed in the public MCP registry as ai.assistable/assistable. Give any AI agent a phone: make and answer calls, get through phone menus, and send texts. This page covers its hosted endpoint (https://api.assistable.ai/mcp).

Is the Assistable MCP server safe to use?

Assistable scores 60 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 Assistable MCP server expose?

Assistable exposes 16 tools: search_tools, assistants_list, assistants_get, assistants_create, assistants_update, and 11 more. Their descriptions and schemas cost roughly 1,187 tokens of context every time the server is loaded.

Does the Assistable MCP server require authentication?

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

Is the Assistable MCP server still maintained?

Assistable is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.