tx_decode — Presend MCP Server MCP Tool
tx_decode
(tx decode) is one of 37 tools on the
Presend MCP Server
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call tx_decode from your client
- Claude Code Presend MCP Server tx_decode run in your project directory
- Claude Desktop Presend MCP Server tx_decode ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Presend MCP Server tx_decode ~/.cursor/mcp.json
- VS Code Presend MCP Server tx_decode .vscode/mcp.json
- Zed Presend MCP Server tx_decode ~/.config/zed/settings.json
- Windsurf Presend MCP Server tx_decode ~/.codeium/windsurf/mcp_config.json
- Cline Presend MCP Server tx_decode ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Presend MCP Server tx_decode ~/.gemini/settings.json
- Grok Presend MCP Server tx_decode .mcp.json (in your project root)
- ChatGPT Presend MCP Server tx_decode Settings → Connectors → Advanced → Developer mode
- Claude.ai Presend MCP Server tx_decode Settings → Connectors → Add custom connector
- LangChain Presend MCP Server tx_decode pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http presend-mcp https://presend.pages.dev/mcpOther tools on this server
- address_risk
- ai_crawler_check
- base64
- color
- csv_json
- dns_lookup
- email_disposable
- email_security
- email_validate
- email_verify
- favicon
- ip
- ip_reputation
- jwt_decode
- jwt_verify
- maintainer_change_check
- password
- password_breach
- password_check
- phone_verify
- redirect_trace
- repo_health_check
- rpc_check
- security_headers
- security_scan
- subdomains
- supply_chain_check
- text_similarity
- timestamp
- typosquat_check
- url_clean
- url_reputation
- user_agent
- uuid
- vulnerability_check
- whois_lookup
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.