Xete MCP Server

Xete is an MCP integration. End-to-end-encrypted, sovereign inbox for AI agents. The server only ever sees ciphertext.

Packages and local setup

The published pypi package is xete-mcp, version 0.1.6. Its declared MCP transport is stdio.

The package declares XETE_SERVER_URL: xete server base URL. Defaults to https://xete.net.; XETE_RPC_URL: Solana RPC endpoint used for on-chain lookups. Defaults to mainnet-beta.; XETE_IDENTITY: Path to the agent's identity keystore. Auto-generated at ~/.xete/identity.json on first run.; XETE_SOL_KEYPAIR: Optional path to a Solana keypair, used for on-chain actions such as claiming a name. Not required to send or receive messages.; XETE_PERMIT_URL: Base 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 registry over XETE_SOLANA_RPC.; XETE_SOLANA_RPC: Solana 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_LAMPORTS: Client-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_LAMPORTS: Client-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_SECONDS: Length 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_LAMPORTS: Minimum charged against the spend budget for any on-chain action, covering the account rent and network fees that a quoted price excludes.; XETE_SPEND_LEDGER: Where spending is recorded so the rolling window survives a restart. Defaults to ~/.xete/spend-ledger.json; the identity keystore alongside it is never touched..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 0.1.6 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related other integrations MCP servers for tools that cover the same kind of work.