Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Gloam

REMOTE · WWW.GLOAM.TRADE · 2 COMPONENTS

Private stablecoin payments for people and AI agents on mainnet, hosted or local with limits.

+3 this week 84 Trust /100

Last scanned (1 hour ago)

Scores higher than 89% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Crypto and Web3

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability60
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2503 tokens (~278/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
  • Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 +1
    • Tool “gloam_networks” rewrote its description, which is the text the model reads security
    • “gloam_create_payment_request” reworded the description of “network” cosmetic
    • “gloam_vault_stats” reworded the description of “network” cosmetic
    • “gloam_swap_quote” reworded the description of “network” cosmetic
    • “gloam_plan_deposit” reworded the description of “network” cosmetic
    • “gloam_networks” reworded the description of “network” cosmetic
    • “gloam_mpp_how_to” reworded the description of “network” cosmetic
  • 2 Nov 26 +1
    • Schema quality: 2163 → 2532 ▼ functional
    • Schema quality: good → excellent functional
    • New tool “gloam_swap_quote” functional
  • 1 Nov 26 0
    • Tool “gloam_networks” rewrote its description, which is the text the model reads security
    • Schema quality: excellent → good functional
    • “gloam_mpp_how_to” reworded the description of “network” cosmetic
    • “gloam_create_payment_request” reworded the description of “network” cosmetic
    • “gloam_vault_stats” reworded the description of “network” cosmetic
    • “gloam_plan_deposit” reworded the description of “network” cosmetic
    • “gloam_networks” reworded the description of “network” cosmetic
  • 30 Oct 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “gloam_networks” rewrote its description, which is the text the model reads security
  • 27 Oct 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: 221 → 251 ▼ functional
    • “gloam_create_payment_request” reworded the description of “network” cosmetic
    • “gloam_mpp_how_to” reworded the description of “network” cosmetic
    • “gloam_networks” reworded the description of “network” cosmetic
    • “gloam_plan_deposit” reworded the description of “network” cosmetic
    • “gloam_vault_stats” reworded the description of “network” cosmetic
  • 26 Oct 26 0
    • “gloam_plan_deposit” reworded the description of “network” cosmetic
    • “gloam_networks” reworded the description of “network” cosmetic
    • “gloam_mpp_how_to” reworded the description of “network” cosmetic
    • “gloam_create_payment_request” reworded the description of “network” cosmetic
    • “gloam_vault_stats” reworded the description of “network” cosmetic

    5 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.

  • 25 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “gloam_verify_proof” rewrote its description, which is the text the model reads security
    • “gloam_mpp_how_to” reworded the description of “network” cosmetic
    • “gloam_networks” reworded the description of “network” cosmetic
    • “gloam_plan_deposit” reworded the description of “network” cosmetic
    • “gloam_vault_stats” reworded the description of “network” cosmetic
    • “gloam_create_payment_request” reworded the description of “network” cosmetic
  • 24 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://www.gloam.trade/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.gloam.trade CN=YR1,O=Let's Encrypt,C=US 13 Sept 2026 12 Dec 2026 RSA 2048 SHA256-RSA 6e750b39ae73c047d55bf3b4b3be55c0cb1
SANs: *.gloam.trade, gloam.trade
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of www.gloam.trade. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
trade. present 64969 8 Verified
gloam.trade. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000
content-security-policy frame-ancestors 'none'; base-uri 'self'; object-src 'none'; form-action 'self'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), browsing-topics=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.gloam.trade/mcp Verified 200
http (plaintext) http://www.gloam.trade/mcp HTTPS enforced 308 https://www.gloam.trade/mcp
MCP tools · 9 exposed · ~2,253 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
gloam_connect_full_agent ~94

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.

NameTypeReqDescription
clientstring–Which app to show commands for.

No output schema declared.

No examples provided.

gloam_create_payment_request ~398

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.

NameTypeReqDescription
amountstring–Amount in whole units, e.g. "12.50". Leave out to let the payer choose.
assetstring–Token symbol or address, e.g. USDG on Robinhood Chain, OUSD or PathUSD on Tempo. Default: the network's main stablecoin.
namestring–Your name as the payer should see it (up to 40 characters).
networkstring–Gloam network: "robinhood-mainnet" (Robinhood Chain mainnet: USDG, GLOAM, PONS, CASHCAT, ETH, AI and ORBIO), "tempo-mainnet" (Tempo mainnet: USDC.e, pathUSD, USDT0, OUSD), "base-mainnet" (Base mainne…
notestring–A reference the payer sees, e.g. "Invoice 042" (up to 80 characters).
tostringyesYour Gloam address to be paid at, gloamr1.… (public; find it in the app under Receive).

No output schema declared.

No examples provided.

gloam_info ~59

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

gloam_mpp_how_to ~274

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.

NameTypeReqDescription
networkstring–Gloam network: "robinhood-mainnet" (Robinhood Chain mainnet: USDG, GLOAM, PONS, CASHCAT, ETH, AI and ORBIO), "tempo-mainnet" (Tempo mainnet: USDC.e, pathUSD, USDT0, OUSD), "base-mainnet" (Base mainne…
rolestring–"charge" to get paid for an API or tool, "pay" for an agent or app paying one, "both" for both.

No output schema declared.

No examples provided.

gloam_networks ~332

The networks Gloam runs on, mainnets first, with each vault (pool) address, the private swap routers (Robinhood Chain and Tempo mainnet), the assets you can deposit (on mainnet: USDC.e, pathUSD, USDT0 and OUSD on Tempo; USDG, GLOAM, PONS, CASHCAT, ETH, AI and ORBIO on Robinhood Chain; USDC, EURC, USDT and ETH on Base; USDC, USDT, USDG, PYUSD, EURC and ETH on Ethereum; on testnet: OUSD and PathUSD on Tempo, USDG and ETH on Robinhood Chain, and more on Base Sepolia and Ethereum Sepolia), explorers, RPCs and the testnet faucets.

NameTypeReqDescription
networkstring–Gloam network: "robinhood-mainnet" (Robinhood Chain mainnet: USDG, GLOAM, PONS, CASHCAT, ETH, AI and ORBIO), "tempo-mainnet" (Tempo mainnet: USDC.e, pathUSD, USDT0, OUSD), "base-mainnet" (Base mainne…

No output schema declared.

No examples provided.

gloam_plan_deposit ~269

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.

NameTypeReqDescription
amountstring–Amount in whole units, e.g. "25".
assetstring–Token symbol or address. Default: the network's main stablecoin (OUSD on Tempo, USDG on Robinhood Chain).
networkstring–Gloam network: "robinhood-mainnet" (Robinhood Chain mainnet: USDG, GLOAM, PONS, CASHCAT, ETH, AI and ORBIO), "tempo-mainnet" (Tempo mainnet: USDC.e, pathUSD, USDT0, OUSD), "base-mainnet" (Base mainne…

No output schema declared.

No examples provided.

gloam_swap_quote ~365

Quote a private swap from a private Gloam balance: what you would get, the route, the vault's fee, and the first thing that would stop the swap (too thin a pool, a refund the vault could not take back, the relay's floor where gas is dear), or none. Read only: it never builds or sends a swap. A private swap hides who swapped; the tokens and amounts are public. To swap, use the Gloam app or the local server (npx -y @gloamtrade/mcp, gloam_execute_private_swap).

NameTypeReqDescription
amountstringyesHow much of `from` to swap, in whole units, e.g. "100" or "0.05".
fromstringyesThe asset you pay with: a symbol (USDG, ETH, USDC.e) or a token address.
networkstring–Gloam network: "robinhood-mainnet" (Robinhood Chain mainnet: USDG, GLOAM, PONS, CASHCAT, ETH, AI and ORBIO), "tempo-mainnet" (Tempo mainnet: USDC.e, pathUSD, USDT0, OUSD), "base-mainnet" (Base mainne…
tostringyesThe asset you receive: a symbol or a token address.

No output schema declared.

No examples provided.

gloam_vault_stats ~220

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.

NameTypeReqDescription
networkstring–Gloam network: "robinhood-mainnet" (Robinhood Chain mainnet: USDG, GLOAM, PONS, CASHCAT, ETH, AI and ORBIO), "tempo-mainnet" (Tempo mainnet: USDC.e, pathUSD, USDT0, OUSD), "base-mainnet" (Base mainne…

No output schema declared.

No examples provided.

gloam_verify_proof ~242

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. The result names the network: `network.testnet` true means the proof was made with test funds, not on mainnet. 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.

NameTypeReqDescription
proofstringyesThe full proof text, starting gloamfunds1:, gloampay1:, gloamroll1:, gloambal1: or gloamdisc1:.

No output schema declared.

No examples provided.

Install

How do I install the Gloam MCP server?

Gloam is a hosted endpoint at https://www.gloam.trade/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · www.gloam.trade

# add to Claude Code
claude mcp add --transport http cryptoduke01-gloam 'https://www.gloam.trade/mcp'
Common questions

What is the Gloam MCP server?

Gloam is an MCP server listed in the public MCP registry as io.github.cryptoduke01/gloam. Private stablecoin payments for people and AI agents on mainnet, hosted or local with limits. This page covers its hosted endpoint (https://www.gloam.trade/mcp).

Is the Gloam MCP server safe to use?

Gloam scores 84 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Gloam MCP server expose?

Gloam exposes 9 tools: gloam_info, gloam_networks, gloam_vault_stats, gloam_create_payment_request, gloam_verify_proof, and 4 more. Their descriptions and schemas cost roughly 2,253 tokens of context every time the server is loaded.

Does the Gloam MCP server require authentication?

No. We connected to Gloam without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Gloam MCP server still maintained?

Gloam is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.