xete
End-to-end-encrypted, sovereign inbox for AI agents. The server only ever sees ciphertext.
The current version, v0.1.6, was published to the official MCP registry on 2026-08-02. It is distributed as xete-mcp on PyPI, filed under Other by this index, and declares 11 environment variables. Removals and unreachable sources are measured across every server this index tracks, contract drift across the servers that answer in consecutive snapshots; the index's current counts put this record in context.
Using xete in Claude, Cursor, Gemini CLI, Cline, or Zed?
MCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and HOLDs the call when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself (use Install this server for that).
Rewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less
uv tool install mcpindex-gate && mcpindex-config-wireSemantic screen found no manipulation pattern in the description. Conformance probe not yet run.
mcpindex.integrity.descriptionpassINFOevidence“No malicious instructions found”via static_description
- - Semantic screen only - the deterministic conformance probe has not run on this server
- - Confidence is reported but not yet calibrated (v1)
- - Screen reads the tool description, not the live behavior
- - advisory
- - registry description only no input schema
- - screen model 8b
- - Still current: the description we screened is unchanged, re-checked against the registry
- - The registry listing (version, packages, links) changed after this screen ran - the description we assessed did not
Semantic screen: an LLM judge reads the tool description for hidden instructions (status PARTIAL). A pass means the description is not lying, not that the tool is safe: a high-capability tool with an honest description still warrants caution. The deterministic conformance probe has not been run on this server yet, so the screen here is semantic-only. Posture: advisory. Confidences are reported but not yet calibrated (calibrated=false at v1). Full verdict history is not shown on this page.
Own this server? Screen its description →
That verdict was true at screening time (snapshot 2026-08-30).
Contracts can change after screening, with no version bump. The gate pins xete’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday.
See your first HOLD in 2 minutes →
Related: how to trust an MCP server · screen before install · silent contract drift
People vet a server before wiring it in. One line on your project site or docs answers that with an independent record: screening verdict, registry provenance, contract drift history. It stays current as new screens and drift events land.
[Independent trust record for xete](https://mcpindex.ai/server/io-github-xetenet-xete-mcp) - screening verdict, registry provenance, and contract drift monitoring.<a href="https://mcpindex.ai/server/io-github-xetenet-xete-mcp">Independent trust record for xete</a> - screening verdict, registry provenance, and contract drift monitoring.A live verdict badge for your README or listing. It reflects the current screen, links back here, and updates when the verdict does.
[](https://mcpindex.ai/server/io-github-xetenet-xete-mcp)<a href="https://mcpindex.ai/server/io-github-xetenet-xete-mcp"><img src="https://mcpindex.ai/api/v1/badge/io-github-xetenet-xete-mcp" alt="mcpindex verdict" height="20" /></a>XETE_SERVER_URLxete server base URL. Defaults to https://xete.net.
XETE_RPC_URLSolana 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_KEYPAIROptional 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 registry over XETE_SOLANA_RPC.
XETE_SOLANA_RPCSolana 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_LAMPORTSClient-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_LAMPORTSClient-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_SECONDSLength 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_LAMPORTSMinimum 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.
Buy travel eSIMs, gift cards and mobile top-ups with crypto — user confirms before any order.
Give your AI agent a spending limit: approval controls and single-use virtual cards.
Ruthless prioritization: cuts a list to the 1-3 items that actually serve your goal.