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