Zipp MCP Server

Multi-language crypto news with editorial sentiment + importance scoring; cites original publisher.

Remote serverstreamable-httpPython

What is the Zipp MCP server?

Zipp MCP server exists for a simple reason — assistants are far more useful when they can act on Zipp directly instead of describing what you should do. Multi-language crypto news with editorial sentiment + importance scoring; cites original publisher.

What you get

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.

What the assistant can call

Once Zipp is connected, these are the calls the assistant has available:

  • search — (query, lang?, category?, limit?)
  • get_latest — (lang?, category?, limit?)
  • get_breaking — (lang?, limit?)
  • get_featured — (lang?, limit?)
  • get_post — (slug_or_id, lang?)
  • list_categories — (lang?)
  • Configuration — The package is read-only — there is nothing to authenticate; the upstream API is public and rate-limited at the Cloudflare edge
  • Cursor — The Cursor tool exposed by this server
  • Windsurf — The Windsurf tool exposed by this server

Setting it up

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Choosing this one

Plenty of cloud and infrastructure servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Zipp's toolset — search, get_latest, get_breaking and 6 more — is a fair guide to whether it matches your workflow. It is maintained by com.zippfeed; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Before you rely on it

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • With 9 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Zipp.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the zipp mcp server does with a few real requests.

Available tools

ToolWhat it does
search(query, lang?, category?, limit?)
get_latest(lang?, category?, limit?)
get_breaking(lang?, limit?)
get_featured(lang?, limit?)
get_post(slug_or_id, lang?)
list_categories(lang?)
ConfigurationThe package is read-only — there is nothing to authenticate; the upstream API is public and rate-limited at the Cloudflare edge.
CursorThe Cursor tool exposed by this server.
WindsurfThe Windsurf tool exposed by this server.

How to install the Zipp MCP server

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

Configuration as documented by the project. Restart the client after saving.

Example prompts to try

  • Use Zipp to search.
  • Use Zipp to get latest.
  • Use Zipp to get breaking.

Frequently asked questions

It connects Zipp to MCP-compatible AI assistants such as Claude and Cursor, exposing 9 tools (search, get_latest, get_breaking, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Zipp directly.