HITZ Sovereign Vault MCP server
io.github.skyhitz/hitz-vaultskyhitzstreamable-httpv1.0.0Scanned
Quote and build HITZ, XLM and USDC swaps on Stellar's Sovereign Vault. Never holds a key.
6 tools: 1 can delete or cancel things, 1 do something that can't be undone, 1 change things and 3 only read.
- Reads private data · 2
- Reads text others write · 6
- Can send data out · 1
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here can delete or cancel things and 1 does something that can't be undone. 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 HITZ Sovereign Vault MCP server can do
The HITZ Sovereign Vault MCP server is published by the GitHub account skyhitz. It has 6 tools. It can delete or cancel things (1 tool: submit_transaction), do things that cannot be undone, such as sending, paying or publishing (build_swap) and create or change data (1 tool: quote). 3 tools only read.
2 tools read private data (get_vault and get_transaction); 6 tools bring in text other people can write (get_vault, get_account, quote and 3 more); 1 tool can send data out of your system (build_swap). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 16, 2026, version 1.0.0.
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
Deletes or cancels 1Claude Code: deny
submit_transactionSubmit a signed vault transaction (from build_swap, signed by the user) to Stellar mainnet and wait for the result: status, hash, explorer link and the amount bought.Reads text others writeNo findings
Why it is in this group
- The name "submit_transaction" says "submit": a word for a change.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Submit a signed vault transaction (from build_swap, signed by the user) to Stellar mainnet and wait for the result: status, hash, explorer link and the amount bought. Only relays calls to the vault.
Annotations the server declares
- title: Submit a signed transaction
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: true
Can't be undone 1Claude Code: ask
build_swapBuild an unsigned, simulated swap transaction for the user's own Stellar account, ready to sign.Reads text others writeCan send data out1 finding
Why it is in this group
- The input addresses people (input.to): what it sends cannot be taken back.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a destination (input.to): what the tool writes goes there.
Findings
- Warn
The server marks "build_swap" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"openWorldHint":true}; The input addresses people (input.to): what it sends cannot be taken back.
Description, as the server wrote it Build an unsigned, simulated swap transaction for the user's own Stellar account, ready to sign. Returns the XDR, the expected and minimum amounts, the network fee, warnings, and sign links: sign.web opens a skyhitz.io page where the user signs with their own wallet and the swap is submitted; sign.sep7 is a SEP-7 link for wallets that support it. Nothing moves until the user signs. Show the user the amounts and warnings first.
Annotations the server declares
- title: Build a swap transaction
- readOnlyHint: true
- openWorldHint: true
Changes things 1Claude Code: ask
quoteExact quote from the contract's own math: the amount out, price, fees per hop and price impact.Reads text others writeNo 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.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Exact quote from the contract's own math: the amount out, price, fees per hop and price impact. Give amount (what is sold) or buy_amount (what should come out; the quote finds the input). Pass account to check its balances, trustlines and whether the trade would push it over the Event Horizon.
Annotations the server declares
- title: Quote a trade
- readOnlyHint: true
- openWorldHint: true
Only reads 3Show 3 read-only tools
get_accountA Stellar account's XLM, USDC and HITZ balances, its trustlines, whether it is vaulted, and how much HITZ it can buy before being vaulted.Reads text others writeNo findings
Why it is in this group
- The name "get_account" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it A Stellar account's XLM, USDC and HITZ balances, its trustlines, whether it is vaulted, and how much HITZ it can buy before being vaulted.
Annotations the server declares
- title: Account
- readOnlyHint: true
- openWorldHint: true
get_transactionStatus of a transaction by hash, with a vault swap decoded (what was sold and bought).Reads private dataReads text others writeNo findings
Why it is in this group
- The name "get_transaction" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "status" and "vault": it reads secrets.
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Status of a transaction by hash, with a vault swap decoded (what was sold and bought).
Annotations the server declares
- title: Transaction status
- readOnlyHint: true
- openWorldHint: true
get_vaultLive state of the HITZ Sovereign Vault: each pool's reserves, HITZ price, current fee and dislocation, USD values, and the HITZ Event Horizon (the most HITZ an account can hold and…Reads private dataReads text others writeNo findings
Why it is in this group
- The name "get_vault" says "get": a word for reading.
What it can reach
- private-dataThe name "get_vault" says "get" and "vault": it reads secrets.
- private-dataThe description's first sentence says "vault": it reads secrets.
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Live state of the HITZ Sovereign Vault: each pool's reserves, HITZ price, current fee and dislocation, USD values, and the HITZ Event Horizon (the most HITZ an account can hold and still send it anywhere).
Annotations the server declares
- title: Vault state
- readOnlyHint: true
- openWorldHint: true
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.
12 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.
- Reads private data2
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write6
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__hitz-vault__build_swap"
]
}
}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 17, 2026, 15:20 UTC, unchanged since Nov 17, 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
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 3 tools that change things (1 destructive, 1 irreversible, 1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://skyhitz.io/mcp: tools/list returned 6 tools to an anonymous client, including submit_transaction (destructive), build_swap (irreversible), quote (write)
Findings
Matches of fixed checks, with the text they matched.
- Warnbuild_swap
The server marks "build_swap" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"openWorldHint":true}; The input addresses people (input.to): what it sends cannot be taken back.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http hitz-vault https://skyhitz.io/mcpclaude mcp add --transport http hitz-vault https://skyhitz.io/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__hitz-vault__get_vault",
"mcp__hitz-vault__get_account",
"mcp__hitz-vault__get_transaction"
],
"ask": [
"mcp__hitz-vault__quote",
"mcp__hitz-vault__build_swap"
],
"deny": [
"mcp__hitz-vault__submit_transaction"
]
}
}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 hitz-vault. Review it before you use it.
Capability tags behind 6 rules
- mcp__hitz-vault__get_vault private-data, untrusted-input
- mcp__hitz-vault__get_account untrusted-input
- mcp__hitz-vault__quote untrusted-input
- mcp__hitz-vault__build_swap untrusted-input, outbound
- mcp__hitz-vault__submit_transaction untrusted-input
- mcp__hitz-vault__get_transaction private-data, untrusted-input
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.skyhitz/hitz-vault/verify?hash=7741a93b59e4249aa304d7b28f5caaa77108ebcc045da317a433833c7c1de247" | jq -e '.changed == false'Pinned hash 7741a93b59e4, from Nov 16, 2026, 22:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.skyhitz/hitz-vault/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.skyhitz/hitz-vault)Source: MCP Registry · repository. Synced Nov 16, 2026, 22:17 UTC.
HITZ Sovereign Vault MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the HITZ Sovereign Vault MCP server safe?
- No scan can promise that. What its definitions show: 6 tools, 3 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the HITZ Sovereign Vault MCP server delete data?
- Yes. 1 tool can delete, cancel or revoke something: submit_transaction.
Can the HITZ Sovereign Vault MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: build_swap.
What tools does the HITZ Sovereign Vault MCP server have?
- 6 tools: 1 destructive, 1 irreversible, 1 write, 3 read. submit_transaction, build_swap, quote, get_vault, get_account and get_transaction.
Does the HITZ Sovereign Vault MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the HITZ Sovereign Vault MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): build_swap.
Has the HITZ Sovereign Vault MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 16, 2026.