SuperAPI AI Directory
Partner with us中文AI newsFavorites
All toolsAI developer platformszipp-mcp

zipp-mcp

Multi-language crypto news summaries with sentiment labels and importance scores, crediting the original publisher.

Open website

About this tool

Purpose

Zipp MCP is a multilingual cryptocurrency news MCP server for AI assistants. Unlike ordinary news connectors that simply hand a raw list of headlines to the model, Zipp adds a layer of editorial processing on top of the feed: each item carries a sentiment label (BULLISH / NEUTRAL / BEARISH), an importance score (0–100), and attribution to the original publishing source. It covers the cryptocurrency / blockchain / Web3 space and supports 8 languages.

Main capabilities

  • Multilingual coverage: crypto / blockchain / Web3 news across 8 languages.
  • Editorial summaries: each news item has an editorial summary in every supported language; sentiment and importance scores are computed only once and shared across language versions.
  • Attribute fields: each Zipp news item carries the original publisher in the source field; item.url is the canonical link to the Zipp editorial summary, and source.url points to the original source.
  • Protocol and access: Streamable HTTP (MCP specification 2025-06-18), no authentication required, public and rate-limited at the Cloudflare edge.
  • Read-only: the package is read-only and requires no authentication.

How to use

The official hosted endpoint is https://zippfeed.com/mcp/, and most clients should connect directly to that URL. For cases where a direct connection is not possible (stdio-only desktop clients, restricted networks, or environments that want a self-contained installation), the PyPI package or Docker image can be used. All three installation paths use the same protocol and call the same upstream API; the choice depends on the client type.

The official documentation provides the following client configuration examples:

  • uvx (no installation, one command): suitable for stdio MCP clients that prefer to launch a local subprocess (Claude Desktop, Cursor's stdio mode, Cline, Zed, etc.).
  • Claude Desktop: configure in claude_desktop_config.json .
  • Claude Code (CLI): one command registers Zipp in the user scope, making it visible to all projects; you can 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。
  • Windsurf：~/.codeium/windsurf/mcp_config.json.
  • Cline (VS Code extension): open the Cline panel → MCP Servers → Edit Configuration, and add Zipp to cline_mcp_settings.json。
  • Zed：~/.config/zed/settings.json; Zed's context_servers interface currently supports only stdio, so use the mcp-remote bridge.
  • Gemini:~/.gemini/settings.json.
  • OpenAI Responses API and Anthropic Messages API: the MCP connector is in beta and requires passing the specified header until GA.

How to self-test: you can verify the server in a shell without a client; it is expected to return a JSON-RPC initialize result in which serverInfo.name = "Zipp", and the server declares tools, resources, and prompts capabilities. You can also run the official MCP Inspector, select Streamable HTTP as the transport in the browser, paste https://zippfeed.com/mcp/, click Connect, and then browse the Tools / Resources / Prompts tabs to test end to end.

Language parameter:lang defaults to en-US.

Example response:get_latest(lang="en-US", limit=1) returns the corresponding structure;get_post additionally returns the full body, hashtags, and the expanded categories[] array.

Attribution policy

Each Zipp news item carries the original publisher in the source field. When presenting Zipp content in AI responses, both Zipp and the original publisher should be credited, for example:via Zipp — original: CoinDesk. Encourages linking to the original source source.url; when pointing to an editorial summary, Zipp's canonical URL (item.url) should be used.

Applicable Scenarios

Suitable for developers and users who want to connect AI assistants to multilingual cryptocurrency news with sentiment and importance scores, for example asking "What's the breaking crypto news right now?" or "Search Zipp for Bitcoin ETF inflows in Turkish" in MCP-supporting clients such as Claude, ChatGPT, Cursor, Cline, Zed, and Gemini.

Limitations and Notes

  • Sentiment is an editorial label, not investment advice.
  • The upstream API is public and rate-limited at the Cloudflare edge.
  • The standalone developer REST API was discontinued on 2026-05-14 —— GET /developer/v1/* it now returns 410 Gone and points to the MCP endpoint; AI agent integrations should use MCP, and long-form content readers should use RSS or JSON Feed.
  • This repository (README, manifest, and example clients) is released under the MIT license and covers only public documentation and the listing manifest; the MCP server implementation itself is proprietary and hosted by Zipp.
  • The editorial methodology (feed selection, AI-assisted summaries, sentiment + importance scoring, human review) is documented at zippfeed.com/en-US/p/methodology.

Other Public Discovery Entry Points

Zipp has been published to the official MCP Server Registry (com.zippfeed/zipp), and directories that aggregate this registry (Smithery, Glama, mcp.so, PulseMCP, etc.) will automatically include it. Public endpoints available when building related tools include /llms.txt、/sitemap.xml、/news_sitemap.xml、/image_sitemap.xml、/rss.xml + /feed.json(offering variants by language, category, and slice). Contact email: hello@zippfeed.com.

Related tools

Browse category