Skip to main content
Glama

Related Servers

Alternatives to Sjothr MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to read multi-chain memecoin launchpad data including coins, burns, staking, fee boards, and read-only perps markets, while calculating quotes and preparing buys, sells, stakes, unstakes, and launches for the user’s own wallet to sign.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI agents and MCP clients to read live isolated lending vault data on Base, including rates, liquidity, deployed contracts, liquidation bot commands, and protocol guides, without keys or signing.
      6
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Exposes three read-only MCP tools for previewing Base token market data, evaluating USDC spend against SpendGuard policies before funds move, and discovering x402 payment challenges without signing or paying.
      Apache 2.0
    • A
      license
      A
      quality
      D
      maintenance
      A read-only MCP server that exposes BaseZap's tipping-agent tools to any MCP client, allowing users to fetch platform info, compute USDC tip quotes, build unsigned ERC-20 transfer calldata, and resolve Farcaster usernames to wallet addresses.
      4
      9 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Provides read-only access to public referral deals and codes, races and leaderboards, DeFi interface restriction data, x402 catalogs, cp0x facts, and open-source repository listings. Supports natural-language queries such as finding deals for a venue or checking interface restrictions by country.
      12
      MIT

    TDQS

    B3.4/5.0

    Scored across 5 tools

    Disambiguation4/5

    Most tools target clearly different things: list campaigns, get one campaign, get raise rules, search, and fetch-by-id. The main risk is sjothr_campaigns vs sjothr_campaign, which differ by a single letter and rely on the descriptions to distinguish list from single-record. search/fetch are cleanly paired since search explicitly returns ids for fetch.

    Naming Consistency3/5

    The three domain tools use a consistent sjothr_<noun> prefix, but search and fetch are bare generic verbs with no namespace, creating a mixed convention. All names are snake_case and readable, but the set is not a single predictable pattern.

    Tool Count4/5

    Five tools is reasonable for a read-only public-record server, and each has a defensible role. It is on the thin side given the surface spans both campaigns and guides, but nothing is redundant.

    Completeness4/5

    The read-only lifecycle (browse list, get detail, get rules, search, fetch full text) is covered, and search+fetch together handle guides. Minor gaps exist: no way to list guides directly or filter campaigns by state/token without going through search.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues