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