scan_html — OnPage.dev MCP Tool
scan_html
(scan html) is one of 20 tools on the
OnPage.dev
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call scan_html from your client
- Claude Code OnPage.dev scan_html run in your project directory
- Claude Desktop OnPage.dev scan_html ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor OnPage.dev scan_html ~/.cursor/mcp.json
- VS Code OnPage.dev scan_html .vscode/mcp.json
- Zed OnPage.dev scan_html ~/.config/zed/settings.json
- Windsurf OnPage.dev scan_html ~/.codeium/windsurf/mcp_config.json
- Cline OnPage.dev scan_html ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI OnPage.dev scan_html ~/.gemini/settings.json
- Grok OnPage.dev scan_html .mcp.json (in your project root)
- ChatGPT OnPage.dev scan_html Settings → Connectors → Advanced → Developer mode
- Claude.ai OnPage.dev scan_html Settings → Connectors → Add custom connector
- LangChain OnPage.dev scan_html pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http onpage https://onpage.dev/mcpOther tools on this server
- scan_page
- check_ai_visibility
- check_focus_keyword
- get_fix_pack
- rescan_and_compare
- check_snippet
- generate_schema
- find_answer_passages
- generate_llms_txt
- ai_crawler_policy
- deep_audit
- check_urls
- test_robots
- validate_schema
- compare_html
- start_site_audit
- get_site_audit
- suggest_internal_links
- compare_pages
This list was read from the server itself, by connecting to it and calling tools/list on 6 October 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.