audit_website — Found17 MCP Prompt
audit_website
is one of 2 prompts on the
Found17
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke audit_website from your client
- Claude Code Found17 Prompt/audit_website run in your project directory
- Claude Desktop Found17 Prompt/audit_website ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Found17 Prompt/audit_website ~/.cursor/mcp.json
- VS Code Found17 Prompt/audit_website .vscode/mcp.json
- Zed Found17 Prompt/audit_website ~/.config/zed/settings.json
- Windsurf Found17 Prompt/audit_website ~/.codeium/windsurf/mcp_config.json
- Cline Found17 Prompt/audit_website ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Found17 Prompt/audit_website ~/.gemini/settings.json
- Grok Found17 Prompt/audit_website .mcp.json (in your project root)
- ChatGPT Found17 Prompt/audit_website Settings → Connectors → Advanced → Developer mode
- Claude.ai Found17 Prompt/audit_website Settings → Connectors → Add custom connector
- LangChain Found17 Prompt/audit_website pip install langchain-mcp-adapters
Other prompts on this server
Found17 also offers 2 resources — data you attach as context, where a prompt is something you run.
Read from the server itself, by connecting to it and calling prompts/list on 7 October 2026.
A listing does not declare its prompts, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each prompt's arguments.