Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Keyless, read-only BNB Chain and Ethereum data: transactions by hash, tokens with a lookalike check
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://altscan.io/mcp在终端中运行这条命令
claude mcp add --transport http explorers https://altscan.io/mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"explorers": {
"url": "https://altscan.io/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"explorers": {
"type": "http",
"url": "https://altscan.io/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://altscan.io/mcp菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过域名 altscan.io 验证(注册中心会核实域名所有权)
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于–,最新版本(0.1.0)于17天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Spec Driven Development, Remote Desktop Commander, Rystic
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Start, seed, clock, inspect and diff Rystic API simulators from your agent.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Altscan
The open-source, multi-chain block explorer platform.
One codebase powers independent explorers for BNB Chain and Ethereum today — and is built to add more chains over time.
Next.js 15, Drizzle ORM, and ethers.js. Maintained by Measurable Data Token (MDT) .
altscan.io | bnbscan.com | ethscan.io | Changelog
Altscan is an open-source, multi-chain block explorer platform. One codebase powers two independent explorers today — BNBScan (bnbscan.com, BNB Chain) and EthScan (ethscan.io, Ethereum) — and is designed to extend to more chains over time. They are fully independent from BscScan, Etherscan, Binance, or the Ethereum Foundation, providing a clean, fast interface for exploring blocks, transactions, addresses, tokens, and on-chain activity.
A single CHAIN environment variable selects which chain a deployment serves — same frontend, same indexer, same schema.
| EthScan homepage, dark mode | Block |
|---|---|
| Transaction | Address |
|---|---|
| Token | Status page |
|---|---|
Captured from production on 12 October 2026, with the sponsored slots switched off.
altscan/
├── apps/ │ ├── explorer/ Unified Next.js 15 frontend + API routes │ │ CHAIN=bnb → bnbscan.com │ │ CHAIN=eth → ethscan.io │ ├── indexer/ Unified block indexer (direct polling loop) │ │ CHAIN=bnb → indexes BNB Chain │ │ CHAIN=eth → indexes Ethereum │ ├── status/ Hono status page for the hosted explorers │ │ Polls /api/health on bnbscan.com and ethscan.io │ ├── altscan-site/ altscan.io umbrella site (Astro on Cloudflare Workers) │ └── admin/ Operator console behind Cloudflare Access (Astro on Cloudflare Workers) ├── packages/ │ ├── chain-config/ getChainConfig() — chain-specific config │ ├── db/ Drizzle ORM schema + Postgres client │ ├── explorer-core/ Shared utils (rate limiting, formatting, Redis cache) │ ├── providers/ Third-party data adapters (Moralis) and their spend budgets │ ├── settings-schema/ Runtime settings shared by the explorer and the admin console │ └── types/ Shared TypeScript types ├── render.yaml Render blueprint for the hosted explorers ├── docker-compose.yml Self-host stack: Postgres, Redis, indexer, explorer ├── turbo.json Turborepo pipeline config └── pnpm-workspace.yaml
| Layer | Technology |
|---|---|
| Frontend | Next.js 15 (App Router), React 19, Tailwind CSS 3 |
| Backend | Next.js API routes, Hono (status page) |
| Database | PostgreSQL (via Drizzle ORM) |
| Indexer | ethers.js, JSON-RPC (direct polling loop, no job queue) |
| Cache | Redis (rate limiting, caching, Moralis CU ledger) |
| Edge sites | Astro on Cloudflare Workers (altscan.io, admin console) |
| Monorepo | pnpm + Turborepo |
| Hosting | Render.com (web services + workers + Postgres + Redis) |
/api/health endpoints every 30 seconds, tracking uptime, block lag, and response time over 24 hours and 30 days. Its targets are fixed in apps/status/src/server.ts, and it is not part of the Docker stack or the Render blueprint.git clone https://github.com/heathermhuang/altscan.git
cd altscan cp .env.docker.example .env docker compose up -d
Open http://localhost:3000. That's Postgres, Redis, the indexer, and the explorer — no configuration required to start, and the indexer creates its own schema on first boot. Set CHAIN=eth in .env and re-run with --build for Ethereum.
Full guide, including Render deployment, retention tuning, and limitations: [docs/SELF_HOSTING.md](docs/SELF_HOSTING.md).
package.json; corepack enable picks up the exact versionREDIS_URL, rate limits and caches fall back to per-process memory# Clone the repo
git clone https://github.com/heathermhuang/altscan.git cd altscan
pnpm install
docker compose up -d postgres
cp apps/explorer/.env.example apps/explorer/.env.local
CHAIN=bnb NEXT_PUBLIC_CHAIN=bnb pnpm --filter @altscan/explorer dev
The BNB explorer will be available at http://localhost:3000. The indexer creates the database schema on its first boot, so run it once (below) before expecting data; the explorer alone, against an empty database, has no tables to read. pnpm dev starts every app at once through Turborepo: the explorer, the indexer, the status page, and both Astro sites.
# BNB Chain explorer only
CHAIN=bnb NEXT_PUBLIC_CHAIN=bnb pnpm --filter @altscan/explorer dev
CHAIN=eth NEXT_PUBLIC_CHAIN=eth pnpm --filter @altscan/explorer dev -p 3001
pnpm --filter @altscan/db build && pnpm --filter @altscan/chain-config build && pnpm --filter @altscan/explorer-core build && pnpm --filter @altscan/providers build CHAIN=bnb pnpm --filter @altscan/indexer dev
pnpm --filter @altscan/status dev
CHAIN drives the server; NEXT_PUBLIC_CHAIN is inlined into the client bundle, so set both to the same chain. The indexer reads its settings from the environment or from apps/indexer/.env: at least DATABASE_URL (or ETH_DATABASE_URL), the chain's RPC URL, and a START_BLOCK near the chain head — its built-in start is millions of blocks back.
The explorer compiles the workspace packages from source, but the indexer loads their built dist/ output, which is not committed — build them once after cloning and again after changing them.
These are the variables a deployment needs. apps/explorer/.env.example adds the optional provider caps, and docs/SELF_HOSTING.md covers the indexer's retention and disk settings.
| Variable | Required | Description |
|---|
| CHAIN | Yes | bnb or eth — selects which
只显示了开头部分;其余内容请在仓库中阅读