Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Live spot crypto ETF flows for 16 assets and their funds, CEFI index and prices.
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://mcp.cryptoetf.today/api/mcpOpen Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"cryptoetf": {
"command": "npx",
"args": [
"-y",
"@zerosix-studio/cryptoetf-mcp"
]
}
}
}Run this in your terminal
claude mcp add --transport http cryptoetf https://mcp.cryptoetf.today/api/mcpclaude mcp add cryptoetf -- npx -y @zerosix-studio/cryptoetf-mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"cryptoetf": {
"url": "https://mcp.cryptoetf.today/api/mcp"
}
}
}Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"cryptoetf": {
"command": "npx",
"args": [
"-y",
"@zerosix-studio/cryptoetf-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": {
"cryptoetf": {
"type": "http",
"url": "https://mcp.cryptoetf.today/api/mcp"
}
}
}Paste into .vscode/mcp.json in your project
{
"servers": {
"cryptoetf": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@zerosix-studio/cryptoetf-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://mcp.cryptoetf.today/api/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 7, 2026
The publisher (sly13) is not the repo owner (zerosix-studio); someone else may have listed it
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 0 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.
Either way works: install it on your computer or connect to the cloud version.
The GitHub repo last changed –, and the latest version (1.0.12) reached the registry 22 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, AvaHR
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.
Read hiring data and create inactive assessment and questionnaire drafts for human review.
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.
The Model Context Protocol surface of cryptoetf.today: daily net flows for every US-listed spot crypto ETF complex and every fund in it, fund AUM, the CEFI sentiment index and live coin prices — for Claude, Cursor, Codex, Gemini CLI and any other MCP-capable agent.
Sixteen assets: BTC, ETH, SOL, XRP, HYPE, DOGE, LINK, AVAX, HBAR, LTC, BNB, DOT, SUI, NEAR, TRX, ZEC. Flow figures are net USD millions, sourced from the issuers' own daily reports; for the eleven smaller complexes there is no market-wide aggregator, so the numbers are computed from each issuer's fund pages.
You probably don't need to install anything. The server is hosted, and every client that speaks remote MCP can reach it directly:
https://mcp.cryptoetf.today/api/mcp Streamable HTTP · JSON-RPC 2.0
No API key, no account — the endpoint is open.
Claude Code — one command, no restart:
claude mcp add --transport http cryptoetf https://mcp.cryptoetf.today/api/mcp
Cursor — .cursor/mcp.json (project) or ~/.cursor/mcp.json (global):
{
"mcpServers": { "cryptoetf": { "url": "https://mcp.cryptoetf.today/api/mcp" } } }
Claude Desktop and other stdio-only clients — this package is the bridge. claude_desktop_config.json, then restart the app fully:
{
"mcpServers": { "cryptoetf": { "command": "npx", "args": ["-y", "@zerosix-studio/cryptoetf-mcp"] } } }
Nothing to install by hand: npx fetches the package on first run. It has zero dependencies and simply forwards JSON-RPC between stdin/stdout and the hosted endpoint.
| Tool | What it returns |
|---|---|
get_flows_summary | Latest-day net flow for all 16 assets, with the date each figure belongs to |
get_asset_flows | Daily net flow history for one asset over the last 30 days |
get_fund_flows | The same 30 days for one asset, fund by fund (IBIT, FBTC, ETHA…), with ticker and issuer |
get_funds | Fund directory: issuer, fee, listing date, current net assets (AUM) and coins held |
get_weekly_analytics | 7-day totals per asset: net flow, average day, positive/negative day counts |
get_cefi_index | Composite CEFI index (0–100, 50 = zero net flow) with its flow, trend and breadth components |
get_prices | Spot price and 24h change for every tracked asset |
History reaches back 30 days, in the tools and in the REST API alike. Longer history is on cryptoetf.today.
| Variable | Default | Purpose |
|---|---|---|
CRYPTOETF_MCP_URL | https://mcp.cryptoetf.today/api/mcp | Point the bridge at another endpoint |
CRYPTOETF_API_KEY | — | Sent as Authorization: Bearer … when set; the public endpoint does not need it |
Requires Node.js 18 or newer.
Flow data is updated every business day as issuers publish. Figures are informational — this is market data, not investment advice.
Full policy: cryptoetf.today/en/privacy.
What is collected. The bridge forwards your JSON-RPC requests to https://mcp.cryptoetf.today/api/mcp and returns the responses. The only request data that leaves your machine is the tool name and its arguments (an asset ticker, at most). Conversation content, files and credentials are never read or transmitted.
How it is used and stored. The server logs the standard request metadata of any web service — IP address, timestamp, endpoint — and keeps a per-IP counter in Redis to enforce the 60 requests/minute rate limit. Logs are retained for 30 days and are used only to operate and protect the service.
Third-party sharing. None. Request data is not sold, shared or passed to any third party. The service is operated by us and calls only our own API.
Retention. Rate-limit counters expire within a minute; request logs within 30 days. No user accounts and no personal profiles exist — the endpoint is open and unauthenticated.
Contact. github.com/zerosix-studio/cryptoetf-mcp/issues or the contact form at cryptoetf.today.
Bump the version in package.json, then tag the commit:
git tag v1.0.4 && git push --tags
The Publish to npm workflow runs the bridge against the live server, skips the publish if that version is already in the registry, and otherwise pushes it with provenance — the npm page then links back to the exact workflow run and commit the tarball was built from.
MIT licensed.