Browser Tools
whipnode.com
WhipNode is a browser automation MCP server that fetches and uploads files, captures website screenshots, and renders HTML across device viewports for visual comparisons.
ENDPOINT 1
https://whipnode.com/api/v1/mcp
MCP server metadata
- Name
- whipnode
- Version
- 1.0.0
WhipNode gives you tools to work with visual context. When the user shares a whipnode.com URL, use whipnode_fetch to read it. When you need to see a website, use whipnode_capture. When checking responsive design, use whipnode_render. Use whipnode_help to show the user what's available.
Known tools 7
whipnode_renderRender HTML at multiple device viewports and produce screenshot comparisons.
Inferred read-onlywhipnode_statusShow your WhipNode connection status, active devices, and device groups.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.whipnode]
url = "https://whipnode.com/api/v1/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"whipnode": {
"type": "http",
"url": "https://whipnode.com/api/v1/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: whipnode
Remote MCP URL: https://whipnode.com/api/v1/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"whipnode": {
"url": "https://whipnode.com/api/v1/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"whipnode": {
"type": "http",
"url": "https://whipnode.com/api/v1/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "whipnode",
"transport": "streamable-http",
"url": "https://whipnode.com/api/v1/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.