Cli

dev.kantaPublished by kanta.devv0.1.8Updated Oct 24, 2026

Kanta Verify, Find, and Database: email verification, email finding, and B2B contact search.

VerifiedSTDIODesktop onlyWeb Search & ScrapingBusiness & Commerce

Overview

AI-generated overview

Lets an assistant verify email addresses, find emails, and search B2B contacts through the Kanta API.

What you can do
Kanta Cli exposes the Kanta Verify, Find, and Database services to an assistant: email verification, email finding, and B2B contact search. It runs locally over stdio and is started with npx from the @kantadev/cli package. The manifest does not list individual tool names, so the exact tool set is not documented here.
When to use it
Worth adding when a workflow needs to check whether an email address is deliverable, look up an address for a person or company, or pull B2B contact data. It is aimed at desktop use rather than browser-based sessions.
Requirements
A local Node.js runtime to run the npm package via npx. A Kanta API key is required, supplied through the KANTA_API_KEY environment variable or a named profile in ~/.kanta/config.json selected with KANTA_PROFILE. Optional KANTA_BASE_URL and KANTA_DB_URL variables override the API endpoints. Network access to the Kanta services is needed.
Before you install
The server requires the secret KANTA_API_KEY, which grants access to your Kanta account and its usage quota. Contact search and email finding send queries about people and companies to Kanta's servers, so consider the privacy of the data you submit. Verify and Find results may be billed or rate-limited by your Kanta plan.

Installation

In SourceWeft

  1. Open Cli in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

5
  1. v0.1.8LatestOct 14, 2026
  2. v0.1.7Oct 12, 2026
  3. v0.1.6Oct 8, 2026
  4. v0.1.3Oct 7, 2026
  5. v0.1.1Sep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.