Onchain Data MCP
mcpotherio.github.madlabs-tech/onchain-data-mcp · v0.2.1
Blockchain data for EVM and Solana: balances, tokens, prices, DeFi and RPC via free-tier vendors
run it
on your own machines, one way per deploy methodgenerated from the record, not tested yet
CHANGE_ME: check the image's README for its transport and port; this assumes streamable HTTP at :8000/mcp. If it speaks stdio only, use it from clients/mcp.json as a `docker run -i` command instead.
#!/usr/bin/env bash
# onchain-data (io.github.madlabs-tech/onchain-data-mcp), recipe docker (generated).
# Generated by Hub for toolset "my-agent"; started by mcp-my-agent-onchain-data.service.
set -euo pipefail
export HOST=127.0.0.1 PORT=8101
exec docker run --rm --name mcp-my-agent-onchain-data -p 127.0.0.1:${PORT}:8000 --env-file /etc/mcp/my-agent.env ghcr.io/madlabs-tech/onchain-data-mcp:0.2.1
[Unit]
Description=MCP server onchain-data (toolset my-agent), generated by Hub
After=network-online.target docker.service
Wants=network-online.target
[Service]
Type=simple
User=mcp
Group=mcp
SupplementaryGroups=docker
EnvironmentFile=/etc/mcp/my-agent.env
Environment=HOME=/var/lib/mcp/onchain-data
WorkingDirectory=/var/lib/mcp/onchain-data
ExecStart=/opt/mcp/my-agent/bin/onchain-data.sh
Restart=on-failure
RestartSec=5
NoNewPrivileges=true
ProtectSystem=strict
ProtectHome=true
PrivateTmp=true
ReadWritePaths=/var/lib/mcp/onchain-data
[Install]
WantedBy=multi-user.target
generated from the record, not tested yet
CHANGE_ME: check the image's README for its transport and port; this assumes streamable HTTP at :8000/mcp. If it speaks stdio only, use it from clients/mcp.json as a `docker run -i` command instead.
docker run --rm -p 127.0.0.1:8101:8000 -e ALCHEMY_API_KEY -e HELIUS_API_KEY -e COINGECKO_API_KEY -e MORALIS_API_KEY ghcr.io/madlabs-tech/onchain-data-mcp:0.2.1
generated from the record, not tested yet
CHANGE_ME: check the image's README for its transport and port; this assumes streamable HTTP at :8000/mcp. If it speaks stdio only, use it from clients/mcp.json as a `docker run -i` command instead.
# Generated by Hub for toolset "my-agent" (2026-10-18T01:30:03+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:
onchain-data:
image: ghcr.io/madlabs-tech/onchain-data-mcp:0.2.1
ports:
- 127.0.0.1:8101:8000
restart: unless-stopped
x-note: 'CHANGE_ME: check the image''s README for its transport and port; this assumes streamable
HTTP at :8000/mcp. If it speaks stdio only, use it from clients/mcp.json as a `docker run -i` command
instead.'
environment:
ALCHEMY_API_KEY: ${ALCHEMY_API_KEY}
HELIUS_API_KEY: ${HELIUS_API_KEY}
COINGECKO_API_KEY: ${COINGECKO_API_KEY}
MORALIS_API_KEY: ${MORALIS_API_KEY}
volumes:
npm-cache: {}
uv-cache: {}
generated from the record, not tested yet
CHANGE_ME: check the image's README for its transport and port; this assumes streamable HTTP at :8000/mcp. If it speaks stdio only, use it from clients/mcp.json as a `docker run -i` command instead.
# Generated by Hub for toolset "my-agent" (2026-10-18T01:30:03+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: onchain-data
namespace: mcp
labels: &id001
app: onchain-data
spec:
replicas: 1
selector:
matchLabels: *id001
template:
metadata:
labels: *id001
spec:
containers:
- name: onchain-data
image: ghcr.io/madlabs-tech/onchain-data-mcp:0.2.1
ports:
- containerPort: 8000
name: http
env:
- name: ALCHEMY_API_KEY
valueFrom:
secretKeyRef:
name: mcp-credentials
key: ALCHEMY_API_KEY
- name: HELIUS_API_KEY
valueFrom:
secretKeyRef:
name: mcp-credentials
key: HELIUS_API_KEY
- name: COINGECKO_API_KEY
valueFrom:
secretKeyRef:
name: mcp-credentials
key: COINGECKO_API_KEY
- name: MORALIS_API_KEY
valueFrom:
secretKeyRef:
name: mcp-credentials
key: MORALIS_API_KEY
---
apiVersion: v1
kind: Service
metadata:
name: onchain-data
namespace: mcp
spec:
selector:
app: onchain-data
ports:
- port: 8000
targetPort: http
name: http
generated from the record, not tested yet
CHANGE_ME: check the image's README for its transport and port; this assumes streamable HTTP at :8000/mcp. If it speaks stdio only, use it from clients/mcp.json as a `docker run -i` command instead.
# Generated by Hub for toolset "my-agent" (2026-10-18T01:30:03+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:
onchain-data:
enabled: true
replicas: 1
port: 8000
path: /mcp
container:
name: onchain-data
image: ghcr.io/madlabs-tech/onchain-data-mcp:0.2.1
ports:
- containerPort: 8000
name: http
env:
- name: ALCHEMY_API_KEY
valueFrom:
secretKeyRef:
name: mcp-credentials
key: ALCHEMY_API_KEY
- name: HELIUS_API_KEY
valueFrom:
secretKeyRef:
name: mcp-credentials
key: HELIUS_API_KEY
- name: COINGECKO_API_KEY
valueFrom:
secretKeyRef:
name: mcp-credentials
key: COINGECKO_API_KEY
- name: MORALIS_API_KEY
valueFrom:
secretKeyRef:
name: mcp-credentials
key: MORALIS_API_KEY
# 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: ALCHEMY_API_KEY, HELIUS_API_KEY, COINGECKO_API_KEY, MORALIS_API_KEY. 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 needsdocker run -i --rm -e ALCHEMY_API_KEY -e HELIUS_API_KEY -e COINGECKO_API_KEY -e MORALIS_API_KEY ghcr.io/madlabs-tech/onchain-data-mcp:0.2.1
{
"mcpServers": {
"onchain-data": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"ALCHEMY_API_KEY",
"-e",
"HELIUS_API_KEY",
"-e",
"COINGECKO_API_KEY",
"-e",
"MORALIS_API_KEY",
"ghcr.io/madlabs-tech/onchain-data-mcp:0.2.1"
],
"env": {
"ALCHEMY_API_KEY": "${ALCHEMY_API_KEY}",
"HELIUS_API_KEY": "${HELIUS_API_KEY}",
"COINGECKO_API_KEY": "${COINGECKO_API_KEY}",
"MORALIS_API_KEY": "${MORALIS_API_KEY}"
}
}
}
}
#!/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 onchain-data -e "ALCHEMY_API_KEY=${ALCHEMY_API_KEY}" -e "HELIUS_API_KEY=${HELIUS_API_KEY}" -e "COINGECKO_API_KEY=${COINGECKO_API_KEY}" -e "MORALIS_API_KEY=${MORALIS_API_KEY}" -- docker run -i --rm -e ALCHEMY_API_KEY -e HELIUS_API_KEY -e COINGECKO_API_KEY -e MORALIS_API_KEY ghcr.io/madlabs-tech/onchain-data-mcp:0.2.1
{
"mcpServers": {
"onchain-data": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"ALCHEMY_API_KEY",
"-e",
"HELIUS_API_KEY",
"-e",
"COINGECKO_API_KEY",
"-e",
"MORALIS_API_KEY",
"ghcr.io/madlabs-tech/onchain-data-mcp:0.2.1"
],
"env": {
"ALCHEMY_API_KEY": "${ALCHEMY_API_KEY}",
"HELIUS_API_KEY": "${HELIUS_API_KEY}",
"COINGECKO_API_KEY": "${COINGECKO_API_KEY}",
"MORALIS_API_KEY": "${MORALIS_API_KEY}"
}
}
}
}
{
"servers": {
"onchain-data": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"ALCHEMY_API_KEY",
"-e",
"HELIUS_API_KEY",
"-e",
"COINGECKO_API_KEY",
"-e",
"MORALIS_API_KEY",
"ghcr.io/madlabs-tech/onchain-data-mcp:0.2.1"
],
"env": {
"ALCHEMY_API_KEY": "${ALCHEMY_API_KEY}",
"HELIUS_API_KEY": "${HELIUS_API_KEY}",
"COINGECKO_API_KEY": "${COINGECKO_API_KEY}",
"MORALIS_API_KEY": "${MORALIS_API_KEY}"
}
}
}
}
name: my-agent target: local servers: - hub: io.github.madlabs-tech/onchain-data-mcp
- 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.