MCP

Use the hosted Wappalyzer MCP server at https://mcp.wappalyzer.com/mcp to expose Wappalyzer data as MCP tools and resources inside AI clients that support remote MCP over HTTP and OAuth.

The hosted service is read-only. You sign in with your Wappalyzer account during setup, and the server reads your existing API key on your behalf. You do not need to paste the key into the MCP client.

The hosted MCP endpoint is https://mcp.wappalyzer.com/mcp.

To connect, sign in with a Wappalyzer account that already has an API key at /apikey/. During setup, the hosted server reads that existing key and stores an encrypted copy for runtime calls.

The hosted implementation lives in a separate repository: github.com/wappalyzer/mcp-hosted.

Use the management page to inspect or remove an active hosted link: mcp.wappalyzer.com/manage.

The MCP server exposes three tools:

lookup_site accepts a single url plus optional live, sets, denoise, and max_age inputs. The MCP wrapper always sends recursive=false, so the call stays synchronous even when live=true. Responses include the original request, structured result data, and normalized credit usage.

Supported sets values are locale, email, phone, contact, social, meta, security, company, keywords, signals, createdAt, events, and all.

lookup_subdomains accepts a single domain, optional after pagination, and a limit between 10 and 1000 in steps of 10. Responses also include normalized credit usage information.

The MCP server exposes four read-only metadata resources:

• wappalyzer://technologies
• wappalyzer://technologies/{slug}
• wappalyzer://categories
• wappalyzer://categories/{slug}

These resources read from Wappalyzer's public metadata endpoints and do not send your API key. Responses are cached in-process for 5 minutes to reduce repeated reads during a session.

Any MCP client that supports a remote Streamable HTTP server with OAuth can use the hosted endpoint.

Codex

codex mcp add wappalyzer --url https://mcp.wappalyzer.com/mcp
codex mcp login wappalyzer

After signing in, ask Codex to use the Wappalyzer MCP server for a site lookup, subdomain lookup, or credit-balance check.

ChatGPT developer mode

Add https://mcp.wappalyzer.com/mcp as a remote MCP app in ChatGPT developer mode, then complete the Wappalyzer OAuth flow during connection.

The same endpoint can also be used in other remote MCP clients that support OAuth and dynamic client registration.

If you want a local stdio server instead of the hosted endpoint, use the open source package in github.com/wappalyzer/mcp.

The local package requires Node.js 20 or newer and WAPPALYZER_API_KEY.

Optional environment variables for the local package:

• WAPPALYZER_API_BASE_URL defaults to https://api.wappalyzer.com/v2/
• WAPPALYZER_METADATA_BASE_URL defaults to WAPPALYZER_API_BASE_URL
• WAPPALYZER_HTTP_TIMEOUT_MS defaults to 30000

git clone https://github.com/wappalyzer/mcp.git
cd mcp
npm install
WAPPALYZER_API_KEY=your_api_key npx wappalyzer-mcp

The local package remains useful for clients that prefer a local stdio transport, including local MCP setups in tools such as Claude Desktop and Cursor.