Prepare the server locally
Run this once before adding it to Claude Code.
npm installRegister it in Claude Code
claude mcp add -e "WAPPALYZER_API_KEY=${WAPPALYZER_API_KEY}" wappalyzer -- node /path/to/wappalyzer/mcp/index.jsReplace any placeholder paths in the command with the real path on your machine.
WAPPALYZER_API_KEY+ 3 optionalMake your agent remember this setup
wappalyzer's config, env vars, and the gotchas you hit — recalled in every future Claude Code, Cursor, and Codex session.
npx conare@latestFree · one command · indexes the sessions already on disk. Set up in the browser instead →
What it does
- Identify web technologies used on specific websites
- Retrieve subdomains for a given domain
- Access public technology and category metadata
- Monitor API credit usage
Tools 3
lookup_siteIdentify web technologies and metadata for a specific URL.lookup_subdomainsRetrieve a list of subdomains for a given domain.get_credit_balanceCheck the remaining API credit balance.Environment Variables
WAPPALYZER_API_KEYrequiredYour Wappalyzer API keyWAPPALYZER_API_BASE_URLBase URL for the Wappalyzer APIWAPPALYZER_METADATA_BASE_URLBase URL for metadata resourcesWAPPALYZER_HTTP_TIMEOUT_MSHTTP request timeout in millisecondsTry it
Original README from wappalyzer/mcp
Wappalyzer MCP
wappalyzer-mcp is a local stdio MCP server that wraps the public Wappalyzer API.
Requirements
- Node.js 20+
- A Wappalyzer API key in
WAPPALYZER_API_KEY
Install
cd /Users/elbert/Sites/wappalyzer/mcp
npm install
Run
WAPPALYZER_API_KEY=your_api_key npx wappalyzer-mcp
Environment variables:
WAPPALYZER_API_KEYrequiredWAPPALYZER_API_BASE_URLoptional, defaults tohttps://api.wappalyzer.com/v2/WAPPALYZER_METADATA_BASE_URLoptional, defaults toWAPPALYZER_API_BASE_URLWAPPALYZER_HTTP_TIMEOUT_MSoptional, defaults to30000
The server fails fast on startup if WAPPALYZER_API_KEY is missing.
Tools
`lookup_site`
Inputs:
urlrequiredliveoptional, defaultfalsesetsoptional, default[]denoiseoptional, defaulttruemax_ageoptional, default2
Notes:
- exactly one URL is accepted
recursive=falseis always forced- unsupported async-only parameters are not exposed
setsis limited tolocale,email,phone,contact,social,meta,security,trackers,company,keywords,signals,createdAt,events, andall
Output:
{
"request": {
"url": "https://www.wappalyzer.com/",
"live": false,
"sets": [
"company",
"contact"
],
"denoise": true,
"max_age": 2,
"recursive": false
},
"data": {},
"credits": {
"spent": 1,
"remaining": 99999
}
}
`lookup_subdomains`
Inputs:
domainrequiredlimitoptional, default100afteroptional
Notes:
- exactly one domain is accepted
limitmust be between10and1000and a multiple of10
Output:
{
"request": {
"domain": "example.com",
"limit": 100
},
"data": {},
"credits": {
"spent": 1,
"remaining": 99999
}
}
`get_credit_balance`
Output:
{
"credits": 99999
}
Resources
wappalyzer://technologieswappalyzer://technologies/{slug}wappalyzer://categorieswappalyzer://categories/{slug}
These resources are read-only and fetch public metadata from:
GET /technologies/GET /technologies/{slug}/GET /categories/GET /categories/{slug}/
Metadata resources do not send the API key and are cached in-process for 5 minutes.
Client Config
Claude Desktop
Add this to claude_desktop_config.json:
{
"mcpServers": {
"wappalyzer": {
"command": "node",
"args": [
"/Users/elbert/Sites/wappalyzer/mcp/index.js"
],
"env": {
"WAPPALYZER_API_KEY": "your_api_key"
}
}
}
}
Cursor
Add this to .cursor/mcp.json:
{
"mcpServers": {
"wappalyzer": {
"command": "node",
"args": [
"/Users/elbert/Sites/wappalyzer/mcp/index.js"
],
"env": {
"WAPPALYZER_API_KEY": "your_api_key"
}
}
}
}
ChatGPT
Use a remote MCP deployment when you need ChatGPT MCP connector support.
Development
Run automated tests:
npm test
Run live smoke tests with the local secret file:
npm run test:live