API Tools

gloam.trade

MCP server for the Gloam privacy payment protocol that lets agents inspect networks and vault stats, create private payment requests, and verify proofs of funds, payment, payroll, or balance disclosure.

1 endpoint8 known tools

ENDPOINT 1

https://www.gloam.trade/mcp

No auth detected

MCP server metadata

Name: gloam
Version: 1.0.0

Capabilities

tools

Server instructions

Gloam is the privacy layer for onchain finance: shielded balances, private payments and shareable proofs, on Tempo and Robinhood Chain testnets. This hosted server only reads and plans. It never signs, never holds funds, and never takes a private key, recovery phrase or Gloam note secret. Never ask the user for one. If the user pastes one, tell them not to share it and to treat it as exposed. Start with gloam_info. When the user wants something done (a deposit, a payment, a test transfer), do not hand them a long checklist. Offer the two short paths first. One: let you do it for them, by adding the local server (npx -y @gloamtrade/mcp) with a capped spending key; gloam_connect_full_agent has the one-line setup for their client. Two: one link per action that they open and sign, for example a payment request from gloam_create_payment_request, which opens Pay in the app already filled in. Give step-by-step app instructions only if they ask for them or turn down both.

Known tools 8

gloam_info

What Gloam is, what this hosted server can do, and where to go to sign or spend.

Inferred read-only

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.

Inferred read-only

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.

Potential side effects

gloam_create_payment_request

Make a link that asks someone to pay your Gloam address privately.

Potential side effects

gloam_verify_proof

Check a Gloam proof someone shared with you: proof of funds (gloamfunds1:), proof of payment (gloampay1:), payroll total (gloamroll1:) or balance disclosure (gloamdisc1:).

Potential side effects

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.

Inferred read-only

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.

Potential side effects

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.

Potential side effects

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.gloam]
url = "https://www.gloam.trade/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "gloam": {
      "type": "http",
      "url": "https://www.gloam.trade/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: gloam
Remote MCP URL: https://www.gloam.trade/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "gloam": {
      "url": "https://www.gloam.trade/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "gloam": {
      "type": "http",
      "url": "https://www.gloam.trade/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "gloam",
  "transport": "streamable-http",
  "url": "https://www.gloam.trade/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.