Enterprise DNA
M MCP Servers Developer low

namixai/funding-mcp

by Various

[](https://glama.ai/mcp/servers/namixai/funding-mcp) ๐Ÿ“‡ โ˜๏ธ - Multi-venue perpetual funding-rate data & cross-exchange funding arbitrage across 20+ exchanges (incl. HIP-3 sub-DEXes)

N

MCP

namixai/funding-mcp

Added 18 June 2026

Overview

Provides multi-venue perpetual funding-rate data and cross-exchange funding arbitrage signals across 20+ exchanges, including HIP-3 sub-DEXes. It aggregates funding rates from multiple sources to help traders identify arbitrage opportunities. The tool runs as an MCP server using JavaScript.

Best for

Best for
Developers building or integrating funding-rate-based arbitrage strategies

Use cases

  • Monitor funding rates across 20+ exchanges simultaneously
  • Identify cross-exchange funding arbitrage opportunities
  • Integrate funding data into trading bots or dashboards

Notes

Provides multi-venue perpetual funding-rate data and cross-exchange funding arbitrage signals across 20+ exchanges, including HIP-3 sub-DEXes. It aggregates funding rates from multiple sources to help traders identify arbitrage opportunities. The tool runs as an MCP server using JavaScript.

0 stars on GitHub. Last updated 2026-06-18.

Use cases

  • Monitor funding rates across 20+ exchanges simultaneously
  • Identify cross-exchange funding arbitrage opportunities
  • Integrate funding data into trading bots or dashboards

Pros

  • Covers a wide range of exchanges including sub-DEXes
  • Focuses on a specific, actionable trading metric (funding rate)
  • Open-source and extensible via MCP protocol

Cons

  • Zero stars on GitHub indicates early-stage or unproven adoption
  • No documentation or usage examples provided in the given facts
  • Requires running an MCP server, adding deployment overhead

Indexed from awesome-mcp-servers-punkpeye and enriched against its public facts.

Pros

  • Covers a wide range of exchanges including sub-DEXes
  • Focuses on a specific, actionable trading metric (funding rate)
  • Open-source and extensible via MCP protocol

Cons

  • Zero stars on GitHub indicates early-stage or unproven adoption
  • No documentation or usage examples provided in the given facts
  • Requires running an MCP server, adding deployment overhead