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.
Power your agent
Yayıncının kendi URL'si. PlugMCP uç noktası değildir.
Host a copy with our keys and logs.
https://zippfeed.com/mcp/Yukarıdaki Claude düğmesi, ad ve URL doldurulmuş olarak Claude'u açar. Onayı yine orada siz verirsiniz.
claude mcp add --transport http com.zippfeed-zipp https://zippfeed.com/mcp/Run in a terminal.
{ "mcpServers": { "com.zippfeed-zipp": { "command": "npx", "args": [ "-y", "mcp-remote", "https://zippfeed.com/mcp/" ] } }}claude_desktop_config.json
Uzak URL mi, yoksa makinenizde bir komut mu? İki kurulum arasındaki fark
PlugMCP’de çalıştır
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
BaşlatYayıncıdan
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.
Multi-language crypto news with editorial sentiment + importance scoring; cites 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.
https://zippfeed.com/mcp/2025-06-18)uvx zipp-mcp · Docker: ghcr.io/deficlow/zipp-mcp (Day 3 follow-up)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 commandFor stdio MCP clients (Claude Desktop, Cursor's stdio mode, Cline, Zed, etc.) that prefer launching a local subprocess:
uvx zipp-mcp
Claude Desktop config (claude_desktop_config.json):
{
"mcpServers": {
"zipp": {
"command": "uvx",
"args": ["zipp-mcp"]
}
}
}
pip install — for embedded usepip install zipp-mcp
zipp-mcp --transport stdio
Or import the client directly in your own code:
from zipp_mcp import ZippClient
async with ZippClient() as zipp:
payload = await zipp.search(query="bitcoin etf", lang="en-US", limit=5)
for item in payload["items"]:
print(item["title"], item["sentiment"], item["importance"])
docker run -i --rm ghcr.io/deficlow/zipp-mcp
For Streamable HTTP transport on a server (Railway, Fly, Render):
docker run -p 8080:8080 -e MCP_HOST=0.0.0.0 \
ghcr.io/deficlow/zipp-mcp \
zipp-mcp --transport http
All flags read from env vars too; everything is optional.
The package is read-only — there is nothing to authenticate; the upstream API is public and rate-limited at the Cloudflare edge.
Most news connectors are pure aggregators that hand the model a raw headline list. Zipp adds an editorial layer on top of the firehose:
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.
Add to your claude_desktop_config.json (macOS:
~/Library/Application Support/Claude/claude_desktop_config.json):
{
"mcpServers": {
"zipp": {
"type": "http",
"url": "https://zippfeed.com/mcp/"
}
}
}
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."
One-liner — registers Zipp at user scope so every project sees it:
claude mcp add --scope user --transport http zipp https://zippfeed.com/mcp/
Verify with claude mcp list.
Settings → Connectors → Add custom connector →
URL: https://zippfeed.com/mcp/ → no authentication.
Settings → Connectors → Add → Custom connector →
URL: https://zippfeed.com/mcp/ → Authentication: None.
~/.cursor/mcp.json:
{
"mcpServers": {
"zipp": {
"url": "https://zippfeed.com/mcp/"
}
}
}
~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"zipp": {
"serverUrl": "https://zippfeed.com/mcp/"
}
}
}
Open the Cline panel → MCP Servers → Edit Configuration, then
add Zipp to cline_mcp_settings.json:
{
"mcpServers": {
"zipp": {
"url": "https://zippfeed.com/mcp/",
"type": "streamableHttp"
}
}
}
~/.config/zed/settings.json — Zed's context_servers interface is
stdio-only today, so use the mcp-remote
bridge:
{
"context_servers": {
"zipp": {
"command": {
"path": "npx",
"args": ["-y", "mcp-remote", "https://zippfeed.com/mcp/"]
}
}
}
}
~/.gemini/settings.json:
{
"mcpServers": {
"zipp": {
"httpUrl": "https://zippfeed.com/mcp/"
}
}
}
from openai import OpenAI
client = OpenAI()
resp = client.responses.create(
model="gpt-5",
tools=[{
"type": "mcp",
"server_label": "zipp",
"server_url": "https://zippfeed.com/mcp/",
"require_approval": "never",
}],
input="What's breaking in crypto right now? Cite the original publisher.",
)
print(resp.output_text)
The MCP connector is a beta — pass the header below until it goes GA:
import anthropic
client = anthropic.Anthropic()
msg = client.messages.create(
model="claude-opus-4-7",
max_tokens=1024,
mcp_servers=[{
"type": "url",
"url": "https://zippfeed.com/mcp/",
"name": "zipp",
}],
messages=[{"role": "user", "content": "What's breaking in crypto right now?"}],
extra_headers={"anthropic-beta": "mcp-client-2025-04-04"},
)
print(msg.content)
Verify the server from your shell — no client needed:
curl -s -X POST "https://zippfeed.com/mcp/" \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"smoke","version":"1.0"}}}'
Expected: a JSON-RPC initialize result where serverInfo.name = "Zipp"
and the server advertises tools, resources, and prompts capabilities.
For an interactive UI, run the official MCP Inspector:
npx @modelcontextprotocol/inspector
In the browser tab that opens, pick Streamable HTTP as the
transport, paste https://zippfeed.com/mcp/, click Connect, then
browse the Tools / Resources / Prompts tabs to exercise the
server end-to-end.
lang defaults to en-US. See Languages below for the full list.
get_latest(lang="en-US", limit=1) returns shape:
{
"items": [
{
"id": 1234,
"slug": "bitcoin-etf-inflows-500m",
"url": "https://zippfeed.com/en-US/a/bitcoin-etf-inflows-500m",
"title": "Bitcoin ETF inflows hit $500M",
"summary": "Spot Bitcoin ETFs absorbed $500M in net inflows…",
"category": "markets-etfs",
"sentiment": "BULLISH",
"importance": 82,
"published_at": "2026-05-13T15:08:55Z",
"language": "en-US",
"tags": ["markets-etfs", "btc", "etf"],
"source": {
"name": "CoinDesk",
"url": "https://www.coindesk.com/..."
},
"image_url": "https://cdn.zippfeed.com/images/rss/abc.jpg"
}
]
}
get_post additionally returns the full body, hashtags, and an
expanded categories[] array.
Every story is editorially summarised in every supported language; sentiment and importance scoring are computed once and shared across language variants.
Every Zipp story carries the original publisher in the source field.
When you surface Zipp content in an AI response, please credit both
Zipp and the original publisher, e.g.:
via Zipp — original: CoinDesk
Linking to the original source.url is encouraged. Zipp's own
canonical URL (item.url) is the right link when pointing to the
editorial summary.
Zipp's editorial process — feed selection, AI-assisted summarisation, sentiment + importance scoring, human review — is documented at zippfeed.com/en-US/p/methodology.
Sentiment is editorial labelling, not investment advice.
Zipp is published to the official MCP Server Registry as
com.zippfeed/zipp —
directories that aggregate the registry (Smithery, Glama, mcp.so,
PulseMCP, etc.) pick it up automatically.
If you're building tooling around Zipp, the following endpoints are also public:
/llms.txt — AI-discoverable URL map/sitemap.xml, /news_sitemap.xml, /image_sitemap.xml/rss.xml + /feed.json (per-language + per-category + per-slice variants)The standalone developer REST API was retired on 2026-05-14 — GET /developer/v1/* now returns 410 Gone with a pointer to the MCP endpoint. AI-agent integrations should use MCP; long-form content readers should use the RSS or JSON Feed surfaces above.
[email protected]This repository — README, manifest, and the example client — is released under the MIT License. It covers the public documentation and listing manifest only; the MCP server implementation itself is proprietary and hosted by Zipp.
Multi-language crypto news with editorial sentiment + importance scoring; cites original publisher.
{ "mcpServers": { "com.zippfeed-zipp": { "url": "https://zippfeed.com/mcp/", "headers": {} } }}Araçlar
Henüz araç listesi yok. Uzak sunucular ilk sağlık kontrolünden sonra bir liste alır.
SSS
Bu sayfadan Cursor, Claude Desktop, Claude Code veya VS Code için http yapılandırmasını kopyalayın. PlugMCP proxy'sini değil, yayıncının kurulumunu kullanır.
Bu kayıtta gerekli bir ortam değişkeni listelenmiyor.
Zipp sunucusuna HTTP üzerinden ulaşılır.
Son kontrol: 2026-11-08. Multi-language crypto news with editorial sentiment + importance scoring; cites original publisher.