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