mcpbeat Sign in

Gloam MCP Server

by cryptoduke01 Your server? Claim it
not responding

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.

Installs per day peak 29 · avg 1
a month agotoday
Uptime history 6 days of history · worst day 29%
6 days agonow
35.2%
Uptime 24h
32 of 91 checks
8
Tools
read from the server
456 ms
Response time
average over 24h
48
Installs / week
npm and PyPI

What changed 2

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 11 October 2026. No other catalogue keeps this.

11 Oct a tool description was rewritten gloam_verify_proof
11 Oct a tool changed the parameters it asks for gloam_verify_proof

What the code does

We read the source, 1 h ago · tools taken from the live server · rules ccca72095570

Capabilities

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.

Sends data to a third-party sink app/src/lib/telegramBot/telegram.ts:100
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.

This code can reach further than it looks

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.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.

run in your terminal
claude mcp add gloam --transport http https://www.gloam.trade/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "gloam": {
      "url": "https://www.gloam.trade/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.gloam]
url = "https://www.gloam.trade/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "gloam": {
      "url": "https://www.gloam.trade/mcp"
    }
  }
}
.vscode/mcp.json
{
  "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.

Available tools 8

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

gloam
gloam_connect_full_agent
Commands to install the local Gloam MCP server, which can sign and pay (shield, private pay, x402 and MPP, spending limits) with keys kept on your machine: Claude Code, Codex, Cursor, VS Code, Claude Desktop and any MCP client, plus the plugin marketplace cryptoduke01/gloam-plugins.
gloam_create_payment_request
Make a link that asks someone to pay your Gloam address privately. It opens Pay in the Gloam app with the address, amount, asset and note filled in; the payer checks and sends. The details ride after the # of the link, so the payer's browser never sends them to a server. Needs your public Gloam address (gloamr1.…), never a key.
gloam_info
What Gloam is, what this hosted server can do, and where to go to sign or spend. Call this first. This server only reads and plans: it never holds funds and never takes a private key, recovery phrase or note secret.
gloam_mpp_how_to
How to pay or charge privately over MPP (the Machine Payments Protocol, HTTP 402) with the gloam method from @gloamtrade/mppx-gloam, with code. A charge settles as a private transfer in a Gloam vault: the chain sees no amount, asset, payer or payee.
gloam_networks
The networks Gloam runs on, with each vault (pool) address, the assets you can deposit (OUSD and PathUSD on Tempo, USDG and ETH on Robinhood Chain), explorers, RPCs and faucets.
gloam_plan_deposit
Plan a deposit into a private Gloam balance (a shield): the steps, what becomes public and what stays private, and the app link to do it. Does not sign or send anything; you sign in your own wallet in the app.
gloam_vault_stats
Public totals for each Gloam vault, read from the chain: what it holds, and counts of deposits, private transfers, cash outs and payment messages. Totals only, no wallets. Cached about a minute.
gloam_verify_proof
Check a Gloam proof someone shared with you: proof of funds (gloamfunds1:), proof of payment (gloampay1:), payroll total (gloamroll1:) or exact balance (gloambal1:). Runs the same checks as gloam.trade/verify on the server: the zero-knowledge proof, that it was made on Gloam's vault, who it is for, expiry, and the live vault state. A proof of payment shows a private payment was made, not who paid whom; a payroll total shows a run of payments the prover funded, not who was paid. The older gloamdisc1 balance disclosure is never verified: anyone can copy one from a public deposit. Proofs are meant to be shared; they hold no secrets.

Endpoints

URLTransportStateLatencyChecked
https://www.gloam.trade/mcp streamable-http answering 56 ms 12 min ago

Alternatives to Gloam

same job, measured the same way
Clawvault MCP Server
by andrewszk

AI agent payment security - spending limits, whitelists, and human approval.

64 installs/wk local only
AgentPay
by rumblingb

Agent payments, API key vaulting, and governed mandates. Agents spend within user-defined limits.

106 installs/wk answering
SRA-RiskGate
by sriram1983007-dev

Check stablecoin and x402 payments before an AI agent pays: approve, hold or reject.

411 installs/wk local only
XDC AI
by 0xbeny

Wallet and payments for AI agents: auto-pay x402 APIs in USDC on XDC, within on-chain limits.

answering
ClawPay MCP — Non-Custodial x402 Payments for AI Agents
by up2itnow0822

Non-custodial x402 payments for AI agents. Sign locally, spend limits, Base network.

39 installs/wk local only
Lightning Wallet
by lightningfaucet

Give AI agents a Bitcoin wallet with Lightning Network payments and L402 support.

147 installs/wk local only
Lightningfaucet
by lightningfaucet

Give AI agents a Bitcoin wallet with Lightning Network payments and L402 support.

30 installs/wk local only
Agiscorecard Web3 Reconcile
by f-tiger

Reconcile declared stablecoin invoices and transfers; flag partial, pending and mismatched payments.

3 tools answering

Gloam — questions

Answers built from our own checks of this server.

What can Gloam do?
It exposes 8 tools, read directly from the server on our last check. Among them: gloam_connect_full_agent, gloam_create_payment_request, gloam_info, gloam_mpp_how_to, gloam_networks, gloam_plan_deposit and 2 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Gloam working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 32 of 91 checks got a reply (35.2%), average response time 456 ms. The bar chart above shows every period we have measured.
The registry lists Gloam as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Gloam?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Gloam need an API key?
No. Gloam completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 8 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Gloam?
It answers our handshake in 456 ms on average, which is faster than 29% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use Gloam?
The npm package @gloamtrade/mcp was installed 48 times in the last week. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is Gloam open source?
Yes — it is published under the MIT licence, written in TypeScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.