The GTM MCP Directory
Directory / Vendors / Artisan AI (Ava)

Artisan AI (Ava)

1 product in the directory 1 official MCP server 1 live handshake Data baked 2026-09-27

Vendor domain: artisan.co · vendor page id artisan-co

The rollup
Products
1, facts checked by hand 2026-09-02
Official MCP servers
1 of 1, as recorded on 2026-09-02
Community MCP servers
0 of 1
Live handshake
1 of 1 answered an MCP initialize, 1 probed, 2026-09-04
Repo local
0 of 1: a server you install and run yourself
Docs only
0 of 1: the recorded URL is a page about the server, not the server
Tools catalogued
4 named across 1 measured server, harvested 2026-09-27
Bench tested
0 of 1 here, 1 of 1,252 across the directory
Ships a CLI
0 of 1 official, 0 community only, 1 none found, harvested 2026-09-27
GitHub organisation
github.com/Artisan-AI, tied to the domain with evidence 2026-09-08

A live handshake means the URL answered an MCP initialize as a server on the probe date. It is liveness and nothing more: nobody has run its tools. A tool being catalogued means a server names it, by answering tools/list, in its own source, or in the vendor's documentation. None of them has been called. A tool count of 0 means not measured, never zero tools.

Products, 1

Artisan AI (Ava)

An AI agent ("Ava") that finds and enriches B2B leads, writes and sends personalized outreach, handles replies, and books meetings - marketed as running outbound "end to end."

Endpoint probe
answered as an MCP server, 2026-09-04
Connect URL
Tools catalogued
4 named, harvested 2026-09-27, catalogue fixed
last_checked
2026-09-02
The gates, in plain words

1 of 1 enterprise only, API access needs a contract.

The gate is the api_gate field on each product entry, established by hand on the last_checked date shown above. It records whether a solo operator can get API access without a contract. Money is not tracked.

Jobs the vendor says its products do

5 distinct job labels, the union across 1 product, tagged 2026-08-25. A job tag means the vendor says the tool does this. It is not a test result, not proof the capability is reachable through the tool's MCP server, and not proof it is available on the gate this entry records.

Connect URLs

An endpoint is where an agent connects. A docs page is where a person reads about connecting. Both are published because both are what the probe found; an agent needs the first.

Command line

No CLI found for any product of this vendor by the 2026-09-27 harvest across vendor docs, npm, PyPI, Homebrew and GitHub. That is a probe result, not proof of absence.

On GitHub

github.com/Artisan-AI tied to the vendor by rule 3, account website https://www.artisan.co has the vendor's domain, confidence strong

Public repositories
1, forks excluded, as read on 2026-09-08
Mention MCP
0 of them
Look like CLIs
0 of them
Latest push
2026-05-25

The five most recently pushed, on 2026-09-08:

RepositoryKindDescriptionStarsPushedLatest release
mitch-prototypesotherInteractive prototypes for Artisan product design02026-05-25

Kind is a heuristic guessed from the repository name, topics and description, not a fact the vendor stated. A repository count is activity, not a verdict. Read 2026-09-08.

What this page does not claim

A job tag is a vendor claim: it means the vendor says the product does this, and it is not a test result. A listed tool has not been run: the catalogue says what an agent could try, not what works. 1 of 1,252 directory entries are bench tested, meaning somebody personally ran the tool on a stated date, and 0 of this vendor's 1 product are among them. There is no verdict here on whether this vendor is better than another.

Vendor pages group the directory's canonical product entries by vendor_domain. The vendor name is the product display name that matches the domain when several products share it; nothing on this page is typed by hand. Data baked 2026-09-27 by build_directory.py (phase 1).