Skip to main content
Glama
Fuul MCP Server

Fuul MCP Server

by kuyen-labs

Related Servers

Alternatives to Fuul MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables users to set up and run an affiliate program from any MCP client in plain language, including planning commissions, creating campaigns, adding tracking, inviting affiliates, approving sales, and viewing payouts. It relays requests to a hosted backend using the user's sign-in or API key, with plan limits and audit logging applied.
      28
      284 npm
      2
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      MCP server for managing affiliate and referral programs. Track referrals, manage affiliates, process conversions, and handle payouts through AI assistants like Claude, Cursor, and ChatGPT.
      18
      81 npm
      2
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables advertisers and publishers to create and fund crypto ad campaigns, register sites, manage wallets, and withdraw earnings through the crawlproof network. Provides MCP tools for interacting with the associated web, API, and CLI services.
      46 npm
      1
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      MCP server for AI agent affiliate attribution and commission tracking. 7 tools for program discovery, conversion tracking, attribution token verification, and commission queries.
      7
      MIT

    TDQS

    A3.6/5.0

    Scored across 39 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, with detailed descriptions that help differentiate them. However, the large number of tools related to referrals and affiliates could cause some confusion for an agent.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case, such as list_chains, create_trigger, and approve_payouts. No mixed conventions are observed.

    Tool Count3/5

    39 tools is on the higher side for a single server, covering a broad API surface. While the complexity of the domain may justify the count, it risks overwhelming agents and could benefit from splitting into sub-servers.

    Completeness4/5

    The tool set covers CRUD operations for most entities and includes essential workflows like event tracking and payouts. However, the absence of a 'publish' operation (noted as required externally) is a notable gap.