stellar-expert-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | Bind address. Use 0.0.0.0 behind a reverse proxy. | 127.0.0.1 |
| PORT | No | Listen port for the HTTP server. | 3000 |
| ALLOWED_HOSTS | No | Comma-separated Hostnames when binding non-localhost. | |
| STELLAR_EXPERT_NETWORK | No | Default network for asset/ledger tools (public or testnet). | public |
| STELLAR_EXPERT_API_BASE | No | API origin for StellarExpert. | https://api.stellar.expert |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_directory_entriesA | Search the StellarExpert curated Directory of well-known accounts. Filter by address list, tags (exchange, anchor, issuer, wallet, custodian, malicious, unsafe, personal, sdf, memo-required, airdrop, defi), or a search string (name/domain/address, min 5 chars). Use for reverse lookups, scam checks (tag malicious/unsafe), and labeling counterparties. |
| get_directory_entryA | Look up one Stellar account in the Directory. Returns name, domain, and tags when listed. An empty object (or 404) means the account is not in the Directory — it may still exist on-chain. |
| list_directory_tagsA | List all Directory tag categories (name + description) used to classify well-known and reported accounts. |
| list_blocked_domainsA | List domains reported for fraudulent Stellar-related activity. Paginated Horizon-style response. Prefer check_blocked_domain for a single hostname. |
| check_blocked_domainA | Check whether a domain (or its registrable parent) is on the StellarExpert blocked-domains list. Use before linking or recommending a Stellar-related URL. |
| list_assetsA | List Stellar assets with on-chain stats and StellarExpert composite rating. Search by code, issuer, home domain, or stellar.toml metadata. Sort by rating (default), created, payments, trades, trustlines, volume, or volume7d. Use to find or rank assets; rating is technical (age, activity, liquidity, SEP metadata), not an investment recommendation. |
| get_asset_ratingA | Fetch StellarExpert composite technical rating for one asset (age, trades, payments, trustlines, volume7d, interoperability, liquidity, average). Ledger-activity based; not financial advice. |
| list_asset_holdersA | List accounts holding a non-zero balance of an asset, sorted by balance. Zero-balance trustlines are omitted. Horizon-style paging. |
| get_asset_holder_rankA | Get an account’s relative balance rank among holders of an asset (position and total holder count). |
| get_asset_supplyB | Return total issued supply for an asset as plain text (useful for aggregators and dashboards). Native XLM and CODE-ISSUER identifiers are accepted. |
| ledger_sequence_from_timestampA | Resolve the ledger sequence whose close time is equal to or before the given timestamp (UNIX seconds or RFC 3339). Returns 404 if the time is before the first ledger or in the future. |
| ledger_timestamp_from_sequenceB | Resolve the close timestamp (UNIX + ISO date) for a given ledger sequence. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| check-address-safety | Look up a Stellar account in the Directory and report malicious, unsafe, memo-required, and other tags. |
| lookup-asset | Find an asset, then fetch rating and supply from StellarExpert. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| docs | Pointer and summary of the official StellarExpert Open API used by this MCP |
TDQS
Scored across 12 tools
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').
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.
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.
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.