verify_external_source — Taste MCP Tool
verify_external_source
(verify external source) is one of 20 tools on the
Taste
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call verify_external_source from your client
- Claude Code Taste verify_external_source run in your project directory
- Claude Desktop Taste verify_external_source ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Taste verify_external_source ~/.cursor/mcp.json
- VS Code Taste verify_external_source .vscode/mcp.json
- Zed Taste verify_external_source ~/.config/zed/settings.json
- Windsurf Taste verify_external_source ~/.codeium/windsurf/mcp_config.json
- Cline Taste verify_external_source ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Taste verify_external_source ~/.gemini/settings.json
- Grok Taste verify_external_source .mcp.json (in your project root)
- ChatGPT Taste verify_external_source Settings → Connectors → Advanced → Developer mode
- Claude.ai Taste verify_external_source Settings → Connectors → Add custom connector
- LangChain Taste verify_external_source pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http taste-mcp https://api.humantaste.app/mcp/Other tools on this server
- list_offerings
- list_expert_profiles
- get_result
- prepare_consult_domain_expert
- request_think_tank_revision
- request_illustration_revision
- review_content
- verify_reasoning_chain
- prepublish_review
- predict_audience_reaction
- arbitrate_dispute
- request_human_approval
- verify_certificate
- order_think_tank_session_30
- order_think_tank_session_60
- consult_domain_expert
- ask_a_human
- review_plan
- review_code
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.