Gloam
概要
作者による説明(英語の原文)
Private stablecoin payments for people and AI agents on mainnet, hosted or local with limits.
PopNx MCPの3つの柱
この3つを1つのスコアにまとめることはしません。意見、測定、人気はそれぞれ別のものだからです。
- 利用者の声iレビューはまだありませんレビューは今後のステップで、アカウント機能と一緒に始まります
- 私たちの基本チェックi3項目中3項目に合格公開情報からチェック。コードはまだスキャンしていません
- 利用状況i初期↓ 1245/週 · ★ –
できること
このサーバーのやさしい解説はまだ書いていません。以下はレジストリから読み取った事実です。
- 接続方法: パソコンでもクラウドでも
- トランスポート: stdio, Streamable HTTP
- カテゴリ: 暗号資産・ブロックチェーン
- 入力が必要なもの:GLOAM_AGENT_PRIVATE_KEY, GLOAM_NOTE_KEY
インストール
使っているAIアプリを選んで、設定をコピーしてください。
インストールの前に
- 基本チェック:3項目中3項目に合格
- 作者のサーバーで動きます。あなたが頼んだ内容は、作者のサーバーを通ります。
- できること:9件(ツール) gloam_info, gloam_networks, gloam_vault_stats, gloam_create_payment_request …
- 自分で入力するもの:
GLOAM_NETWORK,GLOAM_AGENT_PRIVATE_KEY,GLOAM_TEMPO_ACCOUNT,GLOAM_NOTE_KEY
「秘密」と表示された値は、あなたのアカウントの鍵です。絶対に人に教えたり、チャットに貼り付けたりしないでください。
必要なもの
どのアプリを使っていますか?
上でアプリを選んでください。選んだアプリを覚えておくので、次からはボタンに「…にインストール」と表示されます。
ウェブ、デスクトップ、モバイルのClaudeで使えます:
- Settings → Connectors を開く
- Add custom connector を押す
- 下のアドレスを貼り付けて Add を押す
- サインインを求められたら、作者のサービスにサインインする
https://www.gloam.trade/mcpまたは、パソコンで動かす
Claude Desktop → Settings → Developer → Edit Config を開き、claude_desktop_config.json にこれを貼り付けます
{
"mcpServers": {
"gloam": {
"command": "npx",
"args": [
"-y",
"@gloamtrade/mcp"
],
"env": {
"GLOAM_NETWORK": "your-value",
"GLOAM_AGENT_PRIVATE_KEY": "your-value",
"GLOAM_TEMPO_ACCOUNT": "your-value",
"GLOAM_NOTE_KEY": "your-value"
}
}
}
}ターミナルでこれを実行します
claude mcp add --transport http gloam https://www.gloam.trade/mcpまたは、パソコンで動かす
claude mcp add gloam --env GLOAM_NETWORK=your-value --env GLOAM_AGENT_PRIVATE_KEY=your-value --env GLOAM_TEMPO_ACCOUNT=your-value --env GLOAM_NOTE_KEY=your-value -- npx -y @gloamtrade/mcp動かす前に、空欄の値を入力してください。
または、設定を自分でコピーする
プロジェクトの .cursor/mcp.json、または ~/.cursor/mcp.json に貼り付けます
{
"mcpServers": {
"gloam": {
"url": "https://www.gloam.trade/mcp"
}
}
}または、パソコンで動かす
または、設定を自分でコピーする
プロジェクトの .cursor/mcp.json、または ~/.cursor/mcp.json に貼り付けます
{
"mcpServers": {
"gloam": {
"command": "npx",
"args": [
"-y",
"@gloamtrade/mcp"
],
"env": {
"GLOAM_NETWORK": "your-value",
"GLOAM_AGENT_PRIVATE_KEY": "your-value",
"GLOAM_TEMPO_ACCOUNT": "your-value",
"GLOAM_NOTE_KEY": "your-value"
}
}
}
}ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。
または、設定を自分でコピーする
プロジェクトの .vscode/mcp.json に貼り付けます
{
"servers": {
"gloam": {
"type": "http",
"url": "https://www.gloam.trade/mcp"
}
}
}または、パソコンで動かす
または、設定を自分でコピーする
プロジェクトの .vscode/mcp.json に貼り付けます
{
"servers": {
"gloam": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@gloamtrade/mcp"
],
"env": {
"GLOAM_NETWORK": "your-value",
"GLOAM_AGENT_PRIVATE_KEY": "your-value",
"GLOAM_TEMPO_ACCOUNT": "your-value",
"GLOAM_NOTE_KEY": "your-value"
}
}
}
}ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。
ChatGPTがつなげるのは、インターネット上のサーバーだけです:
- ウェブ版のChatGPTを開き → Settings → Connectors (Apps)
- Create または Add を押す(プランによっては、先に Advanced で Developer mode をオンにする必要があります)
- 下のアドレスを貼り付け、名前を付けて保存する
- サインインを求められたら、作者のサービスにサインインする
https://www.gloam.trade/mcpメニューの名前は、プランや時期によって少し違うことがあります。
選んだアプリは、この端末のCookieに保存されます。アカウントは不要です。
自分で入力する値
GLOAM_NETWORKenvDefault network for tools: tempo-mainnet, robinhood-mainnet, base-mainnet or ethereum-mainnet (mainnet); tempo, robinhood, base or ethereum (testnet; robinhood is the default when unset).- 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_ACCOUNTenvThe owner's Tempo account that authorized the agent key in the AccountKeychain.- 32 random bytes in hex that encrypt the server's note store.
この設定は、作者のレジストリ登録情報から作成しています。READMEと違う場合は、READMEに従ってください。
できること
ツールの名前と説明は、サーバーが2026年11月6日に返したそのままの内容です。書いたのは作者で、私たちではありません。プレーンテキストとして表示しています。
gloam_infoWhat 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_networksThe 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 C
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. Totals only, no wallets. Cached about a minute.
gloam_create_payment_requestMake 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 yo
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:). Runs the same checks as gloam.trade/verify on the server: the zero-knowledge proof, that it was made on Gloam's va
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. Does not sign or send anything; you sign in your own wallet in the app.
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. A charge settles as a private transfer in a Gloam vault: the chain sees no amount, asset, payer or payee.
gloam_swap_quoteQuote 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 s
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, Cursor, VS Code, Claude Desktop and any MCP client, plus the plugin marketplace cryptoduke01/gloam-plugi
基本チェックi
誰でも見られる情報をチェックしており、コードは読んでいません。当てはまらない項目は数に入れていません。 · 2026年11月9日にチェック
- ✓ 合格
作者とリポジトリが一致
レジストリ名は、リポジトリを所有するGitHubアカウント cryptoduke01 で確認済みです
- … 未チェック
今もメンテナンスされている
このリポジトリはまだGitHubから読み取っていません
- … 未チェック
ライセンスがある
このリポジトリはまだGitHubから読み取っていません
- ✓ 合格
エンドポイントが応答する
172ミリ秒で応答(HTTP 200)
- – 対象外
OAuthでサインイン
サインイン不要
- ✓ 合格
ツールの説明に隠れた指示がない
9件のツールの説明を読み、AIへの隠れた指示は見つかりませんでした
暗号資産・ブロックチェーンのほかのサーバーとの比較i
- このカテゴリのほかの1622件のうち0%よりスターが多い
- このカテゴリのほかの1622件のうち95%より最近レジストリに公開
- 基本チェックの結果が、このカテゴリのほかの1622件のうち100%と同じかそれ以上
レジストリでこのカテゴリにある有効なすべてのサーバーと比較しています。スターは、公開者がリポジトリの所有者である場合だけ数えます。
よくある質問
Gloamは安全ですか?
当てはまる基本チェック3項目のうち3項目に合格しました。コードは読んでいません。キーやトークンを追加する前に、サーバーがどんなアクセスを求めているかを確認し、必要な権限だけを持つキーを使ってください。
どんなキーやコードが必要ですか?
入力が必要なもの:GLOAM_AGENT_PRIVATE_KEY, GLOAM_NOTE_KEY
パソコンで動きますか、それともクラウドですか?
どちらでも使えます。パソコンにインストールしても、クラウド版につないでもかまいません。
今もメンテナンスされていますか?
GitHubリポジトリの最終更新は–、最新バージョン(1.4.0)がレジストリに届いたのは3 日前です。
どのアプリで使えますか?
Claude Desktop、Claude Code、Cursor、VS CodeなどのMCP対応アプリで使えます。URLでつながるので、リモートMCPサーバーに対応したアプリ(開発者モードのChatGPTなど)でも使えます。
代わりに使えるものは?
同じカテゴリには:Nftdata MCP, onchaincheck, Bvcc Agent Wallet
代わりの候補
同じカテゴリで、ほかの作者が作ったサーバー。スターの多い順。
カードの見方:↓ 週あたりのダウンロードi★ GitHubスターi3つの柱:レビュー · チェック · 利用状況i更新=最新バージョンをレジストリに公開した日i
onchaincheck
100+ pay-per-call tools: token risk, wallet sanctions screening, onchain data, web, company, AI
Bvcc Agent Wallet
Non-custodial BVCC Agent Wallet on-chain for AI agents: balances, transfers, approvals, swaps.
作者のREADME
READMEを開く
作者のリポジトリから書かれたとおりにコピーしたものです。PopNx MCPは内容を確認・推奨していません。HTML、画像、スクリプトは取り除いています。リンクはこのサイトの外へ移動します。
Gloam
Private money on public chains. Private stablecoin payments for people, teams and AI agents: private by default, provable on demand.
gloam.trade · App · Verify a proof · Research report and deck · How Gloam compares · Docs · Whitepaper · @gloamtrade
Live on mainnet (beta): Robinhood Chain 4663 · Tempo 4217 · Base 8453 · Ethereum 1 · real ZK proofs, no mock fills
Stablecoins are becoming how businesses and AI agents pay each other, and every one of those payments is public. Gloam makes them private, and lets the payer prove exactly what someone needs to see: a balance above a figure, that a payment was made, or a payroll total, to one named reader, with an expiry. It is live on four mainnets, Robinhood Chain, Tempo, Base and Ethereum, in beta with deposit limits. You can pay anyone privately, send money as a claim link, run payroll, swap straight from the private balance (who swapped stays private; the tokens and amounts are public, like any DEX trade), and cash out at once or privately in pieces over time.
Why one owner matters. Privacy splits into two jobs. Shared secrets (sealed auctions, order books, lending pools) need someone to compute on many people's hidden data, so FHE and MPC networks such as Zama and Arcium use a committee that holds keys. A payment has one owner, so the owner proves it on their own device with zero-knowledge proofs, and nobody else ever holds a key. If a committee or operator is breached, everyone can be exposed, past payments included. If one owner's device is breached, one person is. Gloam does not invent new cryptography: it uses the proven ZK maths of the Zcash lineage and builds the payments product on top. Full comparison with Zama, Arcium, Tempo Zones, Helius Privacy and Railgun: gloam.trade/docs/compare.
What is new
Gloam is not new cryptography. It is a new building block for finance: private payments you can prove. As far as our research found, three parts are new:
- Payroll total proof.
payroll_totalproves a run of up to 32 payments adds up to exactly a total, all funded by the prover, without showing who got what. We found nothing like it. - Proofs scoped to one reader. The label (who the proof is for), expiry, chain and pool are hashed into a public
contextinput bound into thesolvency,receiptandpayroll_totalproofs. Change the label and the proof fails. Anyone can check one in a browser, with no wallet, at/verify. Viewing keys, the usual alternative, show a whole history and cannot be taken back. - Private payments for AI agents. A private payment method proposed for the Machine Payments Protocol from Tempo and Stripe (tempoxyz/mpp-specs#376; MPP had no private method), private x402 payments, and an MCP server that gives agents handles instead of secrets, with spending limits.
Not new: the private pool design (Zcash lineage from 2016, Tornado, Railgun, Cloak) and selective disclosure as an idea (Zcash and Railgun viewing keys, Privacy Pools, Zama decryption rights). One honest limit: a reader can still forward a proof. It says who it was for and when it expires, and a designated-verifier mode is next.
Three surfaces, one private core
The vault app is the reference implementation, not the whole product.
| Surface | What it is | Package |
|---|---|---|
| SDK | Drop shielded balances, private sends, and selective disclosure into any onchain app or agent, on Robinhood Chain, Tempo, Base or Ethereum. Unsigned intents + client proving. | @gloamtrade/sdk |
| Agents | An MCP server + a reference wrapper so an AI agent can shield, move value, and pay for tools privately over x402 or MPP, under policy. | @gloamtrade/mcp · @gloamtrade/mppx-gloam · examples/ |
| Vault | The live app on all four mainnets that proves the whole path works. | app/ |
| Partner API | Apps add private payments with an API key, set their own fee (flat per private payment, a share of cash outs and deposits), and see attributed volume and would-be fees live in the partner portal. Partner fees are not collected yet, on mainnet either: every response says "charged": false and the portal shows what the setting would earn. Only Gloam's own 0.5% cash-out fee is taken on mainnet. Live keys (gloam_live_) are for the mainnets, test keys (gloam_test_) for the testnets. | /partners · /docs/partners · GloamApiClient |
All three share one core: a Poseidon note scheme, a depth-20 incremental Merkle tree, circom witness builders, real Groth16 verification, and one canonical intent shape.
Mainnet beta
Gloam is live on Robinhood Chain mainnet (4663) and Tempo mainnet (4217) since Wednesday 21 October 2026, 13:00 UTC, and on Base mainnet (8453) and Ethereum mainnet (1) since 26 October 2026. The vault has the same address on all four, 0x39E28Cde55CAB798874746ac52cb4B5Cc99a0194. This is beta software. It was reviewed internally before launch (20 October 2026, no Critical or High findings open), and an independent review on 23 October found no new exploitable contract flaw and eight app issues, and fixes in each of the areas it named were merged by 24 October. Kann Audits reviewed the vault contracts (report, 1 November 2026: gloam.trade/security) and found no Critical, High or Medium issues; the swap routers, circuits, app and relay were not part of it.
Robinhood Chain 4663 | Tempo 4217 | Base 8453 | Ethereum 1 | |
|---|---|---|---|---|
| Live since | 21 October 2026 | 21 October 2026 | 26 October 2026 | 26 October 2026 |
| Pool | ShieldPoolPayments, payments only | ShieldPoolPayments, payments only | ShieldPoolPayments, payments only | ShieldPoolPayments, payments only |
| Assets | USDG, $GLOAM, PONS, CASHCAT, ETH, AI, ORBIO; GRIFT once its timelocked limit lands | USDC.e, pathUSD, USDT0, OUSD | USDC, EURC, USDT, ETH | USDC, USDT, USDG, PYUSD, EURC, ETH |
| Gas | ETH | Paid in stablecoins | ETH | ETH; the relay waits while gas is above its ceiling |
| Keys | Final keys from the trusted setup | Final keys from the trusted setup | Final keys from the trusted setup | Final keys from the trusted setup |
| Private swaps | Router v2 (GloamVaultSwapV4b) swaps the 29 tokens it lists, stock tokens and ETH (as WETH) included, over allowlisted Uniswap v4 pools. Router v1 (GloamVaultSwapV4) stays for refunds | USDC.e, pathUSD, USDT0, OUSD on Tempo's stablecoin exchange (GloamVaultSwapTempo) | Not yet | Not yet |
- Fees. Direct deposits and private payments are free. Cashing out costs 0.5%, taken when the cash out lands, at the vault's rate that day. A private swap pays the same 0.5% on the amount swapped, plus a price buffer (0.5% on Robinhood Chain, 0.1% on Tempo) whose unused part goes to the treasury. Money bridged in from another chain pays Relay's fee, and Gloam's own fee when one is set, shown before you send. Since 24 October fees go to their own treasury wallet (
0xB390…30B8), and half of them are set to buy back $GLOAM, half of that burned and half kept. - Beta deposit limits. 50,000 per deposit and 2,500,000 in total for each stablecoin; ETH on Base and Ethereum 20 per deposit and 1,000 in total; $GLOAM 2,500,000 per deposit and 25,000,000 in total. Cash outs and private payments are never limited. Raising a limit or adding an asset waits a public 3-day timelock; the owner can lower limits or close deposits at once.
- Keys. Mainnet proofs use the final keys from the 13-contributor trusted setup (drand round 6561386, release
ceremony-final). - Partners. Raeto funds AI agents from a private Gloam balance, and Agent Wormhole checks an agent's payment request before it pays (MCP 0.4.0, optional).
Addresses are in Contracts below.
What works today (real ZK proofs)
Everything here runs on all four mainnets unless the row says otherwise.
| Path | Status | What you can do |
|---|---|---|
| Shield | Live, proof-gated | Deposit USDG (Paxos Global Dollar) and $GLOAM on Robinhood Chain; USDC.e, pathUSD, USDT0 and OUSD on Tempo; USDC, EURC, USDT and ETH on Base; USDC, USDT, USDG, PYUSD, EURC and ETH on Ethereum, within the beta deposit limits. The pool enforces shieldBound() so a deposit proves commitment == Poseidon(secret, amount, asset) (audit C1) |
| Private send | Live | Send inside the vault to a Gloam address. The recipient finds it through an encrypted heads-up on the payment board (GloamPayMemo) on each chain, which never logs who posted. The Gloam relay posts the heads-up, so your wallet is not the sender either |
| Private payroll | Live | Upload a CSV and pay a whole team at once in any vault stablecoin. Gloam-address payees are paid directly and get an encrypted heads-up; everyone else gets a claim link. Crash-safe resume, results export. Docs |
| Scheduled payroll | Live | Save a pay list as a schedule (monthly, every two weeks, weekly or one time) with a cap per run and an end date. A "Payroll due" reminder runs it in one click. Runs happen in your browser because only you hold the keys; schedules are encrypted at rest |
| Payment requests | Live | Share a link or QR that opens Pay with your Gloam address, amount, asset and reference filled in. The details sit after the #, so they never reach a server and nothing about the request goes on-chain |
| Claim links | Live | Send money to anyone as a link. Claiming is free: no gas, no seed phrase, nothing to buy. The claim moves the payment into a fresh note only the claimer knows, so the sender cannot spend it back |
| Gloam relay | Live | Submits proven sends, cash outs, private swaps and payment memos from a Gloam account so the user's wallet never appears. One request per spend at a time, small memos only, and no cash out to the vault itself. Dry-runs every payment against the pool first; cash-out recipients are bound in the proof, so the relay can only submit or refuse. On mainnet the Gloam team runs the relayer at launch: it pays gas and cannot move or redirect money. SDK relayIntent, MCP GLOAM_USE_RELAY=1 |
| Passkey lock | Live, optional | Protect the private balance on a browser with a passkey (Face ID, Touch ID, security key). The WebAuthn PRF output wraps the key that encrypts notes at rest, so the app unlocks only with the passkey. Backups stay restorable without it. Browsers without PRF keep the device key. Docs |
| Sanctions screening | Live | Checked against a vendored snapshot of the OFAC sanctioned-address list (EVM): the depositing wallet in the app before signing and at /api/screen, and every cash-out address inside the relay before it submits. Public addresses only; a blocked wallet sees one neutral message. Refresh with node app/scripts/refresh-ofac-list.mjs; optional Chainalysis check via CHAINALYSIS_API_KEY |
| Issuer policies (Tempo) | Live | Deposits and cash outs on Tempo also respect the stablecoin's TIP-403 transfer policy: the wallet must be allowed to send and the vault to r
冒頭だけを表示しています。続きはリポジトリで読めます