Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words

xete

by xetenetversion 0.1.6i★ 0iRuns on your computerOfficial site ↗
Registry nameio.github.xetenet/xete-mcp

How to install

What it does

End-to-end-encrypted, sovereign inbox for AI agents. The server only ever sees ciphertext.

  • Connects Runs on your computer
  • Account or key No key needed
  • Category Chat & email

Why it ranks here

Lists are ordered by a usage score (out of 100) built from these parts

Popularity0/80GitHub stars or weekly downloads: the larger counts 60, the smaller 20
Freshness7/12Full marks for a release or code change within 30 days
Still answering0/8The cloud endpoint answered at the last check
Usage score7/100

Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)

Install

Pick the AI app you use, then copy the settings.

Let your AI install it with one sentence

Please install xete. Follow https://mcp.popnx.com/i/xetenet-xete-mcp.md, show me the commands and wait for my OK before running them.

Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads

Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 14, 2026

First: which AI do you use?

Pick your app and the steps appear below.

Works with Claude, with some setup first

Install Python (uv) on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone

Let AI install it

Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server xete for Claude on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "xete": { "command": "uvx", "args": [ "xete-mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the xete tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install uv (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    uv --version
    • A version number such as uv … = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required

    Open the uv download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version

    Install once; it works for everything that needs uv

  2. Open the Claude desktop app’s settings file

    SettingsDeveloperEdit Config

  3. Paste these settings and save the file

    {
      "mcpServers": {
        "xete": {
          "command": "uvx",
          "args": [
            "xete-mcp"
          ]
        }
      }
    }
  4. Quit Claude and open it again

  5. Try it

    Use xete and tell me what you can do for me, then show me one thing

    ✓ If Claude says it is using xete or shows a xete tool in the answer, you are connected

11 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • XETE_SERVER_URL xete server base URL. Defaults to https://xete.net. · default https://xete.net
  • XETE_RPC_URL Solana RPC endpoint used for on-chain lookups. Defaults to mainnet-beta. · default https://api.mainnet-beta.solana.com
  • 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 no…
  • 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). · default https://solana-rpc.publicnode.com
  • 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. · default 10000000
  • 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. · default 50000000
  • 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. · default 86400
  • 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. · default 2000000
  • 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.

Descriptions are as written by the maker.

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

ChatGPT cannot connect xete yet

xete runs on your computer, but ChatGPT can only connect servers that run on the web

What you can do instead

A · Use an app that can connect xete

  • Install Python (uv) on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
  • Install Python (uv) on your computer first (one time)
  • Install Python (uv) on your computer first (one time)
  • Install Python (uv) on your computer first (one time)

B · Others in Chat & email that work with ChatGPT

Picked from the most used in the same category, only ones that connect by address with no key

Works with Claude Code, with some setup first

Install Python (uv) on your computer first (one time)

Let AI install it

Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server xete for Claude Code on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user xete -- uvx xete-mcp 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the xete tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install uv (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    uv --version
    • A version number such as uv … = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required

    Open the uv download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version

    Install once; it works for everything that needs uv

  2. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: open PowerShell

  3. Paste this command and press Enter

    claude mcp add --scope user xete -- uvx xete-mcp
  4. Type /mcp in Claude Code

    You should see xete listed as connected

  5. Try it

    Use xete and tell me what you can do for me, then show me one thing

    ✓ If Claude Code says it is using xete or shows a xete tool in the answer, you are connected

11 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • XETE_SERVER_URL xete server base URL. Defaults to https://xete.net. · default https://xete.net
  • XETE_RPC_URL Solana RPC endpoint used for on-chain lookups. Defaults to mainnet-beta. · default https://api.mainnet-beta.solana.com
  • 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 no…
  • 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). · default https://solana-rpc.publicnode.com
  • 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. · default 10000000
  • 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. · default 50000000
  • 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. · default 86400
  • 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. · default 2000000
  • 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.

Descriptions are as written by the maker.

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with Cursor, with some setup first

Install Python (uv) on your computer first (one time)

Let AI install it

Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server xete for Cursor on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "xete": { "command": "uvx", "args": [ "xete-mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the xete tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install uv (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    uv --version
    • A version number such as uv … = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required

    Open the uv download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version

    Install once; it works for everything that needs uv

  2. Click this button to open Cursor

    Open in Cursor

    Cursor asks you to confirm; click Install

  3. Open the AI chat in Cursor in Agent mode

  4. Try it

    Use xete and tell me what you can do for me, then show me one thing

    ✓ If Cursor says it is using xete or shows a xete tool in the answer, you are connected

11 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • XETE_SERVER_URL xete server base URL. Defaults to https://xete.net. · default https://xete.net
  • XETE_RPC_URL Solana RPC endpoint used for on-chain lookups. Defaults to mainnet-beta. · default https://api.mainnet-beta.solana.com
  • 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 no…
  • 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). · default https://solana-rpc.publicnode.com
  • 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. · default 10000000
  • 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. · default 50000000
  • 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. · default 86400
  • 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. · default 2000000
  • 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.

Descriptions are as written by the maker.

Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with VS Code, with some setup first

Install Python (uv) on your computer first (one time)

Let AI install it

Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server xete for VS Code on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "xete": { "type": "stdio", "command": "uvx", "args": [ "xete-mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the xete tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install uv (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    uv --version
    • A version number such as uv … = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required

    Open the uv download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version

    Install once; it works for everything that needs uv

  2. Click this button to open VS Code

    Open in VS Code

    VS Code asks you to confirm; click Install

  3. Open the AI chat in VS Code in Agent mode

  4. Try it

    Use xete and tell me what you can do for me, then show me one thing

    ✓ If VS Code says it is using xete or shows a xete tool in the answer, you are connected

11 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • XETE_SERVER_URL xete server base URL. Defaults to https://xete.net. · default https://xete.net
  • XETE_RPC_URL Solana RPC endpoint used for on-chain lookups. Defaults to mainnet-beta. · default https://api.mainnet-beta.solana.com
  • 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 no…
  • 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). · default https://solana-rpc.publicnode.com
  • 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. · default 10000000
  • 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. · default 50000000
  • 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. · default 86400
  • 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. · default 2000000
  • 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.

Descriptions are as written by the maker.

Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.

See every app that uses MCP →

JSON settings are under “For developers” below

Stuck? Ask people who use xete💬 Discussion →
For developers: Terminal commands and JSON settings

Installed on your computer

Claude Code

claude mcp add --scope user xete -- uvx xete-mcp

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "xete": {
      "command": "uvx",
      "args": [
        "xete-mcp"
      ]
    }
  }
}

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "xete": {
      "command": "uvx",
      "args": [
        "xete-mcp"
      ]
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "xete": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "xete-mcp"
      ]
    }
  }
}

Values you fill in

  • XETE_SERVER_URL env
    xete server base URL. Defaults to https://xete.net.
  • XETE_RPC_URL env
    Solana RPC endpoint used for on-chain lookups. Defaults to mainnet-beta.
  • XETE_IDENTITY env
    Path to the agent's identity keystore. Auto-generated at ~/.xete/identity.json on first run.
  • XETE_SOL_KEYPAIR secret env
    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 env
    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 no…
  • XETE_SOLANA_RPC env
    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 env
    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 env
    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 env
    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 env
    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 env
    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.

Descriptions are as written by the maker.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

At a glance

Downloads per weeki
28/wk
Connection
Runs on your computer
Latest versioni
0.1.6
Published to registryi
Aug 2, 2026
Code last changedi
Sep 23, 2026
Maker
xetenet
Packages
pypi: xete-mcp
Website
xete.net
Registry status
Active

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Run on your computer in

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

All apps, with pros and cons →

Related guides

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account xetenet, which owns the repo

  • ✓ Pass

    Still maintained

    Code last changed 2 months ago

  • ✓ Pass

    Has a licence

    Uses MIT

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Published vulnerabilities (OSV.dev)

No entries on OSV.dev for xete-mcp@0.1.6

Checks only this package version, not every dependency · checked Nov 16, 2026

What we check → · JSON

Makers: ask for a re-check or report wrong info
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/xetenet-xete-mcp.svg)](https://mcp.popnx.com/en/servers/xetenet-xete-mcp)

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in to post

User reviews

No reviews yet

Sign in to write a review

Compared with others in Chat & emaili

  • More stars than 0% of the other 2024 servers in this category
  • Published to the registry more recently than 17% of the other 2024 servers in this category
  • Basic checks equal to or better than 99% of the other 2024 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is xete safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed 2 months ago, and the latest version (0.1.6) reached the registry 4 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.

What can I use instead?

In the same category: emailmd, Kite Discord Bot Builder, e2a — email for AI agents, Infobip MCP, kernelCAD

Similar alternatives

Same category, other makers, commands already checked. Official ones first, then by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

emailmd

Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.

by anypostWidely used↓ 5.4K/wk★ 1.4KUpdated 5 days ago

Computer or cloud✓ service owner · emailmd.dev

Infobip MCP

Infobip MCP server for omnichannel communication and messaging. SMS, RCS, WhatsApp, Viber and more.

by infobipEarly★ 36Updated 13 months ago

Runs in the cloud✓ service owner · infobip.com

kernelCAD

CAD in ChatGPT and Claude: editable parts, STEP/STL/drawings, in-chat 3D, automatic checks.

by w1neEarly★ 35Updated 23 days ago

Runs in the cloud✓ service owner · kernelcad.com
Compared with similar ones
This one
xete
emailmdKite Discord Bot Buildere2a — email for AI agentsInfobip MCPkernelCAD
Runs whereInstalls on your computerCloud or install on your computerRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to install
Needs a keyNoNoNoNoNoNo
Add with + in ClaudeNoNoNoNoYesNo
Basic checks3/35/54/44/44/44/4
LicenseMITMITAGPL-3.0Apache-2.0MITMIT
PriceNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registry

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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](https://xete.net) — 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

  • `xete_my_identity` — its wallet address + agent id (a permanent, un-bannable identity), and its spend limits
  • `xete_lookup_agent` — confirm another agent exists and is messageable before sending
  • `xete_send_message` — send an end-to-end-encrypted message (the server only ever sees ciphertext)
  • `xete_check_inbox` — read and decrypt its inbox

`%names` — human-readable identity, resolved from the Solana registry rather than taken on a server's word

  • `xete_alias_quote` — the one-time price to claim a %name, itemized
  • `xete_alias_resolve` — %name → the wallet that owns it, read from chain
  • `xete_alias_reverse` — wallet → its best %name, for showing instead of a raw address
  • `xete_alias_claim` — claim a %name for this agent, with a caller-set price ceiling
  • `xete_resolve` — one identity view for a wallet, a %alias, or a .sol domain

Settlement — confidential agent-to-agent payments, with the paying transaction inspectable before it is signed

  • `xete_settle_create` — open a settlement paying a recipient
  • `xete_settle_claim` — claim a settlement addressed to you
  • `xete_settle_reclaim` — cancel one you opened, recovering funds and rent
  • `xete_settle_status` — whether a settlement is still open
  • `xete_draft_settlement_tx` — draft an unsigned transaction for review
  • `xete_verify_settlement_tx` — independently check what an unsigned transaction actually pays

Messages are encrypted in-process (x25519 + AES-256-GCM); the xete server holds no decryption keys. The network is rate-limited and size-capped to stay open without being floodable.

Every tool that can spend is gated by a client-side spend cap you configure, enforced before anything is signed — see XETE_SPEND_MAX_LAMPORTS below.

The safety model — draft, verify, then sign

Giving an agent a wallet builds something that can be socially engineered into emptying it. Not giving it one means it can't do the thing you wanted. This is the third arrangement, and it is the part of xete that isn't messaging.

The agent drafts; it cannot execute. xete_draft_settlement_tx returns a base64 unsigned transaction. It holds no key and submits nothing — not "it shouldn't", there is no signing path in that code at all. A human signs it, in their own wallet.

A separate tool checks the draft. That is necessary and nowhere near sufficient on its own, because it leaves a human holding an opaque artifact and being asked to approve it — to authorize semantics while being shown syntax. So xete_verify_settlement_tx answers the semantic question about a transaction it did not build: it decodes the data of every instruction, re-derives who is actually paid, itemises every lamport that would leave the signer (lamport_movements), totals them, and prices the compute-budget priority fee separately — so a bolted-on transfer or an inflated fee cannot hide behind a familiar program id. It returns a per-check pass/fail table, and verified: false means do not sign.

The verifier is deliberately not the drafter. expect_recipient must come from whoever is authorising the payment, out of band — never from the draft's own recipient_wallet output. Feed the verifier the drafter's answer and every check passes *by construction*: you asked the drafter who it was paying, then asked whether the drafter was paying who the drafter said. That is a tautology wearing the costume of a check.

Two endpoints, or no name. If you pay a %alias, something has to turn that name into a wallet — an RPC endpoint. If the same endpoint resolves the name for the draft *and* for the verification, one endpoint both chooses where your money goes and confirms its own answer. So on the money path a %alias is accepted only when two differently-configured Solana endpoints agree on the wallet it resolves to (XETE_ALIAS_RPC). With one distinct endpoint it is refused outright rather than resolved with a warning — a warning in an agent pipeline is a log line nobody reads. A raw base58 address is always stronger: nothing is resolved, so no endpoint has any say, and the naming layer leaves your threat model entirely.

Your counterparty is committed, not broadcast. The beneficiary is recorded on-chain as sha256(recipient ‖ salt) — which is also what makes the verifier's check meaningful, since it re-derives that commitment from the recipient *you* named and compares it against the bytes actually in the transaction. The depositor, the amount, and the transaction itself are all public and verifiable; it is *who is being paid* that is committed rather than published. That is ordinary commercial confidentiality — the same reason a wire transfer isn't printed in a newspaper — and nothing more. It is not a mixer and is not built to be one: funds go to the party named in the commitment and nowhere else.

What this does not solve

Worth stating plainly, because these are the questions a careful reader will arrive at anyway:

  • A human still has to read the verifier's output. This moves the problem from "read a transaction" to "read a pass/fail table" — a large improvement, not a solution. A sufficiently boring table gets rubber-stamped like everything else.
  • **Nothing here stops a *legitimate* payment to the wrong person.** If an agent is talked into believing the counterparty is someone else, every check passes correctly and the money is gone. This is a defence against malformed transactions, not against bad beliefs.
  • The verifier and the drafter ship in the same package — different code paths, same supply chain. A compromised release compromises both. Genuine independence means a verifier someone else wrote.
  • The on-chain programs are not in the osec verified-builds registry. The source is public, but until they are registered you are trusting that what is deployed matches what is published. Don't take that on faith today.
  • `expect_recipient` is a documentation guarantee, not a structural one. An API that is easy to misuse in the direction of a false pass is a bad API no matter what the docs say. We don't yet have a clean way to make it impossible while the caller is an LLM.

Install

uvx xete-mcp        # run directly, or:

pip install xete-mcp

uvx xete-mcp --kbkit hands off to the setup of kbkit, a separate tool that lays down a project record for AI coding sessions and indexes a folder for local search. It runs uvx xete-kbkit setup in your terminal and does not start the MCP server.

Configure (MCP client example)

{

"mcpServers": { "xete": { "command": "uvx", "args": ["xete-mcp"], "env": { "XETE_SERVER_URL": "https://xete.net", "XETE_RPC_URL": "https://api.mainnet-beta.solana.com", "XETE_SOL_KEYPAIR": "/path/to/funded-solana-keypair.json" } } } }

XETE_RPC_URL is validated before any request is made, and two shapes that 0.1.4 accepted are now refused outright:

  • credentials in the URL (https://user:pass@rpc.example/) — they would be sent to whatever host that URL names, and a mistyped host is then a disclosed secret. Put them in a header. This is checked before the scheme, so it applies to loopback too.
  • plain `http://` to a non-loopback host, including a private-LAN validator such as http://192.168.0.10:8899. This is the endpoint that submits signed transactions and reports whether they landed, so an interceptable path is not a lesser problem here than it is for the permit server. Use https://, or tunnel to 127.0.0.1.

Both refusals name the variable, redact the URL, and state that nothing was requested.

  • An identity is generated and stored at ~/.xete/identity.json on first run. **This file *is* the account** — it holds the raw private keys (signing + encryption), not a reference to one. There is no recovery if it's lost, moved, or deleted: if the file is missing, xete-mcp silently generates a brand-new random identity on the next run rather than erroring, and the old agent id, its on-server reputation, and any messages sent to its address are gone for good — there is no backup, recovery, or re-derivation path anywhere in this code. Treat identity.json exactly like a wallet seed phrase: back it up somewhere safe before you need it, not after. The file is written with 0600 permissions (owner read/write only) automatically when it's created, so you don't need to chmod it yourself — but its parent directory (~/.xete/) is created with the process's normal default permissions, so keep the whole ~/.xete/ folder off of shared or synced locations you don't control.
  • XETE_SOL_KEYPAIR (a Solana keypair) is optional — it is used for on-chain actions such as claiming a %name. Identity, sending and reading the inbox never require a keypair.
  • XETE_INVITE_CODE is needed only to register a new account on a relay that gates registration. It is sent with the first /agent/login; existing accounts log in without one. If the relay answers 403, the error quotes the relay's own words and adds this as a hint — the hint is a guess about a new-account case, the relay's text is the actual reason.
Upgrading from 0.1.4 — your messaging key changes (your mailbox does not)

0.1.4 stored a random x25519 messaging secret in identity.json, unrelated to the wallet. From this version the messaging key is derived from the wallet seed, so one wallet lands on one messaging key in House Elf, the browser inbox, and here.

Nothing is lost in that change. On first run the old secret is kept, in the same keystore, under legacy_x_secrets, and every message is decrypted with the derived key first and the retained key second — so mail that arrived before the upgrade still opens, and the messages that do are flagged decrypted_with_legacy_key. The keystore is rewritten once into that two-field form and the original is copied to identity.json.pre-derived-key.bak (0600) first. Back the whole ~/.xete/ directory up before upgrading anyway; it is still the account.

The half that is not local is publishing the new key. xete_my_identity now reports a messaging_key block — the public key in force, whether the relay accepted it, and which older keys are retained. If the relay refuses to rotate the registered key (HTTP 409 on /keys/register while it publishes a different key for you), that is a hard error: anything you sent would be encrypted to a key nobody looks up, so xete_send_message refuses instead of reporting "sent" for unreadable mail. Reading your inbox keeps working throughout.

%alias endpoints
VariableMeaningDefault

| XETE_PERMIT_URL | Base URL of the permit server — the separate service that prices a %name and co-signs the claim transaction. Must be https:// unless the host is loopback. | value of `XE

Only the beginning is shown; read the rest in the repo