hitz-vault
Registry code: c02eb382ef6f1bc1
Trade HITZ, the token of HITZ Protocol on Stellar mainnet, through its own exchange, the Sovereign Vault: protocol-owned pools against XLM and USDC, with no oracle. Flow: get_vault for prices and fees; quote to price a trade (pass account to check balances, trustlines and the Event Horizon); build_swap for an unsigned transaction from the user's own account; the user signs it in their Stellar wallet, or opens the sign.web link, a skyhitz.io page that signs with their wallet and submits; submit_transaction with a signed XDR; get_transaction to follow it. This server never sees or needs a…
- endpoint
- https://skyhitz.io/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is hitz-vault live?
- Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
- Is hitz-vault free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does hitz-vault have?
- 6 tools: get_account, submit_transaction, quote, get_transaction, build_swap, get_vault.
- Is hitz-vault safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 100%· all time 100%
last good check
of 6 tools
- unknown → live
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
get_vault open 2h ago
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).
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linesget_account unknown 2h ago
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.
{ "type": "object", "required": [ "address" ], "properties": { "address": { "type": "string", "pattern": "^G[A-Z2-7]{55}$", "description": "Stellar account address (G…)." } }, "additionalProperties": false }arguments 14 linessubmit_transaction unknown never probed
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.
{ "type": "object", "required": [ "xdr" ], "properties": { "xdr": { "type": "string", "description": "The signed transaction envelope, base64." } }, "additionalProperties": false }arguments 13 linesquote unknown never probed
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.
{ "type": "object", "required": [ "sell", "buy" ], "properties": { "buy": { "type": "string", "description": "HITZ, XLM, USDC (any case), or a token contract address (C…)." }, "sell": { "type": "string", "description": "HITZ, XLM, USDC (any case), or a token contract address (C…)." }, "amount": { "type": "string", "pattern": "^\\d+(\\.\\d+)?$", "description": "Amount of sell to trade, e.g. \"100\"." }, "account": { "type": "string", "pattern": "^G[A-Z2-7]{55}$", "description": "Optional: the account that would trade." }, "buy_amount": { "type": "string", "pattern": "^\\d+(\\.\\d+)?$", "description": "Instead of amount: how much of buy to receive." } }, "additionalProperties": false }arguments 33 linesget_transaction unknown never probed
Status of a transaction by hash, with a vault swap decoded (what was sold and bought).
{ "type": "object", "required": [ "hash" ], "properties": { "hash": { "type": "string", "pattern": "^[0-9a-fA-F]{64}$", "description": "Transaction hash." } }, "additionalProperties": false }arguments 14 linesbuild_swap unknown 2h ago
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.
{ "type": "object", "required": [ "account", "sell", "buy", "amount" ], "properties": { "to": { "type": "string", "description": "Optional recipient (G… or C…) instead of account." }, "buy": { "type": "string", "description": "HITZ, XLM, USDC (any case), or a token contract address (C…)." }, "sell": { "type": "string", "description": "HITZ, XLM, USDC (any case), or a token contract address (C…)." }, "amount": { "type": "string", "pattern": "^\\d+(\\.\\d+)?$", "description": "Exact amount of sell to trade." }, "account": { "type": "string", "pattern": "^G[A-Z2-7]{55}$", "description": "The user's account: it pays, signs and (unless to is set) receives." }, "valid_for": { "type": "integer", "default": 300, "maximum": 3600, "minimum": 30, "description": "Seconds the transaction stays valid." }, "slippage_bps": { "type": "integer", "default": 100, "maximum": 1000, "minimum": 0, "description": "How far below the quote the output may land, in basis points (100 = 1%)." } }, "additionalProperties": false }arguments 48 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idc02eb382ef6f1bc1.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/c02eb382ef6f1bc1/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/c02eb382ef6f1bc1?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.