zipp-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searchA | 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'. |
| get_latestA | 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?'. |
| get_breakingA | Breaking news only — last 24 hours, importance score >= 75. Lower volume than get_latest but every item is market-moving by Zipp's editorial threshold. |
| get_featuredA | Editor-picked feature stories (is_featured=TRUE). No time window. Use when the user wants curated highlights rather than the firehose. |
| get_postA | 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. |
| list_categoriesA | 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose: get_breaking for high-importance news, get_featured for curated stories, get_latest for recent news by category, get_post for full details, list_categories for taxonomy, and search for full-text queries. No overlaps.
All tools follow a verb_noun pattern with underscores (e.g., get_breaking, list_categories, search). Consistent naming makes it easy to predict tool behavior.
Six tools is an appropriate size for a news reading service. Each tool addresses a distinct retrieval need without being excessive or insufficient.
The set covers all common access patterns: breaking news, featured stories, latest by category, search, taxonomy listing, and full post details. No obvious gaps for a read-only news server.