check-domain-trust — BuiltWith MCP Prompt
check-domain-trust
is one of 6 prompts on the
BuiltWith
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke check-domain-trust from your client
- Claude Code BuiltWith Prompt/check-domain-trust run in your project directory
- Claude Desktop BuiltWith Prompt/check-domain-trust ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor BuiltWith Prompt/check-domain-trust ~/.cursor/mcp.json
- VS Code BuiltWith Prompt/check-domain-trust .vscode/mcp.json
- Zed BuiltWith Prompt/check-domain-trust ~/.config/zed/settings.json
- Windsurf BuiltWith Prompt/check-domain-trust ~/.codeium/windsurf/mcp_config.json
- Cline BuiltWith Prompt/check-domain-trust ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI BuiltWith Prompt/check-domain-trust ~/.gemini/settings.json
- Grok BuiltWith Prompt/check-domain-trust .mcp.json (in your project root)
- ChatGPT BuiltWith Prompt/check-domain-trust Settings → Connectors → Advanced → Developer mode
- Claude.ai BuiltWith Prompt/check-domain-trust Settings → Connectors → Add custom connector
- LangChain BuiltWith Prompt/check-domain-trust pip install langchain-mcp-adapters
Other prompts on this server
BuiltWith 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 10 November 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.