Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Keyless, read-only BNB Chain and Ethereum data: transactions by hash, tokens with a lookalike check
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://altscan.io/mcpRun this in your terminal
claude mcp add --transport http explorers https://altscan.io/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"explorers": {
"url": "https://altscan.io/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"explorers": {
"type": "http",
"url": "https://altscan.io/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://altscan.io/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified against the domain altscan.io (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (0.1.0) reached the registry 16 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, zanadir
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
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.
Find what a repository's CI is missing, and which security checks cannot fail the build.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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
Only the beginning is shown; read the rest in the repo