Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Private stablecoin payments for people and AI agents on mainnet, hosted or local with limits.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
GLOAM_NETWORK, GLOAM_AGENT_PRIVATE_KEY, GLOAM_TEMPO_ACCOUNT, GLOAM_NOTE_KEY标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
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/mcpclaude 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 只能连接互联网上的服务器:
https://www.gloam.trade/mcp菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
GLOAM_NETWORK envGLOAM_TEMPO_ACCOUNT env这些设置是根据作者在注册中心的条目生成的。如果 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
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
注册名称已通过 GitHub 账户 cryptoduke01 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
在 172 毫秒内响应(HTTP 200)
无需登录
已读取 9 个工具描述,未发现针对 AI 的隐藏指令
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:GLOAM_AGENT_PRIVATE_KEY, GLOAM_NOTE_KEY
两种方式都可以:安装在你的电脑上,或者连接云端版本。
GitHub 仓库最后更新于–,最新版本(1.4.0)于昨天进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Spec Driven Development, Remote Desktop Commander, Fomu MCP
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Kenya government form guides: checklists, draft letters, eCitizen, Huduma, timelines. Sample data.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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.
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 proves 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.context input bound into the solvency, receipt and payroll_total proofs. 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.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.
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.
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 |
0xB390…30B8), and half of them are set to buy back $GLOAM, half of that burned and half kept.ceremony-final).Addresses are in Contracts below.
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
只显示了开头部分;其余内容请在仓库中阅读