Galactic
Server Details
On-chain asset, market, and GPU price data for galactic.inc.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 6 tools
Each tool targets a distinct resource: list_assets vs get_asset is a clean list/detail split, market_totals is the only aggregate, and compute_vaults, gpu_price_index, and search_news cover non-overlapping domains. The descriptions explicitly state when to call one over the other (e.g. get_asset after list_assets, market_totals vs per-asset figures), leaving no realistic misselection path.
All names are snake_case and four follow a verb_noun pattern (compute_vaults, get_asset, list_assets, search_news). Two are noun-only (gpu_price_index, market_totals), a minor deviation but still predictable and readable.
Six tools is well-scoped for a read-only market-data API: one per data domain (assets, aggregates, vaults, GPU index, news) with a paired list/detail for assets. No tool feels redundant or missing for the stated surface.
The surface covers listing, detail, market aggregates, news, vault metrics, and GPU indices, with pagination fields present on list_assets. Minor gaps remain: no dedicated issuer entity tool, no enumeration of chains/categories, and get_asset is the only path to per-chain data, but these are workable around the existing endpoints.
Available Tools
6 toolscompute_vaultsARead-onlyInspect
On-chain figures for the USD.AI and GAIB compute vaults.
Call this for tokens outstanding, vault share price, and the trailing 90-day figure. trailing_90d_apy_percent annualizes the change in vault share price over the trailing window. It is not an issuer-quoted yield. loan_count and loan_balance_usd (US dollars) are present only when the loan book is read on-chain.
JSON: {"as_of", "vaults": [{id, name, tokens, share_price_symbol, tokens_outstanding_usd, share_price, trailing_90d_apy_percent, read_at, loan_count, loan_balance_usd}]}. Unknown id: {"error": "not_found", "query", "vaults": [ids]}.
Inputs: asset, response_format.
get_assetARead-onlyInspect
One published asset, with per-chain supply and an optional daily price history.
Call this after list_assets, or when the id is already known. Pass the id from an ambiguous result. Do not guess among assets that share a display ticker.
JSON is the asset card plus by_chain (chain, supply, market_cap_usd, holders where published) and history ([{date, price_usd}], newest days only, only when the price is published). Unknown id: {"error": "not_found", "query"}. Shared ticker: {"error": "ambiguous", "query", "matches": [{id, ticker, display_ticker, name, chains}]}. An announced id returns the listing with status upcoming and no figures. Units match list_assets. Price history values are US dollars per token.
Inputs: id (required), history_days, response_format.
gpu_price_indexARead-onlyInspect
Latest GPU rental price index families, in US dollars per GPU-hour.
Call this for the current index level of a GPU model in one market segment. Omit model for every model. Pass one model name for that model only.
Each family is one model, one segment (HYP hyperscaler, PUBNEO public neocloud, PRIVNEO private neocloud, MKT marketplace), and one price class (OD on-demand, MK marketplace ask, SP spot), with id IG.... Segments are never combined, and no cross-segment figure is returned. A published family has median_usd_per_gpu_hour, p25_usd_per_gpu_hour, p75_usd_per_gpu_hour, and providers; it needs at least 3 providers after a 3-MAD filter. Any other family has status and providers only. Unknown model: {"error": "not_found", "query", "models": [names]}.
Inputs: model, response_format.
list_assetsARead-onlyInspect
List published tokenized assets.
Call this to find an asset by ticker, name, category, chain, or issuer before get_asset. Live assets are the galactic.inc screener universe. Announced listings have a launch date and no supply, price, or holders.
JSON shape: {"matched", "offset", "limit", "assets": [cards], "upcoming": [cards]}. A card includes id, ticker, display_ticker, name, category, category_label, chains, chain_ids, and status. Figures appear only when their check passed: supply (token supply), price_usd and market_cap_usd (US dollars), holders (address count), top10_share (fraction of supply from 0 to 1), change_1d_percent, change_7d_percent, change_30d_percent, supply_change_30d_percent, volume_30d_usd (US dollars), transfers_30d. Price and market cap require an on-chain price check that passed. Holders require balances that reconcile. Issuer is omitted when the issuer did not resolve. Omitted fields are unpublished, not zero. as_of is the asset's data time in UTC.
Inputs: chain, limit, query, issuer, +4 more.
market_totalsARead-onlyInspect
Category and chain totals for the published asset universe.
Call this for asset counts, pricing coverage, and holder totals. The aggregate market cap is published only when every listed asset has a published on-chain price. Until then market_cap_usd is null, market_cap_withheld is true, every by_category and by_chain row leaves out market_cap_usd, and coverage says how many listed assets are priced. Per-asset market caps from list_assets and get_asset are not affected. When every listed asset is priced, market_cap_usd sums them and each row carries its own market_cap_usd. holders sums only assets with a published holder count. holder_assets is how many assets contributed, so a missing holder count is not treated as zero. Per-chain holder counts include a chain only when that chain published holders.
JSON: {"listed_assets", "priced_assets", "market_cap_usd", "market_cap_withheld", "coverage", "holders", "holder_assets", "by_category": [{category, category_label, assets, priced_assets, market_cap_usd, holders, holder_assets}], "by_chain": [{chain_id, chain, assets, priced_assets, market_cap_usd, holders, holder_assets}], "ethereum_block", "ethereum_block_time", "note"}. An asset on more than one chain is counted in each of those chains. holders is omitted on a row that has no published holder counts. Market cap is US dollars. Each asset keeps its own as_of; chain-native assets can differ from the Ethereum block time.
Inputs: response_format.
search_newsARead-onlyInspect
Search approved galactic.inc newsroom items.
Call this for recent headlines about an asset, an issuer, or a topic. Items that are not approved are omitted. The response has no source URL.
JSON: {"matched", "items": [{id, date, category, headline, lede, assets}]}. assets is a list of tickers. date is YYYY-MM-DD. limit defaults to 8.
Inputs: limit, query, response_format.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
GPU compute-asset identity registry: resolve device identity, verify history, buy official reports.
Raw and normalized on-chain data: balances, transactions, blocks and Ethereum validator activity.
Live GPU rental and LLM inference prices across dozens of providers, plus GPU price forecasts.
Live GPU rental market: 2,500+ offers across a dozen provider feeds. History, watches, limit orders.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceAI-powered crypto signal intelligence for 20 assets (BTC, ETH, SOL, etc). 6 scoring dimensions: whale activity, technical analysis, derivatives flow, narrative strength, sentiment, market structure. Market regime detection (TRENDING/RANGING), portfolio optimization, and accuracy tracking. 9 read-only MCP tools. Free via MCP, $0.001 USDC via x402 on Base for REST API.3MIT
- AlicenseAqualityBmaintenanceEnables AI assistants to access real-time on-chain crypto analytics, whale tracking, and market metrics through natural language queries. It provides access to over 245 endpoints for comprehensive data analysis of assets like Bitcoin, Ethereum, and stablecoins.773 npm8MIT
- AlicenseAqualityDmaintenancePay-per-call MCP server for on-chain blockchain data including wallet profiles, token metrics, protocol TVL, and gas prices.5MIT
- AlicenseAqualityCmaintenanceAuction house analytics, market intelligence, crafting optimization, inventory valuation, farming routes, guild analytics, and token tracking — all through the Model Context Protocol.10MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.