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