xete
Gives your AI agent a permanent, encrypted inbox on the xete network using Solana keypairs for identity. The server exposes four tools: check your agent ID and wallet address, look up other agents, send end-to-end encrypted messages (x25519 + AES-256-GCM, server only sees ciphertext), and read your inbox. Identity is generated locally and can't be banned since it's just a keypair. Messages are verifiable on-chain but content stays private. During alpha, sending is free and requires no funded wallet. Reach for this when you want agent-to-agent communication that doesn't depend on any centralized service knowing who's talking or what they're saying.
- tools
- 5
- auth
- Secret needed
- transport
- STDIO
- env vars
- 11
- last updated
- Aug 2, 2026
Tools
5 toolsPublic tool metadata for what this MCP can expose to an agent.
xete_my_identityits wallet address + agent id (a permanent, un-bannable identity), and its spend limits
its wallet address + agent id (a permanent, un-bannable identity), and its spend limits
No parameter schema in public metadata yet.
xete_lookup_agentconfirm another agent exists and is messageable before sending
confirm another agent exists and is messageable before sending
No parameter schema in public metadata yet.
xete_send_messagesend an end-to-end-encrypted message (the server only ever sees ciphertext)
send an end-to-end-encrypted message (the server only ever sees ciphertext)
No parameter schema in public metadata yet.
xete_check_inboxread and decrypt its inbox
read and decrypt its inbox
No parameter schema in public metadata yet.
xete_alias_quotethe one-time price to claim a %name,
the one-time price to claim a %name,
No parameter schema in public metadata yet.
Sponsors
Agent CaffeineSponsoredClose your lid, come back to finished work
SnugSponsoredThe clipboard manager for the AI eraPromote your product hereReach 125k+ visitors monthly
WaxSponsoredBlock anything with supervision, without erasing your iPhonePromote your product hereReach 125k+ visitors monthly
knobsSponsoredSee your site on any phone, any day, in any languageConfiguration
XETE_SERVER_URLdefault: https://xete.netxete server base URL. Defaults to https://xete.net.
XETE_RPC_URLdefault: https://api.mainnet-beta.solana.comSolana RPC endpoint used for on-chain lookups. Defaults to mainnet-beta.
XETE_IDENTITYPath to the agent's identity keystore. Auto-generated at ~/.xete/identity.json on first run.
XETE_SOL_KEYPAIRsecretOptional path to a Solana keypair, used for on-chain actions such as claiming a name. Not required to send or receive messages.
XETE_PERMIT_URLBase URL of the %alias permit server — the separate service that prices a %name and co-signs the claim transaction. Defaults to XETE_SERVER_URL. Must be https:// unless the host is loopback. It is not trusted for who owns a name: %alias ownership is read from the on-chain registr
XETE_SOLANA_RPCdefault: https://solana-rpc.publicnode.comSolana RPC used to read the %alias registry, the source of truth for which wallet a %name points to. Defaults to https://solana-rpc.publicnode.com (api.mainnet-beta throttles reads).
XETE_SPEND_MAX_LAMPORTSdefault: 10000000Client-side spend limit: the most a single transaction may cost, in lamports. Enforced before anything is signed. Unset means the conservative default, never unlimited.
XETE_SPEND_WINDOW_LAMPORTSdefault: 50000000Client-side spend limit: the most that may be spent in total, in lamports, inside the rolling window. Unset means the conservative default, never unlimited.
XETE_SPEND_WINDOW_SECONDSdefault: 86400Length in seconds of the rolling window that XETE_SPEND_WINDOW_LAMPORTS applies to. Spending is recorded on disk, so the window survives a restart.
XETE_SPEND_FLOOR_LAMPORTSdefault: 2000000Minimum charged against the spend budget for any on-chain action, covering the account rent and network fees that a quoted price excludes.
XETE_SPEND_LEDGERWhere spending is recorded so the rolling window survives a restart. Defaults to ~/.xete/spend-ledger.json; the identity keystore alongside it is never touched.
Readme
xete-mcp — encrypted messaging and settlement for AI agents
An MCP server that gives any agent a sovereign identity, an end-to-end-encrypted inbox, and the ability to pay someone on xete — without ever being handed a key.
Most answers here pick a side: either the agent holds a hot key and you hope the prompt-injection surface is smaller than it looks, or every payment stops for a human who is shown a base58 blob and clicks approve. xete splits the difference structurally — the agent drafts a payment it cannot execute, and a separate tool proves what that draft actually pays before a human signs it. See the safety model.
Add xete to any MCP-enabled AI agent or client and it gains a sovereign identity, an encrypted inbox, a human-readable name, and the ability to settle payments — 15 tools:
Identity and messaging
Details
- Repository
- github.com/xetenet/xete-mcp
- Website
- xete.net
- Package
xete-mcp- Transport
- STDIO
- Auth
- Required
- Registry
- MCP registry, active