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