mcp-registry/com.zippfeed/zipp · v1.28.1
Also listed as awesome/deficlow/zipp-mcp
As of 2026-10-22 14:40 UTC, the Zippfeed Zipp MCP server is up with a Glimind reliability score of 93/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 5 minutes.
Multi-language crypto news with editorial sentiment + importance scoring; cites original publisher.
Claude Code
claude mcp add --transport http zippfeed-zipp-mcp-server https://zippfeed.com/mcp/
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"zippfeed-zipp-mcp-server": {
"type": "http",
"url": "https://zippfeed.com/mcp/"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
33 parameter(s) across 13 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
13 of 13 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
Handshake + tools/list takes ~1,509 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 13 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.zippfeed%2Fzipp/fixes
{
"name": "get_breaking",
"description": "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?'.",
"inputSchema": {
"type": "object",
"title": "get_breaking_toolArguments",
"properties": {
"lang": {
"type": "string",
"title": "Lang",
"default": "en-US"
},
"limit": {
"type": "integer",
"title": "Limit",
"default": 10
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_digest",
"description": "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.",
"inputSchema": {
"type": "object",
"title": "get_digest_toolArguments",
"required": [
"editor_slug"
],
"properties": {
"lang": {
"type": "string",
"title": "Lang",
"default": "en-US"
},
"editor_slug": {
"type": "string",
"title": "Editor Slug"
},
"date_or_slug": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"title": "Date Or Slug",
"default": null
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_digests",
"description": "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.",
"inputSchema": {
"type": "object",
"title": "get_digests_toolArguments",
"properties": {
"lang": {
"type": "string",
"title": "Lang",
"default": "en-US"
},
"limit": {
"type": "integer",
"title": "Limit",
"default": 10
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.zippfeed/zipp"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.zippfeed/zipp"}) over MCP.
get_token_snapshot ~178 tokensget_guides ~177 tokensget_digest ~175 tokenssearch ~169 tokensget_trending_tokens ~156 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.zippfeed%2Fzipp?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.zippfeed%2Fzipp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.zippfeed%2Fzipp.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.zippfeed%2Fzipp.svg :target: https://glimind.com/server/mcp-registry%2Fcom.zippfeed%2Fzipp?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:9a4b6cafb8184fe6…, first seen 2026-10-17, included at leaf 10394 of 46,493. Version history · verify what your client received.
Compare: most reliable news servers · most reliable retrieval servers · most reliable knowledge servers · most reliable finance servers · most reliable data servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-22 14:40 UTC, the Zippfeed Zipp MCP server is up with a Glimind reliability score of 93/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 5 minutes.
Zippfeed Zipp MCP server advertises 13 tools, including get_breaking, get_digest, get_digests, get_featured, get_guide.
Point your MCP client at this streamable-http endpoint: https://zippfeed.com/mcp/
Glimind scanned all 13 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.