Sjothr MCP Server
Related Servers
Alternatives to Sjothr MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables 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

CantorFi MCP serverofficial
AlicenseAqualityCmaintenanceEnables 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.6MIT- AlicenseNot gradedqualityCmaintenanceExposes 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
- AlicenseAqualityCmaintenanceThe x402 ecosystem's read MCP for Base. Verify on-chain USDC settlements, parse publisher manifests, and audit x402 payment receipts from any MCP-compatible AI agent.11115 npm2MIT
- AlicenseAqualityDmaintenanceA 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.49 npmMIT
- AlicenseAqualityBmaintenanceProvides 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.12MIT
TDQS
Scored across 5 tools
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.
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.
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.
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.