StellarMCP
Related Servers
Alternatives to StellarMCP
No user-submitted related servers found.
Related Servers
- AlicenseCqualityAmaintenanceAn MCP server that gives AI agents real-time market data, DeFi intelligence, and automatic tool discovery via plugins. Supports x402 micropayments and is always updated.23MIT
- FlicenseAqualityNot gradedmaintenanceAn MCP server that transforms SKILL.md files into executable tools for AI agents, allowing them to discover and pay for services via the x402 protocol. It supports automatic payments on Stellar and EVM networks, enabling seamless integration of premium API skills.65 npm1-
- FlicenseNot gradedqualityCmaintenanceAn MCP server for AI agents to purchase resources via Stellar testnet USDC, handling quotes, purchase URLs, and merchant receipts.-
- AlicenseNot gradedqualityDmaintenanceMCP server with X402 payment integration, enabling AI agents to access paid tools like weather, web search, and image generation with crypto payments via MetaMask on Base network.MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides DeFi data tools (crypto prices, whale concentration, funding rates) for AI agents via the x402 protocol.10 npm1MIT
- AlicenseBqualityDmaintenanceAn MCP server providing 22 pay-per-call utility tools for AI agents (scrape, validate, embed, store, moderate, notify, convert, prevent loops) without accounts or API keys, using USDC payments via the x402 protocol.1738 npm1MIT
TDQS
Scored across 17 tools
Most tools are clearly distinct, but getTradeAggregations and getPriceHistory both provide OHLC data from SDEX trade aggregations, making their boundary unclear. getPrice and getOrderbook also overlap around price discovery, so an agent could easily select the wrong tool for a price query.
All tools follow a consistent camelCase verb_noun pattern using 'get' plus the resource name, such as getAccount, getLedger, and getLiquidityPools. There is no mixing of naming conventions or ambiguous verb styles.
At 17 tools, the server sits in the 'heavy' range, though each tool does target a distinct Stellar data resource. The count is defensible for a broad read-only Stellar data API but is slightly more than the typical well-scoped server.
The server covers a wide range of Stellar data resources: accounts, transactions, payments, operations, effects, ledgers, assets, DEX orderbooks, trades, offers, liquidity pools, claimable balances, network status, and Soroban token info. Minor gaps exist, such as fetching a single transaction by hash or listing ledgers, but most core read-only workflows are covered.