zipp MCP

MCP金融服务

提供方 deficlow

金融服务 未标注 无需鉴权 社区 / 第三方

Multi-language crypto news MCP server with editorial summaries, sentiment labels (BULLISH/NEUTRAL/BEARISH), and importance scores (0–100). 6 tools across 8 languages; every story credits the original publisher. Bridges stdio to the public Streamable HTTP endpoint at https://zippfeed.com/mcp/.

一句话选型结论

按资料字段整理

zipp MCP 属于金融服务类 MCP 服务器,传输方式未标注,无需鉴权,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类金融服务 传输方式未标注 鉴权无需鉴权 部署方式支持远程部署
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

金融服务
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

安装与配置

未标注 无需鉴权
上游未给出传输方式
  1. 1
    准备运行环境

    确认你的客户端支持远程端点,并拿到服务地址。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
行情与财务数据

查行情、财报、汇率等金融数据。

支付与账务查询

查订单、账单与交易流水。

风控与核验

做身份、信用与风险信息核验。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 资料标注无需鉴权,装好就能连。

先想清楚的地方

  • 远程端点依赖网络与服务方可用性,注意密钥与调用额度。
  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在金融服务场景里让模型直接调用外部能力的人。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
zipp MCP当前 未标注 未标注 支持远程部署 无 2026-05-17
Alpaca MCP 62 stdio · 本地进程 支持远程部署 有 2026-05-18
OpenNews MCP 11 stdio · 本地进程 支持远程部署 有 2026-05-17
MCP Server 273df76d 未标注 stdio · 本地进程 本地部署 有 2026-05-17
tradingview-mcp 未标注 stdio · 本地进程 本地部署 有 2026-04-19
goat (Goat SDK) 未标注 未标注 未标注 无 2026-05-17

服务器档案

金融服务
字段来自项目仓库与公开索引,中文说明由本站标注
提供方deficlow上游标注的维护方 deficlow
分类金融服务本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式无需鉴权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型支持远程部署上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

11.5 KB
来自项目仓库与上游目录的原文,未做删改

Zipp MCP

> 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:```bash
uvx zipp-mcp


Claude Desktop config (`claude_desktop_config.json`):```json
{
  "mcpServers": {
    "zipp": {
      "command": "uvx",
      "args": ["zipp-mcp"]
    }
  }
}

pip install — for embedded use```bash

pip install zipp-mcp
zipp-mcp --transport stdio


Or import the client directly in your own code:```python
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 — for hosted / sandboxed environments```bash

docker run -i --rm ghcr.io/deficlow/zipp-mcp


For Streamable HTTP transport on a server (Railway, Fly, Render):```bash
docker run -p 8080:8080 -e MCP_HOST=0.0.0.0 \
  ghcr.io/deficlow/zipp-mcp \
  zipp-mcp --transport http

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
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):```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."*

### Claude Code (CLI)

One-liner — registers Zipp at user scope so every project sees it:```bash
claude mcp add --scope user --transport http zipp https://zippfeed.com/mcp/

Verify with claude mcp list.

Claude.ai web (Connectors)

Settings → Connectors → Add custom connector →
URL: https://zippfeed.com/mcp/ → no authentication.

ChatGPT (Custom Connectors)

Settings → Connectors → Add → Custom connector →
URL: https://zippfeed.com/mcp/ → Authentication: None.

Cursor

~/.cursor/mcp.json:```json
{
"mcpServers": {
"zipp": {
"url": "https://zippfeed.com/mcp/"
}
}
}


### Windsurf

`~/.codeium/windsurf/mcp_config.json`:```json
{
  "mcpServers": {
    "zipp": {
      "serverUrl": "https://zippfeed.com/mcp/"
    }
  }
}

Cline (VS Code extension)

Open the Cline panel → MCP Servers → Edit Configuration, then
add Zipp to cline_mcp_settings.json:```json
{
"mcpServers": {
"zipp": {
"url": "https://zippfeed.com/mcp/",
"type": "streamableHttp"
}
}
}


### Zed

`~/.config/zed/settings.json` — Zed's `context_servers` interface is
stdio-only today, so use the `mcp-remote`
bridge:```json
{
  "context_servers": {
    "zipp": {
      "command": {
        "path": "npx",
        "args": ["-y", "mcp-remote", "https://zippfeed.com/mcp/"]
      }
    }
  }
}

Gemini CLI

~/.gemini/settings.json:```json
{
"mcpServers": {
"zipp": {
"httpUrl": "https://zippfeed.com/mcp/"
}
}
}


### OpenAI Responses API```python
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)

Anthropic Messages API

The MCP connector is a beta — pass the header below until it goes GA:```python
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)


### Smoke test

Verify the server from your shell — no client needed:```bash
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:```bash
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.

## Tools

| Tool              | Signature                                                  | What it returns                                  |
|-------------------|------------------------------------------------------------|--------------------------------------------------|
| `search`          | `(query, lang?, category?, limit?)`                        | Full-text search, recency-first                  |
| `get_latest`      | `(lang?, category?, limit?)`                               | Stories from the last 24 hours                   |
| `get_breaking`    | `(lang?, limit?)`                                          | Importance ≥ 75 within the last 24 hours         |
| `get_featured`    | `(lang?, limit?)`                                          | Editor-curated highlights                        |
| `get_post`        | `(slug_or_id, lang?)`                                      | Full post body + all categories + hashtags       |
| `list_categories` | `(lang?)`                                                  | The 7 × 5 taxonomy (35 leaves)                   |

`lang` defaults to `en-US`. See Languages below for the full list.

### Sample response

`get_latest(lang="en-US", limit=1)` returns shape:```json
{
  "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.

Languages

Code Language
en-US English
tr-TR Türkçe
es-ES Español
ru-RU Русский
pt-PT Português
fr-FR Français
de-DE Deutsch
it-IT Italiano

Every story is editorially summarised in every supported language;
sentiment and importance scoring are computed once and shared across
language variants.

Attribution policy

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.

Editorial methodology

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.

Related discovery surfaces

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.

Legal

  • Methodology
  • Privacy
  • Terms
  • Contact: hello@zippfeed.com

License

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.

常见问题

7 问
答案由本站依据条目字段整理,不引用上游原文
zipp MCP 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

zipp MCP 怎么在客户端里配置?

它的传输方式未标注,在客户端 MCP 配置里按官方文档填写启动命令和参数,保存后重启客户端生效。

zipp MCP 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

zipp MCP 需要 API Key 吗?

资料标注为无需认证,装好就能连;如果实际调用时报鉴权错误,按官方文档补上凭据。

zipp MCP 能提供哪些能力?

资料显示能力标签包括 金融数据、数据分析、API集成。具体工具清单以官方文档为准。

zipp MCP 需要什么运行环境?

属于远程端点,不需要在本地装运行时。

zipp MCP 是本地还是远程?

它是远程端点,连服务地址即可。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-17。