Gloam is listed as active in the registry but did not answer our last check. 48 installs a week from npm. It exposes 8 tools. Last commit 11 Oct 2026.
Private stablecoin payments for people and AI agents, hosted or local with spending limits.
Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 11 October 2026. No other catalogue keeps this.
We read the source, 1 h ago · tools taken from the live server · rules ccca72095570
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
const API = "https://api.telegram.org";
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.
claude mcp add gloam --transport http https://www.gloam.trade/mcp
{
"mcpServers": {
"gloam": {
"url": "https://www.gloam.trade/mcp"
}
}
}
[mcp_servers.gloam]
url = "https://www.gloam.trade/mcp"
{
"mcpServers": {
"gloam": {
"url": "https://www.gloam.trade/mcp"
}
}
}
{
"mcpServers": {
"gloam": {
"url": "https://www.gloam.trade/mcp"
}
}
}
This one needs environment variables set before it will start:
GLOAM_AGENT_PRIVATE_KEY (The agent's key. With GLOAM_TEMPO_ACCOUNT it is a Tempo access key bound by the owner's onchain limits. Optional: without it the tools only read and plan.), GLOAM_TEMPO_ACCOUNT (The owner's Tempo account that authorized the agent key in the AccountKeychain.), GLOAM_NOTE_KEY (32 random bytes in hex that encrypt the server's note store.).
The author declared them in the registry entry; get the values from the project itself.
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
gloam_connect_full_agent
gloam_create_payment_request
gloam_info
gloam_mpp_how_to
gloam_networks
gloam_plan_deposit
gloam_vault_stats
gloam_verify_proof
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://www.gloam.trade/mcp | streamable-http | answering | 56 ms | 12 min ago |
AI agent payment security - spending limits, whitelists, and human approval.
Agent payments, API key vaulting, and governed mandates. Agents spend within user-defined limits.
Check stablecoin and x402 payments before an AI agent pays: approve, hold or reject.
Wallet and payments for AI agents: auto-pay x402 APIs in USDC on XDC, within on-chain limits.
Non-custodial x402 payments for AI agents. Sign locally, spend limits, Base network.
Give AI agents a Bitcoin wallet with Lightning Network payments and L402 support.
Give AI agents a Bitcoin wallet with Lightning Network payments and L402 support.
Reconcile declared stablecoin invoices and transfers; flag partial, pending and mismatched payments.
Answers built from our own checks of this server.