Skip to main content
Glama
NautilusOSS

DorkFiMCP

by NautilusOSS

Related Servers

Alternatives to DorkFiMCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      Enables interaction with the DorkFi lending protocol on Voi and Algorand, supporting market discovery, position queries, liquidation scanning, and transaction preparation without signing or broadcasting.
      10
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with Tinyman AMM protocol on Algorand blockchain, supporting pool management, token swaps, liquidity operations, and analytics for both v1.1 and v2 protocols.
      7 npm
      1
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      Enables interaction with the LENDS protocol for lending, borrowing, PSM conversion, and staking, providing read-only tools and unsigned transaction construction without private key handling.
      37
      2 npm
      MIT
    • A
      license
      B
      quality
      F
      maintenance
      Provides AI assistants with access to real-time DeFi lending rates and yield data across 14+ protocols and multiple blockchains. Enables querying borrow/supply rates, comparing platforms, calculating leverage strategies, and finding best earn opportunities.
      6
      2 npm
      4
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with the Algorand blockchain through 25+ specialized tools for account management, payments, asset creation, NFT operations, and network monitoring. Supports both mainnet and testnet with instant finality and low fees.
      8 npm
      1
      MIT

    TDQS

    A3.8/5.0

    Scored across 21 tools

    Disambiguation3/5

    Most tools are distinct, but get_position, get_user, get_global_user, and get_health_factor all return overlapping user position data with only subtle differences, which can confuse an agent. Market-level getters and transaction builders are clearer, but the user-data cluster creates real selection ambiguity.

    Naming Consistency5/5

    The naming is highly consistent: read operations use the get_ prefix (except is_paused) and transaction builders use the _txn suffix. This predictable pattern makes the tool surface easy to navigate.

    Tool Count3/5

    At 21 tools, this server sits in the heavy 16-25 range, which feels like more than a typical MCP surface. The count is defensible given the depth of lending operations, but some user getter tools could be consolidated to reduce redundancy.

    Completeness5/5

    The tool set covers the full lending lifecycle: market data, user positions, deposits, borrows, repayments, withdrawals, liquidation, and admin/keeper actions like syncing and reserve withdrawals. There are no obvious dead ends for the stated purpose.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues