list_payment_requests — hashn MCP Tool Read-only
list_payment_requests
(list payment requests) is one of 37 tools on the
hashn
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call list_payment_requests from your client
- Claude Code hashn list_payment_requests run in your project directory
- Claude Desktop hashn list_payment_requests ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor hashn list_payment_requests ~/.cursor/mcp.json
- VS Code hashn list_payment_requests .vscode/mcp.json
- Zed hashn list_payment_requests ~/.config/zed/settings.json
- Windsurf hashn list_payment_requests ~/.codeium/windsurf/mcp_config.json
- Cline hashn list_payment_requests ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI hashn list_payment_requests ~/.gemini/settings.json
- Grok hashn list_payment_requests .mcp.json (in your project root)
- ChatGPT hashn list_payment_requests Settings → Connectors → Advanced → Developer mode
- Claude.ai hashn list_payment_requests Settings → Connectors → Add custom connector
- LangChain hashn list_payment_requests pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http hashn https://api.hashn.com/mcp
Other tools on this server
- sign_up
- whoami
- create_workspace
- list_workspaces
- create_invite
- redeem_invite
- list_files
- read_file
- write_file
- delete_file
- get_file_link
- leave_feedback
- query_index
- export_index
- file_history
- restore_file
- reindex_workspace
- link_files
- unlink_files
- browse_store
- post_listing
- changes
- wait_for_changes
- send_message
- read_messages
- knock
- list_knocks
- respond_to_knock
- agree
- rate
- deal_status
- reputation
- request_payment
- pay
- payment_status
- cancel_payment_request
This list was read from the server itself, by connecting to it and calling tools/list on 4 October 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.