hogswap-mcp
Related Servers
Alternatives to hogswap-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceMCP server that builds unsigned Paraswap token swap transactions for self-custody wallets, holding no keys and signing nothing. It returns raw transaction data for a human to review and approve before execution.1MIT No Attribution
- AlicenseBqualityCmaintenanceMCP server for Autonomous Intelligence, enabling AI agents to perform non-custodial, rug-gated multi-chain token swaps including safety checks, quotes, and execution.717 npmMIT
- AlicenseAqualityCmaintenanceMCP server for non-custodial token swaps and honeypot/rug-pull safety checks across 8 blockchains, with free quotes and paid x402-based transaction builds and security screenings.626 npm1MIT
- AlicenseAqualityDmaintenanceMCP server providing cross-chain swaps between Solana and Base for AI agents paid for via x402 micropayments.328 npm2MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server for agentic commerce, enabling AI agents to discover services, make x402 payments with USDC across multiple chains, and manage crypto wallets and token swaps.335 npm1MIT
- AlicenseNot gradedqualityBmaintenanceMCP server for agent-native and human-accessible payments using MPP and x402 protocols, enabling payment flows from CLI or agent hosts.3 npmMIT
TDQS
Scored across 8 tools
Each tool targets a distinct action in the HOGSWAP workflow: listing assets, checking balance, getting quotes, building swaps, paying invoices, registering, verifying, and creating credit offers. The sequential dependencies (quote -> build -> pay; register -> verify) are clear, and no two tools appear to duplicate functionality.
All tool names follow a consistent verb_noun snake_case pattern: list_, get_, build_, pay_, register_, verify_. There is a minor mix of 'list' vs 'get' for retrieval operations, but it is semantically appropriate (listing a collection vs fetching a specific balance/quote), and the overall convention is uniform.
With 8 tools, the server is well-scoped for its purpose—covering authentication, asset discovery, quoting, swap construction, invoice payment, balance checking, and credit top-ups. Each tool earns its place, and the count sits comfortably within the ideal 3-15 range.
The tool surface fully covers the core lifecycle: registration (register_agent + verify_registration), credit management (get_balance, get_credit_offer, pay_x402_invoice), and swap execution (list_payable_assets, get_quote, build_swap). Transaction submission is intentionally external for security, so there are no dead ends in the workflow.