MCP server wrapper for Whatweb — Web technology identification and fingerprinting.
Whatweb (whatweb) is a security tool that provides: Web technology identification and fingerprinting.
See urbanadventurer/WhatWeb for full documentation.
No API keys required — Whatweb runs locally inside the Docker container.
Summary. MCP server wrapper for Whatweb — Web technology identification and fingerprinting.
Tools:
run_whatweb — Run whatweb with the given arguments. Returns structured JSON output.run_whatwebRun whatweb with the given arguments. Returns structured JSON output.
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
arguments | string | Yes | — | Command-line arguments (e.g. "--help") |
timeout_seconds | integer | No | 600 | Maximum execution time in seconds |
{
"raw": "whatweb output will appear here"
}
Here are example prompts you can use with Claude (or any MCP client) when this tool is connected:
docker-compose up -d
docker run -i --rm hackerdogs/whatweb-mcp:latest
docker run -d -p 8281:8281 \
-e MCP_TRANSPORT=streamable-http \
-e MCP_PORT=8281 \
hackerdogs/whatweb-mcp:latest
Add to your Claude Desktop or Cursor MCP config:
{
"mcpServers": {
"whatweb-mcp": {
"command": "docker",
"args": ["run", "-i", "--rm", "-e", "MCP_TRANSPORT", "hackerdogs/whatweb-mcp:latest"],
"env": {
"MCP_TRANSPORT": "stdio"
}
}
}
}
First, start the server using Docker Compose or docker run with HTTP mode (see Deploy above), then point your MCP client at the running server:
{
"mcpServers": {
"whatweb-mcp": {
"url": "http://localhost:8281/mcp"
}
}
}
When to use HTTP mode: HTTP mode is ideal for shared/remote deployments, multi-user setups, and Hackerdogs scheduled prompts. The server runs as a long-lived process and accepts connections from multiple MCP clients concurrently.
| Variable | Default | Description |
|---|---|---|
MCP_TRANSPORT | stdio | Transport mode: stdio or streamable-http |
MCP_PORT | 8281 | HTTP port (only used with streamable-http) |
The fastest way to get started is through Hackerdogs:
Give it a couple of minutes to go live. Then start querying by asking Hackerdogs to use the tool explicitly (e.g. "Use naabu to scan example.com"). If you don't specify, Hackerdogs will automatically choose the best tool for the job — it may choose this one on its own.
Want to contribute or chat with the team? Join our Discord.
docker build -t hackerdogs/whatweb-mcp:latest .
./test.sh
1. Start the server in HTTP mode:
docker run -d --rm --name whatweb-mcp-test -p 8281:8281 \
-e MCP_TRANSPORT=streamable-http \
hackerdogs/whatweb-mcp:latest
2. Initialize the MCP session:
SESSION_ID=$(curl -s -D - -X POST http://localhost:8281/mcp \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"test","version":"0.1"}}}' \
2>&1 | grep -i mcp-session-id | awk '{print $2}' | tr -d '\r\n')
curl -s -X POST http://localhost:8281/mcp \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-H "mcp-session-id: $SESSION_ID" \
-d '{"jsonrpc":"2.0","method":"notifications/initialized"}'
3. Call a tool:
curl -s -X POST http://localhost:8281/mcp \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-H "mcp-session-id: $SESSION_ID" \
-d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"run_whatweb","arguments":{"arguments":"--help"}}}'
4. Clean up:
docker stop whatweb-mcp-test
You can run the whatweb CLI in the same container by overriding the entrypoint to identify web technologies without starting the MCP server.
Scan URL:
docker run -i --rm --entrypoint whatweb hackerdogs/whatweb-mcp:latest https://example.com
Show help:
docker run -i --rm --entrypoint whatweb hackerdogs/whatweb-mcp:latest --help
Content type
Image
Digest
sha256:a2b409b0c…
Size
82.9 MB
Last updated
3 months ago
docker pull hackerdogs/whatweb-mcp