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 contains the public documentation and listing manifest for Zipp's MCP server. The server itself is hosted at https://zippfeed.com/mcp/ — there is nothing to install or self-host.

• 🌐 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

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:

Quick start

Claude Desktop

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."

Claude.ai web (Connectors)

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

Cursor

~/.cursor/mcp.json:

{
  "mcpServers": {
    "zipp": {
      "url": "https://zippfeed.com/mcp/"
    }
  }
}

Smoke test

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.

Tools

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

Sample response

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.

Languages

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)

• /developer/openapi.json — REST OpenAPI 3.1 spec

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.