Galactic MCP server
io.github.masonicGIT/galacticmasonicGITstreamable-httpv0.1.1Scanned
On-chain asset, market, and GPU price data for galactic.inc.
6 tools: 3 change things and 3 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
3 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Galactic MCP server can do
The Galactic MCP server is published by the GitHub account masonicGIT. It has 6 tools. It can create or change data (3 tools: compute_vaults, gpu_price_index and market_totals), but cannot delete data. 3 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 8, 2026, version 0.1.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
6 tools
Changes things 3Claude Code: ask
compute_vaultsOn-chain figures for the USD.AI and GAIB compute vaults.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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]}.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
gpu_price_indexLatest GPU rental price index families, in US dollars per GPU-hour.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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]}.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
market_totalsCategory and chain totals for the published asset universe.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
Only reads 3Show 3 read-only tools
get_assetOne published asset, with per-chain supply and an optional daily price history.No findings
Why it is in this group
- The name "get_asset" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
list_assetsList published tokenized assets.No findings
Why it is in this group
- The name "list_assets" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
search_newsSearch approved galactic.inc newsroom items.No findings
Why it is in this group
- The name "search_news" says "search": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:07 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 3
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.galactic.inc/mcp: tools/list returned 6 tools to an anonymous client, including compute_vaults (write), gpu_price_index (write), market_totals (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools2 changed.~2 changedView diff
- Changed:gpu_price_indexChanges thingsdescriptioninputSchema
- Changed:market_totalsChanges thingsdescription
Install
Pinned to version 0.1.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http galactic https://mcp.galactic.inc/mcpclaude mcp add --transport http galactic https://mcp.galactic.inc/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__galactic__get_asset",
"mcp__galactic__list_assets",
"mcp__galactic__search_news"
],
"ask": [
"mcp__galactic__compute_vaults",
"mcp__galactic__gpu_price_index",
"mcp__galactic__market_totals"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as galactic. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.masonicGIT/galactic/verify?hash=cc855716aec73239194d5f91036222da1767da80af6a26c8ff2b60e305fc5c29" | jq -e '.changed == false'Pinned hash cc855716aec7, from Nov 8, 2026, 12:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.masonicGIT/galactic/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.masonicGIT/galactic)Source: MCP Registry · repository. Synced Oct 22, 2026, 06:19 UTC.
Galactic MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Galactic MCP server safe?
- No scan can promise that. What its definitions show: 6 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Galactic MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Galactic MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Galactic MCP server have?
- 6 tools: 3 write, 3 read. compute_vaults, gpu_price_index, market_totals, get_asset, list_assets and search_news.
Does the Galactic MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Galactic MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Galactic MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 8, 2026. Every change is on this page and in its Atom feed.