Skip to main content
Glama
Sign In
stellar-expert-mcp

stellar-expert-mcp

by Bran18
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to stellar-expert-mcp

No user-submitted related servers found.

    Related Servers

    • stellar-pulse-mcp

      markankamaransheogarat-sys
      A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to query read-only Stellar analytics over MCP: network status and fees, asset data with look-alike warnings, SDEX order books, account balances with spendable XLM, and DeFi TVL. It requires no API keys and refuses secret keys, answering from public APIs like Horizon, StellarExpert and DefiLlama.
      6
      70 npm
      MIT

    • yellow-pages

      ethank64
      F
      license
      A
      quality
      D
      maintenance
      Exposes two MCP tools (discover and execute) that enable agents to query an OpenAPI schema via natural language and execute matched API operations.
      2
      -

    • Polymarket MCP

      falconaipro
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP hosts like Claude and Cursor to query Polymarket data via Falcon AI's external API, including market listings, order books, and trader stats.
      MIT

    • @xrpl-utilities/mcp

      XRPL-Utilities
      A
      license
      B
      quality
      B
      maintenance
      Exposes 17 read-only tools from six XRPL-Utilities services so AI agents can access XRPL wallet analysis, signal feeds, macro telemetry, permissioned asset stacks, RWA tracking, and ETF flow data.
      41
      7,210 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 12 tools

    Disambiguation4/5

    Most tools target clearly distinct resources: directory (tags/entries/single lookup), blocked domains (list/check), assets (list/rating/supply/holders/rank), and ledger-time conversions. Slight overlap exists between list_directory_entries and get_directory_entry, and between list_assets and get_asset_rating, but descriptions explicitly steer the agent toward the right tool (e.g. 'prefer check_blocked_domain for a single hostname').

    Naming Consistency4/5

    Almost all tools follow a verb_noun snake_case pattern (list_*, get_*, check_*), with clear parallelism between paired tools (list/check blocked domains, list/get directory entries). The two ledger tools deviate by using a noun-based construction (ledger_sequence_from_timestamp / ledger_timestamp_from_sequence), though they are internally consistent with each other.

    Tool Count5/5

    Twelve tools is well within a comfortable range and each maps to a distinct lookup operation in the StellarExpert data domain. No filler or redundant tools are apparent.

    Completeness4/5

    The surface covers directory lookup, blocked-domain checks, asset discovery/rating/supply/holders, and ledger-time conversion comprehensively for those subdomains. Gaps exist for other plausible StellarExpert data (e.g. trade/market history, payments, account operation listings), but agents can work around most of these via the existing asset and directory tools.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Resources