Gloam
by cryptoduke01 · remote · local (npm) · no sign-in to list tools · v1.2.0 · published by GitHub user cryptoduke01
Private stablecoin payments for people and AI agents on mainnet, hosted or local with limits.
8 tools: 1 do something that can't be undone and 7 change things.
Scanned Oct 21, 2026
- Deletes or cancels0Claude Code: deny
- Can't be undone1Claude Code: ask: see these tools
- Changes things7Claude Code: ask: see these tools
- Only reads0Claude Code: allow
1 check matched something in the tool definitions. No finding is not a safety guarantee. How the checks work.
claude mcp add --transport http gloam https://www.gloam.trade/mcpFindings
Matches of fixed checks, with the text they matched.
The server marks "gloam_create_payment_request" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "gloam_create_payment_request" says "create": a word for a change.
Tools
Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.
8 tools
Can't be undone 1Claude Code: ask
gloam_create_payment_requestMake a link that asks someone to pay your Gloam address privately.1 finding
Why it is in this group
- The name "gloam_create_payment_request" says "create": a word for a change.
- The name "gloam_create_payment_request" also says "payment": a word that usually means money moves, which cannot be taken back.
- The input addresses people (input.to): what it sends cannot be taken back.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "gloam_create_payment_request" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "gloam_create_payment_request" says "create": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- title: Create a payment request link
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Changes things 7Claude Code: ask
gloam_connect_full_agentCommands 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, Curs…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: Connect the full Gloam agent
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
gloam_infoWhat Gloam is, what this hosted server can do, and where to go to sign or spend.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: About Gloam
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
gloam_mpp_how_toHow to pay or charge privately over MPP (the Machine Payments Protocol, HTTP 402) with the gloam method from @gloamtrade/mppx-gloam, with code.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: Private payments over MPP
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
gloam_networksThe networks Gloam runs on, mainnets first, with each vault (pool) address, the assets you can deposit (on mainnet: USDC.e, pathUSD, USDT0 and OUSD on Tempo, USDG and GLOAM on Robi…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it The networks Gloam runs on, mainnets first, with each vault (pool) address, the assets you can deposit (on mainnet: USDC.e, pathUSD, USDT0 and OUSD on Tempo, USDG and GLOAM on Robinhood Chain; on testnet: OUSD and PathUSD on Tempo, USDG and ETH on Robinhood Chain), explorers, RPCs and the testnet faucets.
Annotations the server declares
- title: Networks and assets
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
gloam_plan_depositPlan 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.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: Plan a private deposit
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
gloam_vault_statsPublic totals for each Gloam vault, read from the chain: what it holds, and counts of deposits, private transfers, cash outs and payment messages.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: Vault stats
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
gloam_verify_proofCheck a Gloam proof someone shared with you: proof of funds (gloamfunds1:), proof of payment (gloampay1:), payroll total (gloamroll1:) or exact balance (gloambal1:).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: Verify a Gloam proof
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Install
Pinned to version 1.2.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http gloam https://www.gloam.trade/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [],
"ask": [
"mcp__gloam__gloam_info",
"mcp__gloam__gloam_networks",
"mcp__gloam__gloam_vault_stats",
"mcp__gloam__gloam_create_payment_request",
"mcp__gloam__gloam_verify_proof",
"mcp__gloam__gloam_plan_deposit",
"mcp__gloam__gloam_mpp_how_to",
"mcp__gloam__gloam_connect_full_agent"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as gloam. Review it before you use it.
