Dero Mcp Server

MCP金融服务

提供方 DHEBP

金融服务 stdio · 本地进程 会话登录 社区 / 第三方 Claude DesktopClaudeCursorCodex
查看接入方式

Read-only MCP server for querying DERO blockchain. Get block heights, inspect smart contracts, look up transactions, query network info. Privacy-first: runs locally, no accounts, no tracking.

一句话选型结论

按资料字段整理

Dero Mcp Server 属于金融服务类 MCP 服务器,stdio · 本地进程,会话登录,可直接接入 Claude Desktop、Claude、Cursor 等,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类金融服务 传输方式stdio · 本地进程 鉴权会话登录 部署方式本地部署
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

金融服务
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

blockchainprivacycryptocurrency

安装与配置

stdio · 本地进程 会话登录
客户端在本机拉起子进程,数据不出本机
node /ABSOLUTE/PATH/TO/dero-mcp-server/dist/index.js

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Cross-platform,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
行情与财务数据

查行情、财报、汇率等金融数据。

支付与账务查询

查订单、账单与交易流水。

风控与核验

做身份、信用与风险信息核验。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude Desktop、Claude、Cursor,换客户端不用重新研究配置。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 使用前要准备好会话登录对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在金融服务场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Dero Mcp Server当前 未标注 stdio · 本地进程 本地部署 有 未标注
Alpaca MCP 62 stdio · 本地进程 支持远程部署 有 2026-05-18
OpenNews MCP 11 stdio · 本地进程 支持远程部署 有 2026-05-17
MCP Server 273df76d 未标注 stdio · 本地进程 本地部署 有 2026-05-17
tradingview-mcp 未标注 stdio · 本地进程 本地部署 有 2026-04-19
goat (Goat SDK) 未标注 未标注 未标注 无 2026-05-17

服务器档案

金融服务
字段来自项目仓库与公开索引,中文说明由本站标注
提供方DHEBP上游标注的维护方 DHEBP
分类金融服务本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式会话登录远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · Cross-platform本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验未标注上游最后核验时间

详细介绍

14.7 KB
来自项目仓库与上游目录的原文,未做删改

DERO MCP server

> A read-only Model Context Protocol server for the DERO privacy blockchain — a private-by-default Layer 1 with encrypted balances, private smart contracts (DVM-BASIC), and no public transaction graph. 21 daemon primitives + 12 composite tools (including TELA on-chain app inspection and dURL→SCID discovery), with a bundled documentation index spanning derod, tela, hologram, and deropay.

Registry listing: io.github.DHEBP/dero-mcp-server · Version: 0.6.0 · Transports: stdio (default, npm package) · streamable-http (--http, for self-hosting)


What is an MCP server

An MCP server (Model Context Protocol) is a small program that gives your AI assistant — Claude Desktop, Cursor, OpenCode, ChatGPT with Custom Connectors — the ability to call specific tools on your behalf. Instead of the AI talking about DERO from memory, it can actually look things up: fetch a block, read a contract, search the docs, trace a transaction, estimate a deploy.

You install it once and point your AI host at it. From then on, every DERO question you ask in chat hits live chain data and the bundled docs corpus — not the AI's training cutoff.

What is DERO

If you're new to DERO: it's a privacy-first L1 blockchain — often described as a private alternative to Ethereum for builders who want smart contracts without a transparent ledger, or as a Monero alternative for users who want account-based privacy with native programmability instead of UTXO-only payments. Homomorphically encrypted balances. Ring signatures hide senders. Zero-knowledge range proofs (Bulletproofs) hide amounts. There is no public transaction graph. The current mainnet is DERO Stargate.

Full docs: derod.org

About this server

Model Context Protocol (MCP) server that exposes read-only and analysis calls against a DERO Stargate daemon JSON-RPC endpoint. Ships as a stdio process for local MCP hosts (Claude Desktop, Cursor, OpenCode) or in streamable-HTTP mode behind a domain (e.g. mcp.derod.org) for ChatGPT Custom Connectors, Cursor hosted mode, and any agent that needs a remote URL. See deploy/ for a reference self-hosted deployment.

Quick start

Get a working DERO MCP connection in under 5 minutes.

What you need

  • Node.js 20+ (install) — verify with node --version.
  • An MCP host — Claude Desktop, Cursor, OpenCode, or ChatGPT with Custom Connectors. This walkthrough uses Claude Desktop; the JSON config below works identically in Cursor and OpenCode.
  • Optional: a local DERO daemon. If one is running on 127.0.0.1:10102, the server detects and uses it automatically; otherwise it falls back to a public RPC, so it works with zero setup. Run your own for production — how to.

1. Open your MCP host's config

Host Where
Claude Desktop (macOS) ~/Library/Application Support/Claude/claude_desktop_config.json
Claude Desktop (Windows) %APPDATA%\Claude\claude_desktop_config.json
Cursor Settings → MCP → Add Server
OpenCode Settings → MCP → Add Server
Codex CLI / IDE codex mcp add or ~/.codex/config.toml

Create the file if it doesn't exist.

2. Add the DERO MCP server```json

{
"mcpServers": {
"dero-daemon": {
"command": "npx",
"args": ["-y", "dero-mcp-server"]
}
}
}


This uses `npx` to fetch and run the latest published version — no manual install or build required.

The server **auto-detects a local node** at `127.0.0.1:10102`. To pin a specific daemon (custom port or a remote URL), add an `env` block:```json
"env": { "DERO_DAEMON_URL": "http://127.0.0.1:10102" }

3. Restart your MCP host

Fully quit and reopen — not just refresh. MCP servers load at startup.

4. Verify it works

In a new chat:

> "What's the current DERO chain height?"

A number back means you're connected. If you see an error, confirm the config file path is correct and your host was fully restarted (not just refreshed).

Once it's working, jump to Try a prompt for a full tour.


What you can do with it

Once installed, your MCP host can do all of these on your behalf — in natural language, no JSON-RPC needed:

  • Inspect the chain — blocks, transactions, mempool, encrypted balances, registered names
  • Analyze smart contracts — read code and state, classify the pattern, estimate deploy gas, pull relevant DVM-BASIC docs in one call
  • Trace transactions — look up any hash, confirm inclusion, classify the kind (transfer / SC install / SC call)
  • Explore the on-chain web (TELA) — discover apps by name (vault.tela → SCID), browse what's deployed, inspect an app's manifest and files, and read the actual on-chain HTML/JS/CSS — no separate indexer to run
  • Search the docs — across all four DERO sites (derod, tela, hologram, deropay)
  • Run composite analyses — chain health, claim audits, docs path recommendations, deploy pre-flights — each returns curated DERO docs citations alongside the data

Try a prompt

After installing and restarting your MCP host, paste any of these. Start simple and work up.

Basic

Single-tool questions that verify the install and exercise live queries.

> "What's the current DERO chain height?"
>
> "Resolve the DERO name 'engram' to an address."
>
> "Find the documentation page on Bulletproofs."
>
> "What does the smart contract at SCID 0000…0001 do?"

Intermediate

Composite tools that fan out into multiple primitives and return a synthesized answer with citations.

> "Explain the smart contract at SCID 0000000000000000000000000000000000000000000000000000000000000001 — what it does, its functions, and which DVM-BASIC docs are relevant."
>
> "Trace transaction with full context — confirmation, classification, and what it touched."
>
> "What's the right reading path for someone new to DERO smart contracts who wants to deploy a DVM-BASIC contract?"
>
> "Estimate the gas cost to deploy this DVM source: "

TELA — the decentralized web on DERO

TELA apps are full web apps (HTML/CSS/JS) deployed entirely on-chain. The server discovers and reads them with no external indexer — the first discovery query runs a one-time ~15s scan, then it's instant.

> "What's the SCID for vault.tela?"
>
> "What TELA apps exist on DERO? Show me a few."
>
> "Inspect the TELA app at SCID — what is it, who made it, and what files does it have?"
>
> "Show me the actual HTML of that app's index.html."

For multi-step agent recipes, per-tool guidance, error contract, and the composite-first rule, see SKILL.md.

Not included (by design): wallet RPC (transfer, scinvoke), DERO.SendRawTransaction, DERO.SubmitBlock. Those can move funds or consensus data; add them only with explicit user consent and a locked-down setup.

See also

  • SKILL.md — per-tool agent runbook: composite-first rule, structured error contract, citation rules, agent-loop recipes, port reference.
  • POSITIONING.md — who DERO MCP is for, who it isn't, comparison vs ACP / Stripe / Crossmint / Skyfire, privacy posture.

Requirements

  • Node.js 20+
  • A reachable DERO daemon with RPC enabled (local node or your own remote URL).

Install & build```bash

cd dero-mcp-server
npm install
npm run build


Run (auto-detects a local node at `127.0.0.1:10102`, else public fallback, when `DERO_DAEMON_URL` is unset):```bash
node dist/index.js

Or set an explicit URL (e.g. your local daemon):```bash
DERO_DAEMON_URL=http://127.0.0.1:10102 node dist/index.js


Daemon resolution is **local-first**: with `DERO_DAEMON_URL` unset, the server uses a local node at `127.0.0.1:10102` if it answers, else the baked-in **third-party** public RPC (`82.65.143.182:10102`). Prefer your own node for privacy.

Strip a trailing `/json_rpc` if you paste a full JSON-RPC URL — this server appends `/json_rpc`.

## HTTP mode (self-hosted)

For clients that can't launch a local subprocess — ChatGPT Custom Connectors, Cursor hosted mode, n8n / Zapier integrations — run the server in streamable-HTTP mode and put it behind your own domain:```bash
DERO_MCP_AUTH_TOKEN=$(openssl rand -base64 48) \
  dero-mcp-server --http
# [dero-mcp-server] HTTP listening on 127.0.0.1:8787 (POST /mcp · GET /health)

Both stdio and HTTP serve MCP 2026-07-28 and retain compatibility with 2025-era clients. HTTP exchanges are stateless and do not issue Mcp-Session-Id; 2026 clients negotiate through server/discover.

Variable Default Description
DERO_MCP_HTTP unset Set to 1 (or pass --http) to start in HTTP mode.
DERO_MCP_HTTP_PORT 8787 Listen port.
DERO_MCP_HTTP_HOST 127.0.0.1 Listen address. Use 0.0.0.0 to bind publicly (do not without auth + TLS upstream).
DERO_MCP_AUTH_TOKEN unset If set, every /mcp request must carry Authorization: Bearer. Constant-time compared.

For a turnkey deploy with Caddy + auto-TLS + Docker Compose, see deploy/README.md. It's a self-hosting reference for running your own hosted instance. The public mcp.derod.org instance was retired on 2026-10-10; use npx dero-mcp-server or self-host. The public default daemon behind a hosted instance may use an older GetInfo schedule formula than CalcSupply; verify_supply still treats the offline schedule number as authoritative (see Verify the Supply).

The stdio transport (below) and the HTTP transport share the same underlying server factory, so the tool surface, response shapes, and error codes are identical across both.

Claude Desktop (same pattern for OpenCode and Cursor)

Add to claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/claude_desktop_config.json):```json
{
"mcpServers": {
"dero-daemon": {
"command": "node",
"args": ["/ABSOLUTE/PATH/TO/dero-mcp-server/dist/index.js"]
}
}
}


Optional: add `"env": { "DERO_DAEMON_URL": "http://127.0.0.1:10102" }` to pin a specific daemon. Not needed if your local node uses the default port — the server auto-detects it.

Restart Claude Desktop (or your OpenCode/Cursor host).

## Cursor (or OpenCode)

In **Cursor Settings → MCP** (or OpenCode MCP settings), add a server that runs the same `command` / `args` / `env` as above.

## OpenCode

In **OpenCode MCP settings**, add a server with the same `command` / `args` / `env` as above.

## Codex

Codex supports DERO MCP as either a local stdio server or a streamable-HTTP server. The stdio setup is simplest for local development because Codex launches the server process for each session.

Add the published npm package with:```bash
codex mcp add dero-daemon --env DERO_DAEMON_URL=http://127.0.0.1:10102 -- npx -y dero-mcp-server

Replace http://127.0.0.1:10102 with your daemon base URL when using a custom host or port. Do not include /json_rpc; this server appends it.

Equivalent ~/.codex/config.toml:```toml
[mcp_servers.dero-daemon]
command = "npx"
args = ["-y", "dero-mcp-server"]

[mcp_servers.dero-daemon.env]
DERO_DAEMON_URL = "http://127.0.0.1:10102"


A copyable example lives at `.codex/config.example.toml`. Rename or copy it to `.codex/config.toml` only when you want a project-scoped Codex config; Codex loads project config only for trusted projects.

For an already-running streamable-HTTP deployment, add the URL instead:```bash
codex mcp add dero-daemon --url http://127.0.0.1:8787/mcp

If the HTTP server requires a bearer token, store the token in an environment variable and add --bearer-token-env-var DERO_MCP_AUTH_TOKEN.

Restart Codex or start a new session, then run /mcp to confirm dero-daemon is enabled. A simple verification prompt is:

> "What's the current DERO chain height?"

Environment

Variable Default Description
DERO_DAEMON_URL (local-first auto-detect) Daemon base URL (no /json_rpc required). Unset → local node at 127.0.0.1:10102 if reachable, else public fallback (82.65.143.182:10102). Set to pin a specific endpoint.
DERO_DOCS_ROOT bundled index Optional dev override: path to a local dero-docs clone to index live MDX instead of the shipped bundle.

Maintainer: bundled docs

Docs tools read from data/docs-index.json, committed in this repo and shipped with the npm package. Rebuild the index when dero-docs changes:```bash
npm run release:docs-check
git add data/docs-index.json && git commit -m "Refresh bundled docs index."


Or run **Refresh docs bundle** under Actions to open a PR. Pushes to `dero-docs` `main` can trigger that workflow via `repository_dispatch` when `MCP_DOCS_SYNC_TOKEN` is configured on the docs repo.

After merging a bundle update: bump the patch version in `package.json` and `server.json`, then `npm publish --otp=...` and `mcp-publisher publish`.

## Testing```bash
# Check daemon connectivity
npm run doctor

# MCP surface contract checks (tools/resources/prompts + error probe)
npm run smoke:mcp

# Docs retrieval checks (bundled index — no clone required)
npm run smoke:docs

# Run flow tests (10 RPC checks)
npm run test:flows

# Typecheck
npm run typecheck

Flow tests run against the default public RPC. Set DERO_DAEMON_URL to test against your own daemon.

CI runs on every push and PR — see .github/workflows/ci.yml.

Official MCP Registry

Publish flow (maintainers):```bash
mcp-publisher validate
mcp-publisher login github
mcp-publisher publish


Verify listing:```bash
curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=io.github.DHEBP/dero-mcp-server"

MCP Surface

  • Tools (33): 21 daemon read/analysis primitives + 12 composites, including verify_supply (offline CalcSupply), TELA app inspection (tela_inspect, tela_get_doc_content), TELA discovery (dero_durl_to_scid, dero_tela_list_apps), and docs retrieval (dero_docs_search, dero_docs_get_page, dero_docs_list)
  • Resources (4): dero://mcp/server-info, dero://mcp/safety-boundary, dero://mcp/example-flows, dero://mcp/composites
  • Prompts (5): network_health_check, inspect_smart_contract, trace_transaction, find_dero_docs_for_intent, estimate_deploy_for_contract

Error Contract

When a tool call fails, the server returns a structured error payload in tool content:json { "ok": false, "tool": "dero_get_sc", "_meta": { "error": { "code": "RPC_UNREACHABLE", "hint": "Confirm daemon is running and reachable, then rerun `npm run doctor`.", "retryable": true, "raw": "fetch failed" } } }

Common code values:

  • INVALID_INPUT
  • RPC_INVALID_PARAMS
  • RPC_METHOD_NOT_FOUND
  • RPC_HTTP_ERROR
  • RPC_UNREACHABLE
  • RPC_INVALID_RESPONSE
  • TOOL_EXECUTION_ERROR

Roadmap

  • Optional wallet-RPC tools behind DERO_ENABLE_WALLET_RPC=1 + separate URL.
  • Stricter typing / OpenAPI-derived tool schemas.
  • TELA-aware contract tooling (INDEX/DOC inspection, on-chain app discovery).

License

MIT

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
Dero Mcp Server 怎么安装?

在客户端按下面的安装命令接入:node /ABSOLUTE/PATH/TO/dero-mcp-server/dist/index.js。装完在客户端配置里引用同一个包或端点。

Dero Mcp Server 怎么在 Claude Desktop、Claude、Cursor 里配置?

它的传输方式是stdio · 本地进程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Dero Mcp Server 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Dero Mcp Server 需要 API Key 吗?

资料标注需要会话登录认证,使用前准备好对应凭据,并按最小权限配置。

Dero Mcp Server 支持哪些客户端?

资料标注支持 Claude Desktop、Claude、Cursor、Codex、Zed;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Dero Mcp Server 能提供哪些能力?

资料显示能力标签包括 blockchain、privacy、cryptocurrency、json rpc。具体工具清单以官方文档为准。

Dero Mcp Server 需要什么运行环境?

运行时为 Cross-platform;属于本地进程,需要在本机装好运行环境。

Dero Mcp Server 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 未标注。