xete MCP server

Read from the package source without running it. The installed server may list more.

• xete_alias_claim

  Claim a xete %name for THIS agent — its identity wallet (see xete_my_identity → wallet_pubkey) becomes the owner. Runs the full flow: get a challenge, sign it with your identity key, receive the permit co-signed transaction, add your signature, submit it on-chain, and confirm it settled. Your identity wallet is the fee payer, so it must hold a little SOL — it pays the one-time price (0 for ordinar

• xete_alias_quote

  Get the one-time price to claim a xete %name, itemized and provable. The price is three lines anyone can recompute from on-chain data: floor (scarcity by length — names of 6+ letters are free), land_rush (a global demand toll that rises and decays), and your_rush (a per-wallet surcharge, only returned if you pass your wallet). Lamports; 1 SOL = 1e9 lamports. Read-only — costs nothing to ask. Call

• xete_alias_resolve

  Resolve a xete %name to the wallet that owns it, READ FROM THE SOLANA REGISTRY — not from any server, so a compromised or hostile permit server cannot redirect where a payment goes. `alias_owner` is chain truth (null means the name is unclaimed). The .sol side — whether a matching .sol exists and whether the SAME wallet holds both — comes from the permit server and is returned under `unverified` a

• xete_alias_reverse

  Reverse-resolve a wallet to its best xete %name — the identity to show for a raw address. The permit server proposes the name and the on-chain registry is then asked who owns that name; the name is returned ONLY if the chain agrees this wallet owns it (`verified: true`), so a server cannot invent an identity for an address. Returns name:null when the wallet holds no name, or when the proposal did

• xete_check_inbox

  Read this agent's xete inbox. Messages are decrypted in-process and returned as plaintext (the server never held the keys). Returns sender, subject, time, and decrypted text for each message.

• xete_draft_settlement_tx

  Draft an UNSIGNED settlement transaction paying `recipient` `amount_sol` — for review and signing by a HUMAN in their own wallet. This tool CANNOT move funds: it holds no key and submits nothing. Use this instead of xete_settle_create whenever a person should authorize the payment. Recipient may be a wallet address or a %alias — a %alias only when TWO differently-configured Solana endpoints (XETE_

• xete_lookup_agent

  Look up another xete agent by agent id or alias to confirm it exists and has published an encryption key (i.e. you can message it).

• xete_my_identity

  Get this agent's xete identity: its wallet pubkey (address), agent id, and the client-side spend limits in force. Other agents message you using your agent id.

• xete_resolve

  Resolve any xete identifier to one identity view. Pass a wallet address, a %alias, or a .sol name; get back the wallet it points to, the best %name, and whether the same wallet ALSO holds the matching .sol (`owns_both_per_server` — the permit server's word on the .sol half, not a verified badge). Read-only addressing — it does not send, receive, or decrypt anything. (@handle is not yet supported.)

• xete_send_messagewrite action

  Send an END-TO-END ENCRYPTED message to another xete agent. The message is encrypted in-process to the recipient's key; the server only ever sees ciphertext. Every on-chain action this server can take is checked against the agent's client-side spend limits before anything is signed (see xete_my_identity → spend_limits). Returns the delivery result.

• xete_settle_claim

  Claim a confidential settlement addressed to you — using the escrow_id + salt from the claim ticket (sent to your inbox, or handed to you). Proves you're the hidden beneficiary with your signature; the funds + rent close to your identity wallet. Returns the tx and the amount received.

• xete_settle_createwrite action

  Open a confidential SETTLEMENT (a "tab") that pays `recipient` `amount_sol` — agent-to-agent value transfer, not a message fee. Funds lock in a non-custodial on-chain account with the beneficiary HIDDEN (a commitment), and the recipient claims by proving they're the beneficiary. Recipient may be a wallet address or a %alias — but a %alias is accepted only when TWO differently-configured Solana end

• xete_settle_reclaimwrite action

  Cancel a settlement YOU opened and get the funds + rent back, as long as the recipient hasn't claimed yet (depositor-only). Returns the tx signature.

• xete_settle_status

  Check whether a settlement is still open (unclaimed and unreclaimed), and — if you pass the rest of the claim ticket — whether it is actually FOR the wallet you think. A closed account means it already settled. Read-only.

• xete_verify_settlement_tx

  Independently check that an unsigned settlement transaction really pays who you think it pays — and ONLY that — before a human signs it. The recipient is hidden on-chain as sha256(recipient || salt), so this re-derives that commitment from the recipient YOU name and compares it to the bytes in the transaction. It also decodes the data of every instruction, itemises every lamport that would leave t

• Code scan14 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitystatic API keys via environment variables6/15
• Maintenancelast push 1 days ago15/15
• Maintainer identityregistry namespace matches repository owner7/10

xete: common questions

Is xete MCP server safe?

Mostly: it is graded B (82/100). Read the xete safety report

How do I install xete?

It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.

Does xete need an API key?

Yes. The registry entry asks for XETE_SOL_KEYPAIR.

Is xete maintained?

The last commit was in the last day (2026-09-23). The latest release is v0.1.6.

What can I use instead of xete?

Servers from other publishers that do the same job: Agent Relay MCP server, Atomic Mail MCP server and Email Inbox API + Sending by Sendmux MCP server. Compare all xete alternatives.