Zipp

Zipp is the official Model Context Protocol server published by Deficlow for the crypto news feed at zippfeed.com. The official product page presents Zipp as a news and market-intelligence service for traders, investors, and builders. The official MCP page and repository identify the same hosted Streamable HTTP endpoint, https://zippfeed.com/mcp/. The official MCP Server Registry also records the product as com.zippfeed/zipp. Smithery lists the candidate as deficlow/zipp and reports a successful external deployment, while Smithery itself marks that listing as not verified and not official. The catalog decision therefore relies on the matching first-party product and repository sources rather than directory metadata.

Purpose and documented scope

According to the provider, Zipp supplies editorially summarized news about crypto, blockchain, and Web3. The MCP server exposes six documented read tools. search performs full-text search across the news catalog and orders matches by recency with relevance as a secondary signal. get_latest returns recent stories by language and optional category. get_breaking filters recent stories with high editorial importance. get_featured returns editor-curated highlights. get_post retrieves a complete post with summary, body, categories, hashtags, and source attribution. list_categories returns the feed taxonomy. The documentation names eight language variants, including English, German, French, Italian, Portuguese, Spanish, Turkish, and Russian. Sentiment values BULLISH, NEUTRAL, and BEARISH and an importance score from 0 to 100 are editorial signals, not investment advice.

Zipp is an information and research tool, not a trading or account-management service. The documented MCP operations read feed and post data. They do not create or modify accounts, publish posts, alter external platforms, subscribe to feeds, or execute trades. Any write operation would be outside this server, for example in a separate client or downstream system. Preserve that boundary in the client and require confirmation before any follow-up action.

Data provenance, freshness, and source quality

The provider source describes an editorial process involving feed selection, AI-assisted summarization, sentiment and importance scoring, and human review. Each story is intended to include the original publisher and an original URL. Attribution supports verification, but it is not a substitute for independent checking. News can be delayed, incomplete, incorrectly classified, or biased by source selection. The tools emphasize recency and published timestamps, but they do not promise a fixed freshness window or complete coverage. For claims that could affect financial decisions, inspect the original publisher, publication time, context, and later corrections.

Authorization, privacy, and access limits

According to the provider, the hosted endpoint is public and does not require an access key. Public access does not mean unlimited access or the absence of rate limits. Feed content is publicly supplied material; private accounts, private feeds, and credentials must not be placed in requests. Tool calls travel to Zipp, results return to the MCP client, and the client may then pass them to a selected model, its provider, or client and proxy logs, where they may be retained under those parties’ rules. The documented public read model does not expose Zipp account roles or private-feed permissions. Users must therefore enforce data minimization, access restrictions, and retention periods in their own client and downstream systems. Original text, names, images, and personal information in news items remain subject to copyright, privacy law, site terms, and source restrictions. The MIT license covers the source software; it does not grant blanket rights to feed content.

Security boundaries and lasting suitability

According to the provider, the public source is MIT licensed and available as a Python package and container for self-hosted read-only use. The repository is public, not archived, and contains the MCP manifest, installation documentation, and tests. The durable product name, first-party website, provider repository, official registry record, and mapped remote endpoint establish an independent product identity. News, snippets, and linked sources remain untrusted data. Prompt injection in an article must not override system rules, permissions, or external-action approvals. Zipp is suitable for the catalog as a durable research MCP server when its read-only boundary, source verification duties, model-provider data sharing, and lack of a completeness guarantee remain explicit.

MCP-capable client with Streamable HTTP support; according to the provider, the public endpoint needs no access key.

Add the official Streamable HTTP endpoint https://zippfeed.com/mcp/ to the MCP client and begin with public read-only queries.

Public and keyless according to the provider; rate limits and availability may still apply.

Read access to public news, posts, categories, and attributions; no documented account, publishing, subscription, or platform write permissions.

Requests go to Zipp; results return to the client and may be shared with model providers or logs and retained under their rules.

News and source text are untrusted data and may contain prompt injection. Review freshness, source quality, content rights, and model-provider sharing before use.