HPP x402 MCP Bridge
mcpkey · packageio.github.hpp-io/x402-mcp-bridge · v0.1.22
MCP bridge for autonomous x402 payments in HPP USDC.e — discover and pay for services per call.
run it
on your own machines, one way per deploy methodgenerated from the record, not tested yet
#!/usr/bin/env bash # x402-mcp-bridge (io.github.hpp-io/x402-mcp-bridge), recipe baremetal (generated). # Generated by Hub for toolset "my-agent"; started by mcp-my-agent-x402-mcp-bridge.service. set -euo pipefail export HOST=127.0.0.1 PORT=8101 exec npx -y supergateway@4 --stdio 'npx -y @hpp-io/[email protected]' --outputTransport streamableHttp --stateful --host 127.0.0.1 --port 8101 --streamableHttpPath /mcp --healthEndpoint /healthz [Unit] Description=MCP server x402-mcp-bridge (toolset my-agent), generated by Hub After=network-online.target Wants=network-online.target [Service] Type=simple User=mcp Group=mcp EnvironmentFile=/etc/mcp/my-agent.env Environment=HOME=/var/lib/mcp/x402-mcp-bridge WorkingDirectory=/var/lib/mcp/x402-mcp-bridge ExecStart=/opt/mcp/my-agent/bin/x402-mcp-bridge.sh Restart=on-failure RestartSec=5 NoNewPrivileges=true ProtectSystem=strict ProtectHome=true PrivateTmp=true ReadWritePaths=/var/lib/mcp/x402-mcp-bridge [Install] WantedBy=multi-user.target
generated from the record, not tested yet
docker run --rm -p 127.0.0.1:8101:8000 -e DELEGATE_PRIVATE_KEY -e HPP_NETWORK -e RESOURCE_SERVER_URL -e SAFE_ADDRESS -e ALLOWANCE_MODULE_ADDRESS node:22-alpine sh -c 'npx -y supergateway@4 --stdio '"'"'npx -y @hpp-io/[email protected]'"'"' --outputTransport streamableHttp --stateful --host 0.0.0.0 --port 8000 --streamableHttpPath /mcp --healthEndpoint /healthz'
generated from the record, not tested yet
# Generated by Hub for toolset "my-agent" (2026-10-18T14:23:50+00:00).
# Each package server runs behind a stdio->HTTP bridge and listens on localhost only.
# cp .env.example .env # fill the ${VAR}s
# docker compose up -d && bash smoke.sh
# Remote servers are not here: clients reach them directly (see clients/).
name: mcp-my-agent
services:
x402-mcp-bridge:
image: node:22-alpine
command:
- sh
- -c
- npx -y supergateway@4 --stdio 'npx -y @hpp-io/[email protected]' --outputTransport streamableHttp
--stateful --host 0.0.0.0 --port 8000 --streamableHttpPath /mcp --healthEndpoint /healthz
ports:
- 127.0.0.1:8101:8000
volumes:
- npm-cache:/root/.npm
healthcheck:
test:
- CMD-SHELL
- wget -qO- http://127.0.0.1:8000/healthz || exit 1
interval: 30s
timeout: 5s
retries: 5
start_period: 2m
restart: unless-stopped
environment:
DELEGATE_PRIVATE_KEY: ${DELEGATE_PRIVATE_KEY}
HPP_NETWORK: ${HPP_NETWORK}
RESOURCE_SERVER_URL: ${RESOURCE_SERVER_URL}
SAFE_ADDRESS: ${SAFE_ADDRESS}
ALLOWANCE_MODULE_ADDRESS: ${ALLOWANCE_MODULE_ADDRESS}
volumes:
npm-cache: {}
uv-cache: {}
generated from the record, not tested yet
# Generated by Hub for toolset "my-agent" (2026-10-18T14:23:50+00:00).
# kubectl create namespace mcp
# kubectl -n mcp create secret generic mcp-credentials --from-env-file=.env
# kubectl apply -f kubernetes.yaml
# Services are cluster-internal: <name>.mcp.svc.cluster.local:8000/mcp. Put an ingress
# with auth in front before exposing any of them.
apiVersion: v1
kind: Namespace
metadata:
name: mcp
---
apiVersion: apps/v1
kind: Deployment
metadata:
name: x402-mcp-bridge
namespace: mcp
labels: &id001
app: x402-mcp-bridge
spec:
replicas: 1
selector:
matchLabels: *id001
template:
metadata:
labels: *id001
spec:
containers:
- name: x402-mcp-bridge
image: node:22-alpine
ports:
- containerPort: 8000
name: http
env:
- name: DELEGATE_PRIVATE_KEY
valueFrom:
secretKeyRef:
name: mcp-credentials
key: DELEGATE_PRIVATE_KEY
- name: HPP_NETWORK
valueFrom:
secretKeyRef:
name: mcp-credentials
key: HPP_NETWORK
- name: RESOURCE_SERVER_URL
valueFrom:
secretKeyRef:
name: mcp-credentials
key: RESOURCE_SERVER_URL
- name: SAFE_ADDRESS
valueFrom:
secretKeyRef:
name: mcp-credentials
key: SAFE_ADDRESS
- name: ALLOWANCE_MODULE_ADDRESS
valueFrom:
secretKeyRef:
name: mcp-credentials
key: ALLOWANCE_MODULE_ADDRESS
command:
- sh
- -c
- npx -y supergateway@4 --stdio 'npx -y @hpp-io/[email protected]' --outputTransport streamableHttp
--stateful --host 0.0.0.0 --port 8000 --streamableHttpPath /mcp --healthEndpoint /healthz
readinessProbe:
httpGet:
path: /healthz
port: http
initialDelaySeconds: 10
---
apiVersion: v1
kind: Service
metadata:
name: x402-mcp-bridge
namespace: mcp
spec:
selector:
app: x402-mcp-bridge
ports:
- port: 8000
targetPort: http
name: http
generated from the record, not tested yet
# Generated by Hub for toolset "my-agent" (2026-10-18T14:23:50+00:00).
# Credentials come from the Secret 'mcp-credentials' (kubectl create secret generic ... --from-env-file=.env).
# Each server under `servers` is one Deployment + Service; the keys after it configure
# upstream charts a worker verified.
servers:
x402-mcp-bridge:
enabled: true
replicas: 1
port: 8000
path: /mcp
container:
name: x402-mcp-bridge
image: node:22-alpine
ports:
- containerPort: 8000
name: http
env:
- name: DELEGATE_PRIVATE_KEY
valueFrom:
secretKeyRef:
name: mcp-credentials
key: DELEGATE_PRIVATE_KEY
- name: HPP_NETWORK
valueFrom:
secretKeyRef:
name: mcp-credentials
key: HPP_NETWORK
- name: RESOURCE_SERVER_URL
valueFrom:
secretKeyRef:
name: mcp-credentials
key: RESOURCE_SERVER_URL
- name: SAFE_ADDRESS
valueFrom:
secretKeyRef:
name: mcp-credentials
key: SAFE_ADDRESS
- name: ALLOWANCE_MODULE_ADDRESS
valueFrom:
secretKeyRef:
name: mcp-credentials
key: ALLOWANCE_MODULE_ADDRESS
command:
- sh
- -c
- npx -y supergateway@4 --stdio 'npx -y @hpp-io/[email protected]' --outputTransport streamableHttp
--stateful --host 0.0.0.0 --port 8000 --streamableHttpPath /mcp --healthEndpoint /healthz
readinessProbe:
httpGet:
path: /healthz
port: http
initialDelaySeconds: 10
# helm install my-agent helm/my-agent -n mcp
in the cloud
one click: the provider's deploy form opens filled in, in your own account- koyeb
-
The form opens with CHANGE_ME for each value you supply: DELEGATE_PRIVATE_KEY, HPP_NETWORK, RESOURCE_SERVER_URL, SAFE_ADDRESS, ALLOWANCE_MODULE_ADDRESS. Fill them in before you deploy.
Clients connect to the service's https://…koyeb.app address plus /mcp.
- azure
-
A Container Apps environment with one app per server, each with HTTPS ingress and one replica. The portal asks for each value you supply as a secure parameter; the deployment's outputs list the endpoints.
connect to it
copy what your client needsnpx -y @hpp-io/[email protected] # env: DELEGATE_PRIVATE_KEY, HPP_NETWORK, RESOURCE_SERVER_URL, SAFE_ADDRESS, ALLOWANCE_MODULE_ADDRESS
{
"mcpServers": {
"x402-mcp-bridge": {
"command": "npx",
"args": [
"-y",
"@hpp-io/[email protected]"
],
"env": {
"DELEGATE_PRIVATE_KEY": "${DELEGATE_PRIVATE_KEY}",
"HPP_NETWORK": "${HPP_NETWORK}",
"RESOURCE_SERVER_URL": "${RESOURCE_SERVER_URL}",
"SAFE_ADDRESS": "${SAFE_ADDRESS}",
"ALLOWANCE_MODULE_ADDRESS": "${ALLOWANCE_MODULE_ADDRESS}"
}
}
}
}
#!/usr/bin/env bash
# Registers every server with Claude Code (run once; `claude mcp list` to check).
set -euo pipefail
set -a; [ -f .env ] && source .env; set +a
claude mcp add x402-mcp-bridge -e "DELEGATE_PRIVATE_KEY=${DELEGATE_PRIVATE_KEY}" -e "HPP_NETWORK=${HPP_NETWORK}" -e "RESOURCE_SERVER_URL=${RESOURCE_SERVER_URL}" -e "SAFE_ADDRESS=${SAFE_ADDRESS}" -e "ALLOWANCE_MODULE_ADDRESS=${ALLOWANCE_MODULE_ADDRESS}" -- npx -y @hpp-io/[email protected]
{
"mcpServers": {
"x402-mcp-bridge": {
"command": "npx",
"args": [
"-y",
"@hpp-io/[email protected]"
],
"env": {
"DELEGATE_PRIVATE_KEY": "${DELEGATE_PRIVATE_KEY}",
"HPP_NETWORK": "${HPP_NETWORK}",
"RESOURCE_SERVER_URL": "${RESOURCE_SERVER_URL}",
"SAFE_ADDRESS": "${SAFE_ADDRESS}",
"ALLOWANCE_MODULE_ADDRESS": "${ALLOWANCE_MODULE_ADDRESS}"
}
}
}
}
{
"servers": {
"x402-mcp-bridge": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@hpp-io/[email protected]"
],
"env": {
"DELEGATE_PRIVATE_KEY": "${DELEGATE_PRIVATE_KEY}",
"HPP_NETWORK": "${HPP_NETWORK}",
"RESOURCE_SERVER_URL": "${RESOURCE_SERVER_URL}",
"SAFE_ADDRESS": "${SAFE_ADDRESS}",
"ALLOWANCE_MODULE_ADDRESS": "${ALLOWANCE_MODULE_ADDRESS}"
}
}
}
}
name: my-agent target: local servers: - hub: io.github.hpp-io/x402-mcp-bridge
- not probed yet: tools unpinned, ingest lists them
tools
Not probed yetThe tools appear once the hub or its worker has listed this entry. Running it still works: your client lists them on first start.