APITube News
REMOTE · MCP.APITUBE.IO · SCANNED AUG 16
Real-time news search across 500,000+ sources in 60+ languages with sentiment and entities.
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 →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability69
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 4442 tokens (~2221/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage91
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 73% of tool parameters carry a description.Partial
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · mcp.apitube.io
claude mcp add --transport http io-apitube-news https://mcp.apitube.io/
[mcp_servers.io-apitube-news] url = "https://mcp.apitube.io/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-apitube-news": {
"type": "remote",
"url": "https://mcp.apitube.io/",
"enabled": true
}
}
} openclaw mcp add io-apitube-news --url https://mcp.apitube.io/ --transport streamable-http
mcp_servers:
io-apitube-news:
url: "https://mcp.apitube.io/" {
"mcpServers": {
"io-apitube-news": {
"type": "http",
"url": "https://mcp.apitube.io/"
}
}
} 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.
- 16 Aug 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “search_news” rewrote its description, which is the text the model reads security
- Stability: unverified → 0.03 ▲ functional
- “search_news” reworded the description of “per_page” cosmetic
- 15 Aug 26 71
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 16 Aug 2026 · Probed https://mcp.apitube.io/
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=apitube.io | CN=WE1,O=Google Trust Services,C=US | 10 Aug 2026 | 8 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | a7f787e50e41121b0e2f27385f572d7d |
| SANs: apitube.io, *.apitube.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
DNSSEC insecure
Validation of mcp.apitube.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| apitube.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.apitube.io/ | Verified | 200 | |
| http (plaintext) | http://mcp.apitube.io/ | HTTPS enforced | 301 | https://mcp.apitube.io/ |
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.
search_news News Search ~3,495
Search news articles using APITube News API with comprehensive filtering. IMPORTANT INSTRUCTIONS FOR QUERY CONSTRUCTION: 1. DO NOT use dots in parameter names directly in the root object. Use nested objects instead. 2. The system will automatically convert nested objects to dot notation for the API. Example: Use { language: { code: "en" } } instead of { "language.code": "en" }. 3. For multiple values in one parameter, use COMMA separation (e.g., "en,ru,fr" for multiple languages). 4. Integer filters (has_*, is_*) accept ONLY 0 or 1 (e.g., has_image=1, is_duplicate=0). 5. Date format: ISO 8601 (YYYY-MM-DD or YYYY-MM-DDTHH:MM:SSZ). 6. Sentiment scores range: -1.0 (negative) to 1.0 (positive). 7. Default sorting: published_at DESC (newest first). 8. Unknown parameters are rejected with an error (-32602) instead of being silently ignored — check the spelling against the list below. 9. By default the response returns id, title, href, published_at, description and source.domain. The article body is NOT included — request it explicitly with fl (e.g. fl: "title,href,body"). AVAILABLE PARAMETERS: ### Content Search - title: Search by article title (supports up to 3 keywords with comma separation) IMPORTANT: a title search covers at most a 31-day published_at window. Omit the dates and the last 31 days are searched; pass a range wider than 31 days and the call fails with 400 ER0110. To cover a longer period, make one call per month-sized window. - ignore: { title: "keyword" } - Exclude articles with specific titles ### Languages (60+ supported) - language: { code: "en,ru,fr" } - Filter by language codes (up to 3) - ignore: { language: { code: "fr" } } - Exclude specific languages ### Categories (IPTC taxonomy) - category: { id: "medtop:04000000" } - Filter by category ID (up to 3) - ignore: { category: { id: "315" } } - Exclude categories ### Topics - topic: { id: "crypto_news,climate_change" } - Filter by topic ID (up to 3) - ignore: { topic: { id: "2"…
| Name | Type | Req | Description |
|---|---|---|---|
| author | object | – | – |
| brand | object | – | – |
| category | object | – | IPTC category filter. |
| disaster | object | – | – |
| disease | object | – | – |
| entity | object | – | Named-entity filter. |
| event | object | – | – |
| facet | boolean|object | – | Enable faceting (true) or object form for analytics. |
| fl | string | – | Comma-separated fields to return (dot-notation supported), e.g. "id,title,source.name,sentiment.overall.score". |
| has_author | integer | – | Has an attributed author. |
| has_hq_images | integer | – | High-quality images (width >= 1200px). |
| has_image | integer | – | Articles with at least one image. |
| has_video | integer | – | Articles with at least one video. |
| hl | boolean|object | – | Enable highlighting (true) or object form. |
| ignore | object | – | Exclusion filters — exclude articles matching these. Mirror the positive filters. |
| industry | object | – | – |
| is_breaking | integer | – | Breaking news only. |
| is_duplicate | integer | – | 0 to exclude duplicates. |
| is_long_read | integer | – | Read time >= 5 minutes. |
| is_media_rich | integer | – | Both images and videos. |
| is_paywall | integer | – | 0 to exclude paywalled content. |
| is_premium_source | integer | – | Premium sources (OPR >= 6). |
| is_short_read | integer | – | Read time < 3 minutes. |
| is_verified_source | integer | – | Verified sources (OPR >= 5). |
| language | object | – | Language filter. |
| location | object | – | – |
| media | object | – | Media-content filter. |
| organization | object | – | – |
| page | integer | – | Page number (default 1). |
| per_page | integer | – | Results per page (default 10). One response carries at most 25 articles. |
| person | object | – | – |
| published_at | object | – | Publication date range (ISO 8601). |
| read_time | object | – | Reading time in minutes. |
| sentiment | object | – | Sentiment filter. Scores range -1.0..1.0. |
| sort | object | – | – |
| source | object | – | Source filter. |
| title | string | – | Search by article title. Up to 3 keywords comma-separated (OR). Phrase in quotes for exact match. |
| topic | object | – | – |
No output schema declared.
No examples provided.
suggest Resolve Taxonomy IDs ~274
Resolve a name or prefix to APITube taxonomy IDs so you can use them in the `search_news` tool's filters. The `search_news` tool's most precise filters require IDs you cannot guess: - entity.id — numeric (persons, organizations, locations, brands, events...) - category.id — IPTC slug, e.g. "medtop:04000000" - topic.id — slug - industry.id — numeric Use this tool FIRST to look those IDs up, then pass them into `search_news`. USAGE: - type: which taxonomy to autocomplete — one of "entities", "categories", "topics", "industries". - prefix: the name (or its beginning) to search, e.g. "Tesla", "Elon", "spo". Returns an array of matches; take the `id` of the best match and put it into `search_news`: suggest({ type: "entities", prefix: "Tesla" }) → [{ id: 12345, name: "Tesla, Inc.", ... }] search_news({ entity: { id: "12345" } })
| Name | Type | Req | Description |
|---|---|---|---|
| prefix | string | yes | Name or prefix to search, e.g. "Tesla", "Elon", "spo". |
| type | string | yes | Which taxonomy to autocomplete. |
No output schema declared.
No examples provided.