Zipp
REMOTE · ZIPPFEED.COM · SCANNED SEP 24
Multi-language crypto news with editorial sentiment + importance scoring; cites original publisher.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 13 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1140 tokens (~87/item across 13 items; 13 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Zipp MCP server?
Zipp is a hosted endpoint at https://zippfeed.com/mcp/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · zippfeed.com
claude mcp add --transport http com-zippfeed-zipp 'https://zippfeed.com/mcp/'
{
"mcpServers": {
"com-zippfeed-zipp": {
"url": "https://zippfeed.com/mcp/"
}
}
} {
"servers": {
"com-zippfeed-zipp": {
"type": "http",
"url": "https://zippfeed.com/mcp/"
}
}
} [mcp_servers.com-zippfeed-zipp] url = "https://zippfeed.com/mcp/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-zippfeed-zipp": {
"type": "remote",
"url": "https://zippfeed.com/mcp/",
"enabled": true
}
}
} openclaw mcp add com-zippfeed-zipp --url 'https://zippfeed.com/mcp/' --transport streamable-http
mcp_servers:
com-zippfeed-zipp:
url: "https://zippfeed.com/mcp/" {
"McpServers": {
"com-zippfeed-zipp": {
"Transport": "http",
"Url": "https://zippfeed.com/mcp/"
}
}
} assistant mcp add com-zippfeed-zipp -t streamable-http -u 'https://zippfeed.com/mcp/'
{
"mcpServers": {
"com-zippfeed-zipp": {
"type": "http",
"url": "https://zippfeed.com/mcp/"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Aug 26 79
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 7 Aug 26 0
- The server no longer declares the “experimental” capability functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Sept 2026 · Probed https://zippfeed.com/mcp/
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=zippfeed.com | CN=YE1,O=Let's Encrypt,C=US | 19 Aug 2026 | 17 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 619a52b61a6598d7bf97bfeb324d5154b15 |
| SANs: *.zippfeed.com, zippfeed.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of zippfeed.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| zippfeed.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), microphone=(), camera=(), payment=(), usb=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://zippfeed.com/mcp/ | Verified | 200 | |
| http (plaintext) | http://zippfeed.com/mcp/ | HTTPS enforced | 301 | https://zippfeed.com/mcp/ |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_breaking ~64
Breaking news only — last 24 hours, importance score ≥ 75. Lower volume than get_latest but every item is market-moving. Use for 'what's the most important crypto news right now?'.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | – |
| limit | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_digest ~94
Full detail of a single Editor Digest — title, standfirst, full HTML body, FAQ, sentiment, and tickers. Pass the editor slug and a digest date (YYYY-MM-DD) or slug; omit the date to get that editor's latest published digest. Use get_digests to discover editors + dates.
| Name | Type | Req | Description |
|---|---|---|---|
| date_or_slug | – | – | – |
| editor_slug | string | yes | – |
| lang | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_digests ~85
List Zipp's daily Editor Digests — market briefings written by named editorial personas, each synthesising the last 24h. Newest-first. Each item carries the editor, headline, standfirst, sentiment, and tickers covered; call get_digest(editor, date) for the full body.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | – |
| limit | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_featured ~53
Editor-picked feature stories (is_featured=TRUE). No time window. Use when the user wants curated highlights rather than recency-sorted news.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | – |
| limit | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_guide ~60
Full detail of a single Zipp Learn guide by slug — title, full HTML body, FAQ pairs, related tokens, and reading time. Use get_guides to discover slugs.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | – |
| slug | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_guides ~108
List Zipp's Learn guides — evergreen, in-depth crypto explainers (what/how articles on tokens, DeFi, trading, security, wallets, regulation). Newest-first. Optionally filter by a free-text category (e.g. 'defi', 'security', 'trading'). Each item links to the full guide; call get_guide(slug) for the body + FAQ.
| Name | Type | Req | Description |
|---|---|---|---|
| category | – | – | – |
| lang | string | – | – |
| limit | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_latest ~67
Latest news from the last 24 hours. Optionally scoped to a category. Returns posts ordered newest-first. Use for 'what's new today?' or 'what happened in DeFi today?'.
| Name | Type | Req | Description |
|---|---|---|---|
| category | – | – | – |
| lang | string | – | – |
| limit | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_post ~63
Full detail of a single post — title, summary, full body, all categories, hashtags, source attribution. Accepts either a slug (from a previous tool call) or a numeric id.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | – |
| slug_or_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_rankings ~95
Live crypto market-cap rankings — the latest top-N snapshot from CoinGecko (default) or CoinMarketCap, with price, market cap, 24h change, and 24h rank movement. Answers 'what are the top coins right now?'. limit clamped to 1–100 (default 10).
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | – |
| limit | integer | – | – |
| provider | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_token_snapshot ~100
Detailed snapshot of a single token — name, ecosystem, exchange listings with deep-link trade URLs, recent Zipp coverage in the requested language, and (when available) a live price. Use when the user asks about a specific coin: 'tell me about Solana', 'where can I trade ETH?', 'what's happening with BTC?'.
| Name | Type | Req | Description |
|---|---|---|---|
| article_limit | integer | – | – |
| lang | string | – | – |
| ticker | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_trending_tokens ~93
Tokens with the most Zipp coverage in a recent time window — useful for 'what coins is the market talking about right now?' Ordered by mention count desc, then recency. Window defaults to the last 24 hours and is clamped to 1–168h (1h–7d).
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | – |
| limit | integer | – | – |
| window_hours | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_categories ~50
List the full Zipp taxonomy (7 main groups × 5 leaves = 35 categories total). Use to discover valid category slugs for the search / get_latest tools.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
search ~82
Full-text search across Zipp's news catalogue. Returns recent matching stories ordered by recency (with relevance as a tiebreaker). Use for questions like 'what's happening with Bitcoin ETFs?' or 'find news about Solana hacks'.
| Name | Type | Req | Description |
|---|---|---|---|
| category | – | – | – |
| lang | string | – | – |
| limit | integer | – | – |
| query | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
What is the Zipp MCP server?
Zipp is an MCP server listed in the public MCP registry as com.zippfeed/zipp. Multi-language crypto news with editorial sentiment + importance scoring; cites original publisher. This page covers its hosted endpoint (https://zippfeed.com/mcp/).
Is the Zipp MCP server safe to use?
Zipp scores 79 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Zipp MCP server expose?
Zipp exposes 13 tools: search, get_latest, get_breaking, get_featured, get_post, and 8 more. Their descriptions and schemas cost roughly 1,014 tokens of context every time the server is loaded.
Does the Zipp MCP server require authentication?
No. We connected to Zipp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Zipp MCP server still maintained?
Zipp is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.