verify_evidence_package — dokimo mcp MCP Tool
verify_evidence_package
(verify evidence package) is one of 3 tools on the
dokimo mcp
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call verify_evidence_package from your client
- Claude Code dokimo mcp verify_evidence_package run in your project directory
- Claude Desktop dokimo mcp verify_evidence_package ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor dokimo mcp verify_evidence_package ~/.cursor/mcp.json
- VS Code dokimo mcp verify_evidence_package .vscode/mcp.json
- Zed dokimo mcp verify_evidence_package ~/.config/zed/settings.json
- Windsurf dokimo mcp verify_evidence_package ~/.codeium/windsurf/mcp_config.json
- Cline dokimo mcp verify_evidence_package ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI dokimo mcp verify_evidence_package ~/.gemini/settings.json
- Grok dokimo mcp verify_evidence_package .mcp.json (in your project root)
- ChatGPT dokimo mcp verify_evidence_package Settings → Connectors → Advanced → Developer mode
- Claude.ai dokimo mcp verify_evidence_package Settings → Connectors → Add custom connector
- LangChain dokimo mcp verify_evidence_package pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http dokimo-mcp https://dokimo.augaster.com/mcpOther tools on this server
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.