opennews-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENNEWS_TOKEN | Yes | 6551 API Bearer Token (from https://6551.io/mcp). Required. | |
| OPENNEWS_WSS_URL | No | Override WebSocket URL. Optional. | |
| OPENNEWS_API_BASE | No | Override REST API URL. Optional. | |
| OPENNEWS_MAX_ROWS | No | Max results per request (default 100). Optional. |
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 |
|---|---|
| get_news_sourcesA | Get all available news source categories and their metadata. Returns a tree structure with engine types (news, listing, onchain, meme, market) and their sub-categories (Bloomberg, Reuters, Binance, etc.). Use this first to understand what news sources are available before searching. |
| list_news_typesA | List all available news type codes for filtering. |
| get_latest_newsA | Get the most recent crypto news articles, newest first. |
| search_newsA | Search crypto news by keyword in text content. |
| search_news_by_coinB | Search news related to a specific cryptocurrency coin/token. |
| get_news_by_sourceA | Get news articles from a specific source. |
| get_news_by_engineA | Get news articles filtered by engine type. |
| search_news_advancedA | Advanced news search with multiple filters. |
| get_high_score_newsA | Get highly-rated news articles (by AI score), sorted by score descending. |
| get_news_by_signalA | Get news filtered by trading signal type. |
| subscribe_latest_newsA | Subscribe to real-time news updates via WebSocket. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| knowledge_guide | Usage guide — tool workflows, search strategies, best practices. |
TDQS
Scored across 11 tools
Most tools have distinct retrieval intents—search by keyword, coin, source, engine, score, signal, or real-time—so an agent can usually pick correctly. The main overlap is between get_news_sources and list_news_types, and between the basic search tools and search_news_advanced, which can cause occasional misselection.
Tool names mostly follow a snake_case verb_noun pattern (get_news_by_*, search_news_*, list_news_types). Minor deviations exist between search_ vs get_ prefixes for similar retrieval operations, and subscribe_latest_news places the modifier before the object, but the overall pattern remains readable.
With 11 tools, the server is well within the ideal range for a specialized news API. The count feels appropriate: discovery, search, filtering, and real-time subscription each have dedicated tools without being bloated.
The toolset covers the full news workflow: discovering sources, listing filter codes, retrieving latest news, searching by multiple dimensions, filtering by rating/signal, and subscribing via WebSocket. No critical dead ends are apparent for the stated crypto-news domain.