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.

Veezco

REMOTE · WWW.VEEZCO.COM

Find local businesses to sell to, with contacts, website checks and an opening line for the call.

Available components

76 Trust /100

Last scanned (11 hours ago)

Scores higher than 66% of remote servers

Reachable. Last reached 5 Nov 2026.

Category CRM and Sales

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 Security89
Transport & Reachability100
Schema Quality & AI Usability66
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 547 tokens (~182/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
  • Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 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
What we tested

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 →

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
    • Stability: unverified → 0.03 ▲ functional
  • 3 Nov 26 +39
    • Transport: unverified → pass ▲ security
    • Injection markers: unverified → pass ▲ security
    • First check of Judged manipulation: pass security
    • Authorization: Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. security
    • MCP protocol: unverified → pass ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • First check of Schema quality: fail functional
    • First check of Destructive annotations: pass functional
    • First check of Schema quality: fail functional
    • First check of Schema quality: good functional
    • First check of Tool coverage: 100 functional
  • 2 Nov 26 36

    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 5 Nov 2026 · Probed https://www.veezco.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=www.veezco.com CN=YR1,O=Let's Encrypt,C=US 9 Oct 2026 7 Jan 2027 RSA 2048 SHA256-RSA 6910dc78d44bb79e4568a8a721e5b60bb80
SANs: www.veezco.com
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 www.veezco.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
veezco.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Challenged, unverified

The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.

Result Challenged, unverified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer realm="Veezco"

Bearer realm="Veezco"
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=(), geolocation=()

Protected resource metadata

Retrieved No
Problem No resource metadata

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.veezco.com/api/mcp Verified 200
http (plaintext) http://www.veezco.com/api/mcp HTTPS enforced 308 https://www.veezco.com/api/mcp
MCP tools · 3 exposed · ~448 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
get_credits ~32

Your Veezco credit balance and plan. Free, no credits used. One credit is one new lead.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_categories ~67

List the business categories Veezco already collected in a city, with the date of the latest collection. Free, no credits used. Use it to pick the exact category name for search_companies.

NameTypeReqDescription
citystringyesCity or town name, e.g. "Torino".

No output schema declared.

No examples provided.

search_companies ~349

Find local businesses in one city and one category, with their contacts, what Veezco measured on their website and an opening line for the call. Each NEW lead costs 1 Veezco credit; leads you already received are free and come first. Categories are written as Veezco stores them: Italian plural names in Italy ("Dentisti", "Ristoranti", "Agenzie immobiliari", "Idraulici", "Centri estetici"), English plural names elsewhere ("Dentists"). Call list_categories first to get the exact names already collected in that city. If the city and category were never collected, Veezco starts a live collection: leads appear while it runs and a full collection usually takes 15-30 minutes, so call this tool again later with the same arguments to receive them. Filters only select what Veezco actually measured: a website it could not read never matches "no_meta_pixel".

NameTypeReqDescription
categorystringyesBusiness category, plural: Italian in Italy (e.g. "Dentisti"), English elsewhere (e.g. "Dentists").
citystringyesCity or town name, e.g. "Torino".
countinteger–How many leads you want in total from this search (1-50, default 10). Leads already yours are included and free.
countrystring–Optional ISO 3166-1 alpha-2 code for a new collection outside Italy (e.g. "GB", "IE", "FR"). Default "IT".
filtersarray–Optional. Combined with AND. no_website cannot be combined with filters that need a website.

No output schema declared.

No examples provided.

Install

How do I install the Veezco MCP server?

Veezco is a hosted endpoint at https://www.veezco.com/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 · www.veezco.com

# add to Claude Code
claude mcp add --transport http com-veezco-veezco 'https://www.veezco.com/api/mcp'
Common questions

What is the Veezco MCP server?

Veezco is an MCP server listed in the public MCP registry as com.veezco/veezco. Find local businesses to sell to, with contacts, website checks and an opening line for the call. This page covers its hosted endpoint (https://www.veezco.com/api/mcp).

Is the Veezco MCP server safe to use?

Veezco scores 76 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 Veezco MCP server expose?

Veezco exposes 3 tools: search_companies, list_categories, get_credits. Their descriptions and schemas cost roughly 448 tokens of context every time the server is loaded.

Does the Veezco MCP server require authentication?

Yes. Veezco asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the Veezco MCP server still maintained?

Veezco 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 Veezco MCP server?

VerifyMCP ran 13 checks on Veezco, 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.