Vendo AI

REMOTE · API.VENDO-AI.COM · SCANNED AUG 3

Autonomous AI sales: agents, signal-based prospecting, outreach, CRM — 149 tools.

Available components

23 23 Trust /100

Trust breakdown (6 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 →

Endpoint Security57

The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. View diagnostics → Unverified
HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
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

Transport & Reachability0

Transport check failed: declared streamable-http, but the endpoint returned HTTP 429. See how to fix → View diagnostics → Fail

Schema Quality & AI Usability0

Schema not yet verified: we couldn't read the endpoint's schema.Unverified

Stability & Change Management0

Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified

Tool Coverage0

Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified

Capabilities0

Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 4 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · api.vendo-ai.com

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add --transport http com-vendo-ai-vendo-ai https://api.vendo-ai.com/mcp

# ~/.codex/config.toml

[mcp_servers.com-vendo-ai-vendo-ai]
url = "https://api.vendo-ai.com/mcp"

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-vendo-ai-vendo-ai": {
      "type": "remote",
      "url": "https://api.vendo-ai.com/mcp",
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add com-vendo-ai-vendo-ai --url https://api.vendo-ai.com/mcp --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  com-vendo-ai-vendo-ai:
    url: "https://api.vendo-ai.com/mcp"

// mcp.json

{
  "mcpServers": {
    "com-vendo-ai-vendo-ai": {
      "type": "http",
      "url": "https://api.vendo-ai.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

31 Jul 26 +9
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
30 Jul 26 −44
- Endpoint reachability: reachable → not serving MCP ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: Schema not yet verified: we couldn't read the endpoint's schema. functional
29 Jul 26 +37
- Authorization: fail → unverified ▼ security
- Transport: unverified → pass ▲ security
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: good functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 10 functional
- First check of Schema quality: pass functional
28 Jul 26 21

First indexed and scored.

Show 1 earlier entry Hide earlier entries

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 3 Aug 2026 · Probed https://api.vendo-ai.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .

Subject	Issuer	Valid from	Valid until	Key	Signature	Serial
CN=api.vendo-ai.com	CN=YE2,O=Let's Encrypt,C=US	3 Jul 2026	1 Oct 2026	ECDSA 256	ECDSA-SHA384	5dfec38489dc23cc1d4b939044079a8dab6
SANs: api.vendo-ai.com
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

DNSSEC insecure

Validation of api.vendo-ai.com. — Not signed

Zone	DS	Keys	Algorithms	Outcome
.	trust_anchor	20326, 38696	8, 8	Verified
com.	present	19718	13	Verified
vendo-ai.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	429

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://api.vendo-ai.com/mcp	HTTP error	429
http (plaintext)	http://api.vendo-ai.com/mcp	HTTPS enforced

MCP tools — 149 exposed · ~7,790 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.

Tool Tokens

archive_campaign Archive a campaign ~30

Archive a campaign — it stops processing and is hidden from the default views.

Input Output Examples

Name	Type	Req	Description
id	string	yes	—

No output schema declared.

No examples provided.

buy_audience_set Buy an audience set ~59

SPENDS CREDITS (2 per contact). Purchases the set and snapshots its contacts into the workspace. Only call after the user reviewed `preview_buy_audience_set` output and explicitly approved the cost.

Input Output Examples

Name	Type	Req	Description
id	string	yes	—

No output schema declared.

No examples provided.

connect_google_meet Start the Google Meet OAuth flow ~45

Returns a Google OAuth URL. The user MUST open this URL in a browser and grant consent — the MCP cannot complete OAuth on its own.

Input Output Examples

Name	Type	Req	Description
id	string	yes	—

No output schema declared.

No examples provided.

connect_linkedin_account Get a link to connect a LinkedIn account ~71

Returns a hosted URL that a HUMAN must open in a browser to authorise a LinkedIn account. This tool cannot complete the connection itself — give the link to the user. No account exists until they finish the flow.

Input Output Examples

Name	Type	Req	Description
campaign_id	string	—	Optionally bind the new account to a campaign

No output schema declared.

No examples provided.

connect_telegram_bot Connect a Telegram bot to the agent ~68

The user creates a bot with @BotFather, gets the HTTP API token, and passes it here. After that, all messages to the bot are answered by the agent.

Input Output Examples

Name	Type	Req	Description
bot_token	string	yes	Telegram Bot API token from @BotFather
id	string	yes	—

No output schema declared.

No examples provided.

create_agent Create a new agent ~132

Create a new AI sales agent. Costs 1 credit. The agent is created in DRAFT status and does not start contacting anyone — you still need to attach it to a campaign and launch the campaign. Required: name + description. Company info (name/website/description) is required BEFORE generating a sales script, so you can either pass it here OR call `set_agent_company` later.

Input Output Examples

Name	Type	Req	Description
description	string	yes	A short description of the agent itself (1-2 sentences, what it does)
name	string	yes	Agent's display name (e.g. 'Sales agent for Acme')

No output schema declared.

No examples provided.

create_campaign Create a campaign (DRAFT, not launched) ~79

Create a new campaign in DRAFT status. The campaign is NOT launched — nobody is contacted until you call `launch_campaign`. Needs an audience id and an agent id.

Input Output Examples

Name	Type	Req	Description
agentId	string	—	—
audienceId	string	yes	—
description	string	—	—
name	string	yes	—
settings	object	—	—

No output schema declared.

No examples provided.

crm_add_comment Add an internal comment on a lead ~44

Internal team note on the lead card (not visible to the lead). Supports @mentions via user ids.

Input Output Examples

Name	Type	Req	Description
body	string	yes	—
id	string	yes	—

No output schema declared.

No examples provided.

crm_communication_cards List communication cards ~52

One card per campaign and per SDR search, with outbound counters. This is the FULL outbound stream — everyone contacted, whether or not they replied (CRM leads only contains people who answered). Read-only, free.

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

crm_communication_history Outbound history for one card ~114

Every outbound touch for one campaign or SDR search, filterable by channel, reply status and date. Use `crm_communication_cards` first to get the id. Read-only, free.

Input Output Examples

Name	Type	Req	Description
channel	string	—	—
from	string	—	ISO date
id	string	yes	Campaign id or SDR search id
limit	number	—	—
offset	number	—	—
replied	boolean	—	—
to	string	—	ISO date
type	string	yes	—

No output schema declared.

No examples provided.

crm_communication_thread Full message thread for one contact ~77

The complete message thread with one contact inside a card. `key` comes from a `crm_communication_history` row (an email address or LinkedIn chat id). Read-only, free.

Input Output Examples

Name	Type	Req	Description
id	string	yes	—
key	string	yes	Thread key from crm_communication_history
type	string	yes	—

No output schema declared.

No examples provided.

crm_create_calendar_event Create a CRM calendar event ~85

Add a custom event to the CRM planner. Write operation, no credit cost. Does NOT send invites to anyone — it only records the event on the internal calendar.

Input Output Examples

Name	Type	Req	Description
all_day	boolean	—	—
ends_at	string	—	ISO datetime
notes	string	—	—
starts_at	string	yes	ISO datetime
title	string	yes	—

No output schema declared.

No examples provided.

crm_create_lead Create a lead manually ~98

Add a lead card to the New stage. ALL fields optional — provide whatever is known (at least one non-empty). Side-effect: a card appears on the customer board.

Input Output Examples

Name	Type	Req	Description
company_name	string	—	—
email	string	—	—
first_name	string	—	—
last_name	string	—	—
linkedin_url	string	—	—
phone	string	—	—
title	string	—	—

No output schema declared.

No examples provided.

crm_create_stage Create a pipeline stage ~47

Add a custom kanban column (name, optional hex color). Inserted before the terminal stages (Won/Lost).

Input Output Examples

Name	Type	Req	Description
color	string	—	—
name	string	yes	—

No output schema declared.

No examples provided.

crm_delete_calendar_event Delete a CRM calendar event ~46

Remove a custom calendar event. Unlike deleting a lead or a stage this destroys no history and needs no preview step, but it cannot be undone.

Input Output Examples

Name	Type	Req	Description
id	string	yes	—

No output schema declared.

No examples provided.

crm_enrich_from_linkedin Enrich a person from a LinkedIn URL ~87

Fetch name / title / current employer / avatar / location for a linkedin.com/in/... URL (same lookup the SDR hunters use). May also suggest an email as an UNVERIFIED pattern guess (email_confidence=pattern_guess). Costs one profile view from the workspace's shared daily LinkedIn budget — do not loop over big lists.

Input Output Examples

Name	Type	Req	Description
linkedin_url	string	yes	—

No output schema declared.

No examples provided.

crm_get_conversation Get lead conversation thread ~44

The full message thread with this lead on their source channel (LinkedIn / email / widget / telegram / phone transcript). Read-only.

Input Output Examples

Name	Type	Req	Description
id	string	yes	—

No output schema declared.

No examples provided.

crm_get_lead Get one CRM lead (full detail) ~43

Full lead card: identity, source ("why is this person here"), company enrichment, activities, comments, assignments. Read-only.

Input Output Examples

Name	Type	Req	Description
id	string	yes	—

No output schema declared.

No examples provided.

crm_get_settings Get CRM settings ~34

Read CRM settings, including the notify_* toggles that control which events send an email/notification. Read-only, free.

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

crm_list_calendar_events List CRM calendar events ~88

List custom calendar events (meetings, reminders) in the CRM planner for a date range. Note: SDR sending windows also appear in the UI calendar but are derived from the search schedule — read those via `sdr_get_search`. Read-only, free.

Input Output Examples

Name	Type	Req	Description
from	string	—	ISO date, start of range
to	string	—	ISO date, end of range

No output schema declared.

No examples provided.

crm_list_leads List CRM leads ~132

List leads in the CRM pipeline. Filters: stage (stage id), source (e.g. linkedin_outreach_reply, email_reply_real, widget_chat, manual), q (name/company/email search), range (24h|7d|30d|90d|180d|1y|all), limit/offset. Read-only. Great first call for "who replied to me?".

Input Output Examples

Name	Type	Req	Description
limit	integer	—	—
offset	integer	—	—
q	string	—	—
range	string	—	—
source	string	—	—
stage	string	—	—

No output schema declared.

No examples provided.

crm_list_linkedin_accounts List connected LinkedIn accounts ~41

List the LinkedIn accounts connected to this workspace, as shown in the CRM. Useful to see which account owns a conversation. Read-only, free.

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

crm_list_notifications List CRM notifications ~42

List CRM notifications (new lead, new reply, stage change). Read-only, free.

Input Output Examples

Name	Type	Req	Description
limit	number	—	—
unread_only	boolean	—	—

No output schema declared.

No examples provided.

crm_list_stages List pipeline stages ~35

Ordered kanban columns for this workspace (id, name, color, is_terminal). Read-only. Call before moving leads.

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

crm_list_workspace_agents List agents visible in CRM ~30

List the AI agents in this workspace that CRM leads can be attributed to. Read-only, free.

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

crm_list_workspace_members List workspace members ~44

List the people in this workspace who can own a CRM lead. Use before `reassign_crm_lead` to get valid owner ids. Read-only, free.

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

crm_mark_all_notifications_read Mark all notifications as read ~21

Clear the CRM notification badge by marking everything read.

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

crm_mark_notification_read Mark one notification as read ~32

Mark a single CRM notification as read. Write operation, no credit cost.

Input Output Examples

Name	Type	Req	Description
id	string	yes	—

No output schema declared.

No examples provided.

crm_move_lead Move lead to another stage ~53

Drag-and-drop equivalent: move a lead to a different pipeline stage by stage_id (get ids from crm_list_stages). Reversible.

Input Output Examples

Name	Type	Req	Description
id	string	yes	—
stage_id	string	yes	—

No output schema declared.

No examples provided.

crm_reply_to_lead Send a reply to a lead (REAL outbound message) ~75

Sends a REAL LinkedIn message or email reply to the lead on their source channel, from the customer's own account. Also moves the lead to the "Manager Dialog" stage. ALWAYS show the drafted text to the human and get approval BEFORE calling this.

Input Output Examples

Name	Type	Req	Description
id	string	yes	—
text	string	yes	—

No output schema declared.

No examples provided.

crm_stats CRM pipeline stats ~24

Counts per stage, new today/this week, stale leads. Read-only.

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

crm_update_calendar_event Update a CRM calendar event ~69

Edit an existing custom calendar event. Write operation, no credit cost.

Input Output Examples

Name	Type	Req	Description
all_day	boolean	—	—
ends_at	string	—	—
id	string	yes	—
notes	string	—	—
starts_at	string	—	—
title	string	—	—

No output schema declared.

No examples provided.

crm_update_lead Update lead fields ~101

Patch lead attributes (name, company, title, email, phone, notes, tags, deal_value). Reversible.

Input Output Examples

Name	Type	Req	Description
company_name	string	—	—
deal_value	number	—	—
email	string	—	—
first_name	string	—	—
id	string	yes	—
last_name	string	—	—
notes	string	—	—
phone	string	—	—
title	string	—	—

No output schema declared.

No examples provided.

crm_update_settings Update CRM settings ~95

Change CRM settings — e.g. mute new-lead or new-reply notifications while an integration drives the CRM itself. Write operation, no credit cost. Turning notifications off means the human stops being alerted, so confirm with the user first.

Input Output Examples

Name	Type	Req	Description
analytics_emails_enabled	boolean	—	—
notify_new_lead	boolean	—	—
notify_new_reply	boolean	—	—
notify_stage_change	boolean	—	—

No output schema declared.

No examples provided.

crm_update_stage Rename / recolor a pipeline stage ~49

Rename or recolor a stage. System stages (New, Manager Dialog) cannot be renamed.

Input Output Examples

Name	Type	Req	Description
color	string	—	—
id	string	yes	—
name	string	—	—

No output schema declared.

No examples provided.

deep_scan_agent Deep-scan an agent (15 credits, 60-180s) ~78

Crawl 15+ pages of the agent's company website, extract people, contacts, pricing, social links. Saves to the agent. Costs 15 credits. Only call after `preview_deep_scan` and user approval.

Input Output Examples

Name	Type	Req	Description
company_name	string	yes	—
company_website	string	yes	—
id	string	yes	—

No output schema declared.

No examples provided.

delete_agent Delete an agent (irreversible) ~41

Permanently delete an agent. NOT reversible. Only call after the user has reviewed `preview_delete_agent` output and explicitly approved.

Input Output Examples

Name	Type	Req	Description
id	string	yes	—

No output schema declared.

No examples provided.

delete_campaign Delete a campaign (irreversible) ~41

Permanently delete a campaign. NOT reversible. Only call after the user has reviewed `preview_delete_campaign` output and explicitly approved.

Input Output Examples

Name	Type	Req	Description
id	string	yes	—

No output schema declared.

No examples provided.

delete_crm_lead Delete a CRM lead (soft) ~54

Soft-delete a lead — it disappears from the pipeline (restorable by support only). Only call after the user reviewed `preview_delete_crm_lead` output and explicitly approved.

Input Output Examples

Name	Type	Req	Description
id	string	yes	—

No output schema declared.

No examples provided.

delete_crm_stage Delete a pipeline stage ~43

Delete an EMPTY, non-system pipeline stage. Only call after the user reviewed `preview_delete_crm_stage` and explicitly approved.

Input Output Examples

Name	Type	Req	Description
id	string	yes	—

No output schema declared.

No examples provided.

disconnect_google_meet Disconnect Google Meet ~33

Revoke Google Meet for this agent. Existing meetings stay in the user's calendar.

Input Output Examples

Name	Type	Req	Description
id	string	yes	—

No output schema declared.

No examples provided.

disconnect_linkedin_account Disconnect a LinkedIn account ~58

Remove a LinkedIn account from the workspace. Any campaign or SDR search sending from it stops immediately and daily capacity drops. Only call after the user reviewed `preview_disconnect_linkedin_account` and explicitly approved.

Input Output Examples

Name	Type	Req	Description
id	string	yes	—

No output schema declared.

No examples provided.

disconnect_telegram_bot Disconnect Telegram bot ~34

Detach the bot from this agent. Bot keeps existing in Telegram but stops responding.

Input Output Examples

Name	Type	Req	Description
id	string	yes	—

No output schema declared.

No examples provided.

duplicate_agent Duplicate an agent ~34

Create a copy of an existing agent (new id, same config). Counts toward agent capacity.

Input Output Examples

Name	Type	Req	Description
id	string	yes	—

No output schema declared.

No examples provided.

generate_agent_description Generate company description from website ~43

Use AI to draft a 2-3 paragraph company description. Costs 1 credit. Requires `company_website` already set.

Input Output Examples

Name	Type	Req	Description
id	string	yes	—

No output schema declared.

No examples provided.

generate_agent_script Generate sales / support / info script ~91

Generate the agent's full sales script (8 stages) and email_script (for email/LinkedIn channels). Requires `company_name` AND `company_description` already set on the agent — call `set_agent_company` first. Costs 1 credit. Re-running OVERWRITES the existing script.

Input Output Examples

Name	Type	Req	Description
id	string	yes	—
purpose	string	—	—
script_style	string	yes	—

No output schema declared.

No examples provided.

get_agent Get an agent ~29

Fetch the full details of a single agent by id.

Input Output Examples

Name	Type	Req	Description
id	string	yes	The agent UUID

No output schema declared.

No examples provided.

get_agent_plan_limits Get agent capacity ~34

How many agents can the user create (base plan + purchased extra slots) vs how many they have. Read-only.

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_audience Get one saved audience ~32

Read one saved audience with its filters and contact count. Read-only, free.

Input Output Examples

Name	Type	Req	Description
id	string	yes	—

No output schema declared.

No examples provided.

get_audience_set Get one audience set ~60

Details of one marketplace set by slug: size, description, freshness. Use the contact count here to work out the purchase cost (2 credits per contact). Read-only, free.

Input Output Examples

Name	Type	Req	Description
slug	string	yes	Human-readable slug, not a UUID

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

28 Jul 3 Aug