Galactic
REMOTE · MCP.GALACTIC.INC
On-chain asset, market, and GPU price data for galactic.inc.
Available components
Last scanned (19 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1924 tokens (~192/item across 10 items; 6 tools + 4 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Nov 26 0
- Server version: 0.1.3 → 0.2.0 functional
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 13 Nov 26 71
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://mcp.galactic.inc/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=galactic.inc | CN=WE1,O=Google Trust Services,C=US | 22 Oct 2026 | 20 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 98a40f5920fed3bf13011ab8dad9b52e |
| SANs: galactic.inc, mcp.galactic.inc, *.mcp.galactic.inc | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.galactic.inc. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| inc. | DS published | 13114, 18077 | 8, 8 | Verified |
| galactic.inc. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.galactic.inc/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.galactic.inc/mcp | HTTPS enforced | 301 | https://mcp.galactic.inc/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
compute_vaults ~218
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]}.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | – | Vault id, usdai or gaib. Empty returns both. |
| response_format | string | – | markdown (default) is a compact reading form. json is the object described below, with source numbers and omitted fields left out. |
No output schema declared.
No examples provided.
get_asset ~271
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.
| Name | Type | Req | Description |
|---|---|---|---|
| history_days | integer | – | Daily published prices to include, from 0 to 30. 0 omits history. History is included only when the price itself is published. |
| id | string | yes | Asset id (slug), registry ticker, or display ticker. A shared display ticker returns an ambiguous error and the matching ids. |
| response_format | string | – | markdown (default) is a compact reading form. json is the object described below, with source numbers and omitted fields left out. |
No output schema declared.
No examples provided.
gpu_price_index ~264
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.<GPU>.<SEGMENT>.<CLASS>. 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]}.
| Name | Type | Req | Description |
|---|---|---|---|
| model | string | – | GPU model name as published, for example H100 SXM. Empty returns every model. |
| response_format | string | – | markdown (default) is a compact reading form. json is the object described below, with source numbers and omitted fields left out. |
No output schema declared.
No examples provided.
list_assets ~470
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Category slug or English label, such as gold or Treasuries. Empty means every category. Slugs: gold, treasuries, money-market, private-credit, stocks, commodities, funds, real-estate, deposit-token. |
| chain | string | – | Chain id (ethereum, solana, robinhood, liquid, zksync, and the other published chain ids) or the chain display name. Empty means every chain. |
| include_upcoming | boolean | – | When true, announced listings with no on-chain figures are included after the live page. |
| issuer | string | – | Case-insensitive substring of the published issuer name. |
| limit | integer | – | Page size from 1 to 200. |
| offset | integer | – | Matches to skip. |
| query | string | – | Case-insensitive substring of ticker, display ticker, name, issuer, or id. Empty lists the universe. |
| response_format | string | – | markdown (default) is a compact reading form. json is the object described below, with source numbers and omitted fields left out. |
No output schema declared.
No examples provided.
market_totals ~353
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.
| Name | Type | Req | Description |
|---|---|---|---|
| response_format | string | – | markdown (default) is a compact reading form. json is the object described below, with source numbers and omitted fields left out. |
No output schema declared.
No examples provided.
search_news ~170
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum items to return, from 1 to 30. |
| query | string | – | Case-insensitive substring of headline, lede, category, or asset ticker. Empty returns the latest approved items. |
| response_format | string | – | markdown (default) is a compact reading form. json is the object described below, with source numbers and omitted fields left out. |
No output schema declared.
No examples provided.
How do I install the Galactic MCP server?
Galactic is a hosted endpoint at https://mcp.galactic.inc/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.galactic.inc
claude mcp add --transport http inc-galactic-galactic 'https://mcp.galactic.inc/mcp'
What is the Galactic MCP server?
Galactic is an MCP server listed in the public MCP registry as inc.galactic/galactic. On-chain asset, market, and GPU price data for galactic.inc. This page covers its hosted endpoint (https://mcp.galactic.inc/mcp).
Is the Galactic MCP server safe to use?
Galactic scores 75 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Galactic MCP server expose?
Galactic exposes 6 tools: compute_vaults, get_asset, gpu_price_index, list_assets, market_totals, search_news. Their descriptions and schemas cost roughly 1,746 tokens of context every time the server is loaded.
Does the Galactic MCP server require authentication?
No. We connected to Galactic without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Galactic MCP server still maintained?
Galactic is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Galactic MCP server?
VerifyMCP ran 13 checks on Galactic, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.