XGR.Network MCP
xgr-networkLABSCO SUMMARY
The missing half of paid APIs for agents.
HTTP 402 has been in the spec for decades with almost nothing behind it; the interesting bet here is that agents are the use case that finally makes it real. What you get is small and specific — a wallet, in the session, able to settle a payment when a service asks for one. The obvious consequence is that a component of your agent stack now holds spendable funds, so the key handling and the balance you fund it with are decisions, not details.
What it is
An MCP server that carries a Solana wallet for an AI agent, so the agent can pay for services that respond with HTTP 402. On first run it generates a wallet and prints the public key, the balance in lamports and SOL, and any recent transactions; on later runs it loads the existing private key from the system keyring.
What you get
- A wallet the agent can pay from, generated on first launch and reloaded from the keyring afterwards
- Payment for services that answer with HTTP 402, driven from inside the MCP session rather than out of band
- Wallet state on startup — public key, balance in lamports alongside the SOL figure, and recent transactions with explorer links
- A working checkpoint before you wire it into a client: run the server in a terminal and read the wallet information it prints
Requirements
No account signup — the wallet is created locally and the private key is stored in the system keyring. The README's install line names latinum-wallet-mcp, which PyPI does not have. To run from source: create a virtualenv, install requirements.txt, then python3 -m latinum_wallet_mcp.server_stdio. The pyproject name is latinum-wallet-mcp (0.0.30) with the entry point latinum-wallet-mcp. Since it holds a spendable key, treat the machine it runs on accordingly.
Setup effort
Build from source — git clone https://github.com/Latinum-Formal-Methods/latinum-wallet-mcp.git
USE CASES
01
Letting an agent buy access to a paid endpoint
When a service answers with HTTP 402, the agent settles the payment through the wallet and retries, instead of stopping and asking you.
02
Trying agent payments without risking much
Run it once, read the printed public key and balance, and work against a small funded wallet while you see how the flow behaves.
03
Checking what the agent has been spending
Read the startup output — balance plus recent transactions with explorer links — to see what actually went out.
BEFORE YOU INSTALL
What to know first
Requires
- Python 3.10+
- git
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
git clone https://github.com/Latinum-Formal-Methods/latinum-wallet-mcp.git
cd latinum-wallet-mcp
python3 -m venv .venv && source .venv/bin/activate
pip install --upgrade pip
pip install --upgrade --upgrade-strategy eager -r requirements.txt
pip install --editable .MCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"latinum_wallet_mcp": {
"command": "<YOUR_PATH_TO_LATINUM_WALLET_MCP>/.venv/bin/latinum-wallet-mcp"
}
}
}Use the output of which latinum-wallet-mcp, run with the .venv from the steps above still active. The steps install the command into that clone's .venv/bin, not into ~/.local/bin.
