deficlow/zipp-mcp

> Multi-language crypto news for AI assistants — editorial summaries,
> sentiment labels (BULLISH / NEUTRAL / BEARISH), importance scores
> (0–100), and every story credited to its original publisher.
This repository hosts the **public listing manifest** and the
**zipp-mcp Python package**. The canonical Zipp MCP server is
hosted at https://zippfeed.com/mcp/ — most clients should connect
to that URL directly. The PyPI / Docker package is for the cases
where they can't: stdio-only desktop clients, locked-down networks,
or anywhere you want a self-contained install.
- 🌐 Website: zippfeed.com
- 🔌 MCP endpoint: https://zippfeed.com/mcp/
- 📡 Transport: Streamable HTTP (MCP spec 2025-06-18)
- 🔓 Auth: none — public, rate-limited at the Cloudflare edge
- 📰 Coverage: crypto / blockchain / Web3 across 8 languages
- ✍️ Editorial: every item carries sentiment + importance + source attribution
- 📦 PyPI: uvx zipp-mcp · Docker: ghcr.io/deficlow/zipp-mcp (Day 3 follow-up)
Self-host
Three install paths. All three speak the same protocol and call the
same upstream API; the right choice depends on the client.
uvx — no install, one command
For stdio MCP clients (Claude Desktop, Cursor's stdio mode, Cline,
Zed, etc.) that prefer launching a local subprocess:
Claude Desktop config (claude_desktop_config.json):
pip install — for embedded use
Or import the client directly in your own code:
Docker — for hosted / sandboxed environments
For Streamable HTTP transport on a server (Railway, Fly, Render):
Configuration
All flags read from env vars too; everything is optional.
| Env var | Default | What it does |
|------------------|------------------------|--------------|
| ZIPP_API_BASE | https://zippfeed.com | Upstream Zipp deployment (staging, mirror, etc.) |
| ZIPP_API_TIMEOUT_S | 30 | HTTP client timeout (1–120s) |
| MCP_HOST | 127.0.0.1 | Bind host for HTTP/SSE transports (set 0.0.0.0 in containers) |
| MCP_PORT | 8080 | Bind port; also aliased as PORT for Railway/Fly/Render/Heroku |
The package is read-only — there is nothing to authenticate; the
upstream API is public and rate-limited at the Cloudflare edge.
Why Zipp?
Most news connectors are pure aggregators that hand the model a raw
headline list. Zipp adds an **editorial layer** on top of the firehose:
| Signal | What it does |
|--------------------|------------------------------------------------------------------------------|
| **Sentiment** | Each story labelled BULLISH / NEUTRAL / BEARISH (editorial, not advice) |
| **Importance** | 0–100 score; ≥ 75 is the *breaking* threshold |
| **Multi-language** | 8 languages, native-quality summaries (not auto-translate) |
| **Attribution** | Original publisher name + URL on every item, always |
| **Taxonomy** | 7 categories × 5 sub-leaves = 35 leaves, stable slugs |
Quick start
Zipp speaks **Streamable HTTP** at https://zippfeed.com/mcp/ — no
auth, no install. Below are copy-paste configs for the major
MCP-capable clients, plus two ways to smoke-test the endpoint.
Claude Desktop
Add to your claude_desktop_config.json (macOS:
~/Library/Application Support/Claude/claude_desktop_config.json):
Restart Claude Desktop. You should see Zipp in the tool list and be
able to ask things like *"What's breaking in crypto right now?"* or
*"Search Zipp for Bitcoin ETF inflows in Turkish."*
Claude Code (CLI)
One-liner — registers Zipp at user scope so every project sees it:
Verify with claude mcp list.
Claude.ai web (Connectors)