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