Vendo AI
REMOTE · API.VENDO-AI.COM
Autonomous AI sales: agents, signal-based prospecting, outreach, CRM — 149 tools.
Available components
Last scanned (6 hours ago)
Scores higher than 10% of remote servers
Reachable. Last reached 5 Nov 2026.
Category CRM and Sales
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 not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- 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 & 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, or could read only part of its tool list.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, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 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.
Checks we ran (5)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (6)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 13 Sept 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 12 Sept 26 0
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- First check of Judged manipulation: pass security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 149 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Destructive annotations: 0 functional
- 9 Sept 26 0
- HSTS header: fail → pass ▲ security
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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://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 | 31 Oct 2026 | 29 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 5b7d06f47371db6948d802acf73a34eeaf9 |
| 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 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.vendo-ai.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| vendo-ai.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 429 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| 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://api.vendo-ai.com/mcp | HTTP error | 429 | |
| http (plaintext) | http://api.vendo-ai.com/mcp | HTTPS enforced |
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 →
save_audience Save an audience ~56
Save a searchable audience using the same filter set as `search_audience`. The audience is named and can then be attached to a campaign. No outreach happens here.
| Name | Type | Req | Description |
|---|---|---|---|
| filters | object | yes | – |
| name | string | – | – |
No output schema declared.
No examples provided.
save_scan_data Persist scan results ~34
Save the output of a deep scan onto the agent (company description, people, contacts).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
scan_website_quick Quick website scan ~52
Crawl a website's structure (sitemap, top pages) BEFORE creating an agent. Useful when deciding which company to set on the agent. Costs ~2 credits.
| Name | Type | Req | Description |
|---|---|---|---|
| website_url | string | yes | – |
No output schema declared.
No examples provided.
sdr_activate_search Activate (start) a Signal Search ~37
Set status=active and fire-start all enabled hunters. Reversible via `sdr_pause_search`.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
sdr_activity_feed Live activity feed for an SDR search ~53
Recent discovery + outreach events for one SDR search, newest first — the same ticker the dashboard shows. Read-only, free.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Default 40 |
| search_id | string | yes | – |
No output schema declared.
No examples provided.
sdr_company_heat Hottest companies by signal strength ~33
Composite "heat" ranking — companies with the strongest live signal in the workspace.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.
sdr_create_search Create a Signal Search (and start hunting) ~182
Create a Signal Search and immediately activate the configured hunters. Required: name, agent_id. Optional: enabled_sources, target_regions (ISO-2 country codes), pre-edited profile fields from `sdr_preview_search`.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| enabled_sources | array | – | E.g. ['linkedin_jobs', 'connected_people']. Paid sources (ai_web_hunter, g2_reviews, tech_stack) are off by default. |
| exclude_keywords | array | – | – |
| icp_summary | string | – | – |
| industry_keywords | array | – | – |
| name | string | yes | – |
| offer_summary | string | – | – |
| relevant_topics | object | – | – |
| signal_weights | object | – | – |
| target_regions | array | – | ISO-2 country codes the search targets, e.g. ['GB', 'US']. |
No output schema declared.
No examples provided.
sdr_delete_outreach Delete the SDR outreach campaign (irreversible) ~46
Delete the SDR outreach campaign. The Signal Search and its hunters CONTINUE running. Only call after `sdr_preview_delete_outreach`.
| Name | Type | Req | Description |
|---|---|---|---|
| search_id | string | yes | – |
No output schema declared.
No examples provided.
sdr_delete_search Delete a Signal Search (irreversible) ~44
Permanently delete a Signal Search. Hunters are paused first, then the search and all its contacts/personas are removed. NOT reversible.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
sdr_export_people_csv Export SDR contacts as CSV ~98
Export the contacts of an SDR search as CSV text (name, title, email, LinkedIn, location, company). Contacts ONLY — deliberately carries no scores or signal reasoning, because this file leaves the platform. Returns the raw CSV; can be large. Read-only, free.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | – |
| min_relevance | number | – | – |
| role | string | – | – |
| search_id | string | yes | – |
No output schema declared.
No examples provided.
sdr_export_personas_to_audience Export personas to a saveable audience ~89
Take the personas matched by a Signal Search (optionally filtered by role / having email / specific IDs) and export them into a custom audience that can then be attached to any campaign.
| Name | Type | Req | Description |
|---|---|---|---|
| ids | array | – | – |
| name | string | – | – |
| only_with_email | boolean | – | – |
| roles | array | – | – |
| search_id | string | yes | – |
No output schema declared.
No examples provided.
sdr_generate_agent_signal_profile Generate an agent's signal profile (Claude) ~48
Run Claude on the agent's knowledge to (re)generate its signal profile. Persists onto the agent so later Signal Searches reuse it.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
No output schema declared.
No examples provided.
sdr_get_agent_signal_profile Get an agent's signal profile ~48
Read the agent's current signal profile (ICP, offer summary, hunter weights). Returns { exists: false } when nothing's generated yet.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
No output schema declared.
No examples provided.
sdr_get_outreach Get SDR outreach status for a search ~39
Read the SDR outreach campaign — channels enabled, ready/queued/sent counts, current content config.
| Name | Type | Req | Description |
|---|---|---|---|
| search_id | string | yes | – |
No output schema declared.
No examples provided.
sdr_get_outreach_content Get SDR outreach content (templates) ~36
Read the configured email subject/body templates and LinkedIn invite template for SDR outreach.
| Name | Type | Req | Description |
|---|---|---|---|
| search_id | string | yes | – |
No output schema declared.
No examples provided.
sdr_get_person_detail Why was this person picked? ~72
Full provenance for one person found by SDR: which hunter found them, what query fired, what signal triggered the pick, and the scoring breakdown. Use this to explain to a customer WHY a contact is in their list. Read-only, free.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Person (persona) id |
No output schema declared.
No examples provided.
sdr_get_search Get a Signal Search ~34
Fetch one Signal Search by id, including its profile, hunters, and contact counts.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
sdr_health Get Signal Search health dashboard ~42
Operator-level health view: states, signals/contacts produced, credits spent, recent events, learning insights for a single search.
| Name | Type | Req | Description |
|---|---|---|---|
| search_id | string | yes | – |
No output schema declared.
No examples provided.
sdr_launch_outreach Launch SDR outreach (sends real messages, spends credits) ~89
Launch SDR outreach. Contacts will start receiving emails and/or LinkedIn invites. Credits spent per message. Only call after `sdr_preview_launch_outreach` and explicit user approval.
| Name | Type | Req | Description |
|---|---|---|---|
| channels | array | – | – |
| daily_email_limit | integer | – | – |
| daily_linkedin_limit | integer | – | – |
| search_id | string | yes | – |
| sender_mode | string | – | – |
No output schema declared.
No examples provided.
sdr_learning_insights Learning insights — per-signal-type performance ~25
Learned weights per signal type and conversion stats based on real outreach outcomes.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
sdr_list_personas List personas (contacts) discovered for a search ~81
List the people Vendo SDR has discovered for a given Signal Search. Filterable by company, role, min_relevance.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | – |
| limit | integer | – | – |
| min_relevance | string | – | – |
| offset | integer | – | – |
| role | string | – | – |
| search_id | string | yes | – |
No output schema declared.
No examples provided.
sdr_list_searches List Vendo SDR Signal Searches ~33
List active Signal Searches in this workspace. Optionally filter by agent.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | – |
No output schema declared.
No examples provided.
sdr_outreach_summary Sent/queued counters for an SDR search ~35
Per-channel sent and queued counts for one SDR search. Read-only, free.
| Name | Type | Req | Description |
|---|---|---|---|
| search_id | string | yes | – |
No output schema declared.
No examples provided.
sdr_pause_outreach Pause SDR outreach delivery ~31
Stop sending new messages on this SDR campaign. Reversible.
| Name | Type | Req | Description |
|---|---|---|---|
| search_id | string | yes | – |
No output schema declared.
No examples provided.
sdr_pause_search Pause a Signal Search ~38
Pause hunters. Existing data stays; no new contacts surface. Reversible via `sdr_resume_search`.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
sdr_persona_stats Get persona stats for a Signal Search ~44
Aggregate stats: total personas, by_role, top_companies, daily count series, credits_spent, quality_blocked.
| Name | Type | Req | Description |
|---|---|---|---|
| search_id | string | yes | – |
No output schema declared.
No examples provided.
sdr_preview_delete_outreach Preview deleting an SDR outreach campaign ~39
Show what would happen. The Signal Search ITSELF is NOT deleted, only the outreach campaign.
| Name | Type | Req | Description |
|---|---|---|---|
| search_id | string | yes | – |
No output schema declared.
No examples provided.
sdr_preview_delete_search Preview deleting a Signal Search ~33
Show what would happen if you delete the Signal Search. Nothing is deleted.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
sdr_preview_launch_outreach Preview launching SDR outreach ~68
Show what would happen if you launch SDR outreach for this search — recipient counts per channel. NOTHING IS SENT. ALWAYS call first and surface the counts to the user.
| Name | Type | Req | Description |
|---|---|---|---|
| channels | array | – | – |
| search_id | string | yes | – |
| sender_mode | string | – | – |
No output schema declared.
No examples provided.
sdr_preview_outreach_content Preview a personalized SDR message ~40
Render an example personalized email/LinkedIn message for a specific contact. Costs ~1 Claude call.
| Name | Type | Req | Description |
|---|---|---|---|
| search_id | string | yes | – |
No output schema declared.
No examples provided.
sdr_preview_run_now Preview an immediate connector run ~93
Show what would happen if you trigger an immediate hunter run. Useful because some sources are paid (ai_web_hunter, g2_reviews, tech_stack — Anthropic + web_search credits).
| Name | Type | Req | Description |
|---|---|---|---|
| search_id | string | yes | – |
| source | string | – | Name of one specific hunter, or omit to run all enabled. E.g. 'linkedin_jobs', 'ai_web_hunter', 'connected_people'. |
No output schema declared.
No examples provided.
sdr_preview_search Preview a Signal Search profile (no save) ~64
Run Claude on the agent's script and return the auto-generated ICP profile (offer summary, ideal customer profile, relevant topics, LinkedIn queries) WITHOUT persisting anything. Use to review/edit before calling `sdr_create_search`.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
No output schema declared.
No examples provided.
sdr_recent_signals Recent signals (workspace-wide) ~39
Last N signals across all Signal Searches in the workspace. Useful for the "is it working?" check.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.
sdr_regenerate_search Regenerate a Signal Search profile (re-run Claude) ~46
Re-run Claude on the agent's current knowledge to regenerate the entire ICP profile and hunter configuration. Useful after the agent's script changed significantly.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
sdr_resume_outreach Resume SDR outreach delivery ~26
Resume a paused SDR outreach campaign.
| Name | Type | Req | Description |
|---|---|---|---|
| search_id | string | yes | – |
No output schema declared.
No examples provided.
sdr_resume_search Resume a paused Signal Search ~25
Clear paused state and restart all hunters.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
sdr_run_now Trigger an immediate connector run ~63
Fire-and-forget kick of one (or all) hunters for this Signal Search. Spends Anthropic + web_search credits for paid sources. Call after `sdr_preview_run_now`.
| Name | Type | Req | Description |
|---|---|---|---|
| search_id | string | yes | – |
| source | string | – | – |
No output schema declared.
No examples provided.
sdr_run_states Get per-source hunter run-states ~36
Per-source map of run state (running / paused / idle) for a Signal Search.
| Name | Type | Req | Description |
|---|---|---|---|
| search_id | string | yes | – |
No output schema declared.
No examples provided.
sdr_signal_stats Signal stats by source (counts over time) ~44
Signals collected by source over the last N days (max 90, default 30).
| Name | Type | Req | Description |
|---|---|---|---|
| days_back | integer | – | – |
| search_id | string | yes | – |
No output schema declared.
No examples provided.
sdr_update_outreach_content Update SDR outreach content templates ~37
Edit email/LinkedIn templates for this SDR outreach. Takes effect on new sends.
| Name | Type | Req | Description |
|---|---|---|---|
| search_id | string | yes | – |
No output schema declared.
No examples provided.
sdr_update_search Update a Signal Search ~38
Edit a Signal Search — name, enabled_sources, target_regions, or profile fields. Partial updates fine.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
search_audience Search the people database ~161
Search the people graph for prospects matching filters (countries, industries, positions, tags, must-have-email, etc.). PREVIEW only — returns aggregate counts and a small sample. Does not save anything, does not contact anyone, does not spend credits.
| Name | Type | Req | Description |
|---|---|---|---|
| cities | array | – | – |
| companySizes | array | – | – |
| countries | array | – | – |
| exactKeyword | string | – | – |
| industries | array | – | – |
| limit | integer | – | – |
| mustHaveEmail | boolean | – | – |
| mustHaveLinkedin | boolean | – | – |
| mustHavePhone | boolean | – | – |
| positions | array | – | – |
| searchMode | string | – | – |
| semanticQuery | string | – | – |
| tags | array | – | – |
No output schema declared.
No examples provided.
set_agent_avatar_from_url Set agent avatar from an image URL ~70
Set the agent avatar from a publicly-reachable image URL (jpg, png). The MCP server downloads the image and uploads it on your behalf — you do not need to handle multipart yourself.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| image_url | string | yes | Publicly reachable HTTPS image URL |
No output schema declared.
No examples provided.
set_agent_company Set company info (name / website / description) ~68
Required before `generate_agent_script` will work. Set the company the agent represents — its name, website, and what it sells.
| Name | Type | Req | Description |
|---|---|---|---|
| company_description | string | yes | – |
| company_name | string | yes | – |
| company_website | string | yes | – |
| id | string | yes | – |
No output schema declared.
No examples provided.
set_agent_contact_channels Set the contact channels an agent hands out ~122
Set the meeting link, email, phone, WhatsApp and Telegram that the AI agent gives out when a visitor asks how to get in touch or book a call. Omitted channels are cleared, so always send the full set you want the agent to have. Write operation, no credit cost.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | – | |
| id | string | yes | Agent id |
| meeting_url | string | – | Booking link, e.g. Calendly |
| phone | string | – | – |
| telegram | string | – | – |
| string | – | – |
No output schema declared.
No examples provided.
set_agent_status Pause / resume / archive an agent ~41
Change agent status. Allowed values: ACTIVE, PAUSED, ARCHIVED, DRAFT.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| status | string | yes | – |
No output schema declared.
No examples provided.
set_agent_voice Configure agent voice (Retell) ~89
Set agent voice settings: voice_type (e.g. "11labs-Anthony"), language, speed, temperature, backchannel. Call `list_retell_voices` first to see what is available.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| language | string | – | – |
| speech_speed | number | – | – |
| voice_temperature | number | – | – |
| voice_type | string | – | – |
No output schema declared.
No examples provided.
update_agent Update an agent ~75
Update an agent's basic info (name, description, company info). Partial updates are fine — only include the fields you want to change.
| Name | Type | Req | Description |
|---|---|---|---|
| company_description | string | – | – |
| company_name | string | – | – |
| company_website | string | – | – |
| id | string | yes | – |
| name | string | – | – |
No output schema declared.
No examples provided.
update_campaign Update campaign settings ~58
Update a campaign before or after it has started. Partial updates allowed (only include fields you want to change).
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| id | string | yes | – |
| name | string | – | – |
| settings | object | – | – |
No output schema declared.
No examples provided.
How do I install the Vendo AI MCP server?
Vendo AI is a hosted endpoint at https://api.vendo-ai.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 · api.vendo-ai.com
claude mcp add --transport http com-vendo-ai-vendo-ai 'https://api.vendo-ai.com/mcp'
What is the Vendo AI MCP server?
Vendo AI is an MCP server listed in the public MCP registry as com.vendo-ai/vendo-ai. Autonomous AI sales: agents, signal-based prospecting, outreach, CRM, 149 tools. This page covers its hosted endpoint (https://api.vendo-ai.com/mcp).
Is the Vendo AI MCP server safe to use?
Vendo AI scores 25 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 Vendo AI MCP server expose?
Vendo AI exposes 149 tools: get_balance, get_balance_full, get_subscription, get_subscription_limits, get_pricing, and 144 more. Their descriptions and schemas cost roughly 7,790 tokens of context every time the server is loaded.
Does the Vendo AI MCP server require authentication?
Its publisher declares that Vendo AI requires credentials, so you will need to authorise it in your MCP client. We have not been able to confirm that against the live endpoint.
Is the Vendo AI MCP server still maintained?
Vendo 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 Vendo AI MCP server?
VerifyMCP ran 5 checks on Vendo AI, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 1 more. 6 items could not be completed, a gap on our side rather than a finding about Vendo AI: Authorization, Schema quality, Stability, Tool coverage and 2 more. 5 categories score 0 for that reason, because we only credit what we can confirm. 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.