intel_site_audit — WebLens MCP Tool
intel_site_audit
(intel site audit) is one of 36 tools on the
WebLens
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call intel_site_audit from your client
- Claude Code WebLens intel_site_audit run in your project directory
- Claude Desktop WebLens intel_site_audit ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor WebLens intel_site_audit ~/.cursor/mcp.json
- VS Code WebLens intel_site_audit .vscode/mcp.json
- Zed WebLens intel_site_audit ~/.config/zed/settings.json
- Windsurf WebLens intel_site_audit ~/.codeium/windsurf/mcp_config.json
- Cline WebLens intel_site_audit ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI WebLens intel_site_audit ~/.gemini/settings.json
- Grok WebLens intel_site_audit .mcp.json (in your project root)
- ChatGPT WebLens intel_site_audit Settings → Connectors → Advanced → Developer mode
- Claude.ai WebLens intel_site_audit Settings → Connectors → Add custom connector
- LangChain WebLens intel_site_audit pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http weblens https://api.weblens.dev/mcpOther tools on this server
- preview_endpoint
- fetch_webpage
- fetch_webpage_pro
- screenshot
- search_web
- search_news
- search_images
- search_places
- search_shopping
- search_scholar
- search_autocomplete
- search_trends
- youtube_transcript
- get_contents
- answer_question
- extract_data
- smart_extract
- research
- deep_research
- extract_pdf
- compare_urls
- batch_fetch
- domain_intel
- project_due_diligence
- package_intel
- detect_tech
- search_discussions
- map_site
- crawl_site
- fetch_resilient
- intel_company
- intel_market
- intel_competitive
- monitor_create
- memory_set
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.