Skip to main content
Glama

Features

  • Native HBAR + USDC transfers on Hedera through Hedera Token Service, no bridges or wrapped assets. Charge either asset for x402 endpoints by toggling X402_ASSET.

  • x402 autopay with the full protocol loop: detect 402, sign payment, retry with proof, deliver content. Buyer pays no gas because the resource server acts as fee payer.

  • Budget caps enforced before every signature, both per-call and per-UTC-day, so a runaway agent cannot drain the account.

  • MCP native with seven JSON-RPC tools exposed over stdio, works with Claude Desktop, Cursor, Windsurf, and any MCP host.

  • Reliable balance queries via Hedera Mirror Node REST so cross-region traffic never times out on gRPC.

  • Full audit trail through the spending report tool: session totals, budget usage, and a rolling history of the last 25 payments.

  • Local x402 demo server included, so you can exercise the full flow on your own machine without any hosted dependency.

  • MetaMask-compatible ECDSA keys, use a single private key across web3 wallets and Hedwig without conversion.


Related MCP server: pay-mcp

Architecture

System architecture

x402 payment flow


Tools

Seven tools exposed to the agent over MCP. Every tool that moves money runs through the budget checker before it signs.

Tool

What it does

check_balance

Return HBAR and USDC balances plus a HashScan account link. Reads from Mirror Node REST for reliability.

transfer_hbar

Send HBAR to any Hedera account. Real on-chain transfer, optional memo, HashScan link returned.

transfer_usdc

Send USDC (HTS token 0.0.429274 on testnet) to another USDC-associated account.

pay

Sign an x402 payment authorization without submitting anything. Useful when you want to drive the HTTP retry yourself.

x402_fetch

Full protocol loop: fetch a URL, catch the 402, sign the payment, retry with the signature header, return the paid body.

spending_report

Session totals, current budget usage, and a rolling history of the last 25 signed payments.

request_funding

Return your account ID plus a link to the Hedera Portal faucet, for topping up testnet HBAR.


Quick start

Three lines and you have a wallet an agent can drive.

git clone https://github.com/DarshanKrishna-DK/Hedwig.git
cd Hedwig
run.bat        # Windows.  Or ./run.sh on macOS or Linux.

run.bat installs dependencies, compiles TypeScript, runs the unit test suite, submits a real on-chain smoke transaction (produces HashScan links), boots the MCP server on stdio, and opens the landing page site in a separate window. Leave both windows open. On first run it will pause and ask you to fill in .env with your Hedera testnet Account ID and ECDSA private key from portal.hedera.com/dashboard.

For the paid endpoint your agent will hit, open another terminal:

start-x402-server.bat                   # Windows
node examples/x402-server/server.mjs    # cross-platform

By default the demo server charges 0.001 HBAR per request. To switch to USDC, add X402_ASSET=usdc to .env and restart the server.

Wire Hedwig into Claude Desktop

Edit %APPDATA%\Claude\claude_desktop_config.json on Windows, or ~/Library/Application Support/Claude/claude_desktop_config.json on macOS. Add this block and restart Claude Desktop fully from the system tray.

{
  "mcpServers": {
    "hedwig": {
      "command": "node",
      "args": ["C:/path/to/Hedwig/dist/index.js"],
      "env": {
        "HEDERA_ACCOUNT_ID": "0.0.YOUR_ID",
        "HEDERA_PRIVATE_KEY": "YOUR_ECDSA_KEY",
        "NETWORK": "hedera-testnet",
        "MAX_PER_CALL": "0.10",
        "MAX_PER_DAY": "20.00"
      }
    }
  }
}

Open a new chat and check the plug icon in the bottom-left. You should see hedwig with seven tools.

Talk to your agent

> Check my Hedera balance.
> Send 0.05 HBAR to 0.0.9865777 with the memo "coffee tip".
> Send 0.001 USDC to 0.0.9865777.
> Fetch http://localhost:4021/premium/quote and pay if it costs HBAR.
> Fetch http://localhost:4021/premium/quote and pay if it costs USDC.
> Show me my spending report.

Live testnet transactions

Every link below is a real transaction on Hedera testnet, submitted through Hedwig during a live demo run.

Accounts. Buyer: 0.0.6886052. Auto-created x402 server: 0.0.9865777.

#

What

Asset

On-chain proof

1

HBAR transfer (0.05 HBAR)

HBAR native

0.0.6886052-1785556514-498454371

2

USDC transfer (0.001 USDC)

HTS 0.0.429274

0.0.6886052-1785556535-966482234

3

x402 payment (first run)

USDC

0.0.9865777-1785556125-503661238

4

x402 payment (repeat)

USDC

0.0.9865777-1785556582-000507004

Rows 3 and 4 are the heart of the project. Agent hit 402, signed a payment on its own, retried with the payment signature header, and only got content after settlement reached consensus. No wallet popup, no manual approval, no bridge. Notice both transaction IDs start with the server account rather than the buyer, which proves gasless UX: the resource server pays HBAR gas as facilitator while the buyer only signs the transfer authorization.


Repo layout

Path

Role

src/

MCP server: seven tools, config, Hedera helpers, spending tracker

__tests__/

Vitest unit tests for spending, config, and Hedera helpers

examples/x402-server/

Local x402 paid endpoint, auto-creates its own Hedera account

projects/Hedwig-frontend/

React site with landing page and docs (Vite + Tailwind + Framer Motion)

docs/

Architecture diagrams as SVG

scripts/smoke.mjs

End-to-end on-chain smoke test that produces HashScan links

DEMO.md

Beat-by-beat script for the demo video recording


Scripts

Command

Purpose

run.bat / ./run.sh

Full end-to-end. Install, build, test, smoke, launch MCP + landing site.

run-frontend.bat / ./run-frontend.sh

Landing page + docs site only, on port 5173.

start-x402-server.bat

Boot the local paid endpoint on port 4021.

smoke.bat

Fast re-run of the on-chain smoke test only.

npm run build

Compile the MCP server TypeScript to dist/.

npm test

Run the 10 unit tests.

npm run smoke

On-chain smoke test producing HashScan links.

npm run build:mcpb

Package as an .mcpb bundle for one-click Claude Desktop install.

Network: Hedera testnet. HBAR asset id in x402: 0.0.0. USDC HTS token id: 0.0.429274 (testnet). HashScan: https://hashscan.io/testnet.

Available Tools

7 tools
check_balanceA

Return HBAR and USDC balances for the configured Hedera account, plus a HashScan link. Reads from the Hedera Mirror Node REST API for reliability.

Inputs: no named parameters.

payA

Sign an x402 payment authorization for a USDC transfer on Hedera. Returns the header value your HTTP client should attach when retrying the paid request.

Inputs: amount (required), recipient (required), feePayer, resource.

request_fundingA

Return a fundable receiving address for the configured Hedera account, plus a testnet faucet link (testnet only).

Inputs: no named parameters.

spending_reportA

Return the current session's USDC spending summary, budget caps, and full history of x402 payments and transfers.

Inputs: no named parameters.

transfer_hbarA

Send HBAR from the configured account to another Hedera account. Amount is in HBAR (e.g. "0.5"), not tinybars.

Inputs: amount (required), recipient (required), memo.

transfer_usdcA

Send USDC (HTS token) from the configured account to another Hedera account. Both accounts must be associated with the USDC token.

Inputs: amount (required), recipient (required), memo.

x402_fetchA

Fetch a URL that may be x402-gated. If the server returns 402, sign a Hedera USDC payment, retry with the payment header, and return the final response body. Includes diagnostic info in the response for debugging.

Inputs: url (required), body, method, headers.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct operation: balance checking, two asset transfers, payment signing, spending analysis, gated fetch, and funding request. No two tools have overlapping purposes; x402_fetch uses pay internally but is clearly for HTTP retrieval.

    Naming Consistency3/5

    Mostly verb_noun (check_balance, transfer_hbar, transfer_usdc, request_funding), but 'pay' is a bare verb, 'spending_report' is a noun phrase, and 'x402_fetch' puts the object first. This mixed style reduces predictability.

    Tool Count5/5

    Seven tools is well-scoped for a payment and x402 server—enough to cover core operations without bloat.

    Completeness4/5

    Covers balances, transfers for both HBAR and USDC, x402 payment authorization and retrieval, spending reports, and funding. Missing a budget management tool (only reports caps, doesn't set them) but core workflows are complete.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      An MCP server for USDC payments on Base, enabling AI agents to check balances, send payments, generate payment requests, and view transaction history.
      4
      2
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server for agentic commerce, enabling AI agents to discover services, make x402 payments with USDC across multiple chains, and manage crypto wallets and token swaps.
      557 npm
      1
      MIT