Marketing
veezco.com
Provides local business contact and category search for sales prospecting, including website insights and call openers.
ENDPOINT 1
https://www.veezco.com/api/mcp
MCP server metadata
- Name
- veezco
- Version
- 1.0.0
Veezco finds local businesses to sell to, with contacts, what it measured on their website and an opening line for the call. Start with list_categories for the city, then search_companies with the exact category name it returns. Each new lead costs 1 credit (get_credits shows the balance); leads already received are free. A city and category not in the catalog start a live collection: call search_companies again a few minutes later to receive the leads.
Known tools 3
search_companiesFind local businesses in one city and one category, with their contacts, what Veezco measured on their website and an opening line for the call.
Inferred read-onlylist_categoriesList the business categories Veezco already collected in a city, with the date of the latest collection.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.veezco]
url = "https://www.veezco.com/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"veezco": {
"type": "http",
"url": "https://www.veezco.com/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: veezco
Remote MCP URL: https://www.veezco.com/api/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"veezco": {
"url": "https://www.veezco.com/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"veezco": {
"type": "http",
"url": "https://www.veezco.com/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "veezco",
"transport": "streamable-http",
"url": "https://www.veezco.com/api/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.