assay_verify_delivery — assay MCP Tool
assay_verify_delivery
(assay verify delivery) is one of 4 tools on the
assay
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call assay_verify_delivery from your client
- Claude Code assay assay_verify_delivery run in your project directory
- Claude Desktop assay assay_verify_delivery ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor assay assay_verify_delivery ~/.cursor/mcp.json
- VS Code assay assay_verify_delivery .vscode/mcp.json
- Zed assay assay_verify_delivery ~/.config/zed/settings.json
- Windsurf assay assay_verify_delivery ~/.codeium/windsurf/mcp_config.json
- Cline assay assay_verify_delivery ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI assay assay_verify_delivery ~/.gemini/settings.json
- Grok assay assay_verify_delivery .mcp.json (in your project root)
- ChatGPT assay assay_verify_delivery Settings → Connectors → Advanced → Developer mode
- Claude.ai assay assay_verify_delivery Settings → Connectors → Add custom connector
- LangChain assay assay_verify_delivery pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http assay https://assay-207908449630.us-central1.run.app/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 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.