Integration

Wappalyzer integration

Wappalyzer identifies the technologies behind websites. Look up the CMS, ecommerce platform, analytics, frameworks and other software running on up to ten URLs at once (with optional company, contact, social and traffic field sets), discover the subdomains of a domain, verify whether an email address is deliverable, build lead lists of websites using given technologies or keywords and finalize them to get the download link, inspect suppression lists, and check the remaining credit balance. Most calls spend credits and the API needs a Wappalyzer Business plan. Starting a suppression list upload and completing it are not included, because the file goes directly to a storage form outside the API. Authentication is an API key sent in the x-api-key header.

Connect Wappalyzer How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Wappalyzer.Built from the 12 Wappalyzer tools below, on the connection you add once.

What you can do with Wappalyzer

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

List, 5 operations

create_lead_listCreate lead listPOSTCreates a lead list of websites matching technology, category, keyword and company filters. Free, async: returns the id, status Calculating; poll get_lead_list (or callbackUrl) until Ready, then buy with finalize_lead_list. 25/day, 3 calculating max.
delete_lead_listDelete lead listDELETEPermanently deletes a lead list. Free.
finalize_lead_listFinalize lead listPOSTFinalizes a Ready lead list: spends its price in credits and unlocks the full download URL; the status becomes Complete. Costs 1 credit per website.
get_lead_listGet lead listGETFetches a lead list by id with its filters, status, price in credits (totalCredits), per-technology row counts, sample URL and, once finalized, the download URL. Free.
list_lead_listsList lead listsGETLists the lead lists created on the account with their status, price in credits, technology and keyword filters and number of results. Free.

Suppression, 3 operations

delete_suppression_listDelete suppression listDELETERetires a suppression list so it can no longer be used in new lead lists; lead lists already created with it keep their snapshot. Storage is reclaimed after at least 24 hours, once no lead list references it. Repeating the deletion is safe. Free.
get_suppression_listGet suppression listGETReturns the status and metadata of one suppression list, for example to check that it is Ready before passing it as suppressionListId to create_lead_list. The file contents are never returned.
list_suppression_listsList suppression listsGETLists the account's suppression lists (domains to exclude from lead lists) with their status, domain count and size, plus the storage allocated and the account limits. Up to 100 per page.

Balance, 1 operation

get_credit_balanceGet credit balanceGETReturns the account's remaining credit balance, so a job can check it has enough credits before starting.

Lookup, 1 operation

lookup_websitesLookup websitesGETLooks up the technologies of 1 to 10 websites, cached (default) or live. 1 credit per URL (5 with live and recursive true, which needs callback_url). Recursive, uncached: only crawl true returns; repeat (free for 1 h) or set recursive=false (1 URL).

Subdomain, 1 operation

lookup_subdomainsLookup subdomainsGETDiscovers website-serving subdomains of one to ten domains from Wappalyzer's dataset of active websites. Costs 1 credit per 10 subdomains returned. Page with limit and the moreAfter value.

Verify, 1 operation

verify_emailVerify emailGETVerifies an email address: whether it is deliverable, disposable, a role account or a catch-all, and whether its domain has valid MX records. Costs 1 credit per address.

Use Wappalyzer from Claude Code, Cursor or Codex

Connect Wappalyzer in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Wappalyzer operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Wappalyzer

Create your workspace
Sign up free. Nothing to install.
Connect Wappalyzer once
Add your Wappalyzer connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.