# TrendsFast (remote · trendsfast.com)

Niche trend intelligence for agents: what is trending, what customers ask, with sources and dates.

- Trust score: 66/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `trendsfast.com`: 66/100 (this document), [markdown](https://verifymcp.io/servers/com-trendsfast-trends/api-mcp-v3.md), [page](https://verifymcp.io/servers/com-trendsfast-trends/api-mcp-v3)

## Channel facts

- Endpoint: `https://trendsfast.com/api/mcp/v3`
- Transports: `streamable-http`
- Auth: `none`
- Version: `3.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 66/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (trendsfast_global_trends).
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 58/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1537 tokens (~170/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the TrendsFast MCP server?

TrendsFast is a hosted endpoint at https://trendsfast.com/api/mcp/v3, 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.

### Claude

```bash
claude mcp add --transport http com-trendsfast-trends 'https://trendsfast.com/api/mcp/v3'
```

### Cursor

```json
{
  "mcpServers": {
    "com-trendsfast-trends": {
      "url": "https://trendsfast.com/api/mcp/v3"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-trendsfast-trends": {
      "type": "http",
      "url": "https://trendsfast.com/api/mcp/v3"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-trendsfast-trends]
url = "https://trendsfast.com/api/mcp/v3"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-trendsfast-trends": {
      "type": "remote",
      "url": "https://trendsfast.com/api/mcp/v3",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-trendsfast-trends --url 'https://trendsfast.com/api/mcp/v3' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-trendsfast-trends:
    url: "https://trendsfast.com/api/mcp/v3"
```

### Netclaw

```json
{
  "McpServers": {
    "com-trendsfast-trends": {
      "Transport": "http",
      "Url": "https://trendsfast.com/api/mcp/v3"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-trendsfast-trends -t streamable-http -u 'https://trendsfast.com/api/mcp/v3'
```

### Other

```json
{
  "mcpServers": {
    "com-trendsfast-trends": {
      "type": "http",
      "url": "https://trendsfast.com/api/mcp/v3"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 66, +1)

- [functional] New tool “trendsfast_community_brief”

### 2026-11-04 (score 65, 0)

- [security] The server rewrote its instructions, which are the text every model session reads

### 2026-11-03 (score 65, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] New tool “trendsfast_video_outlier”, which the server declares destructive
- [functional regression] Schema quality: 1129 → 1375

### 2026-11-02 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 63, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “trendsfast_global_trends” rewrote its description, which is the text the model reads
- [security] Tool “trendsfast_niche_trends” rewrote its description, which is the text the model reads
- [security] Tool “trendsfast_project_context” rewrote its description, which is the text the model reads
- [security] Tool “trendsfast_read_result” rewrote its description, which is the text the model reads
- [functional improvement] Stability: unverified → 0.03

### 2026-10-29 (score 63)

First indexed and scored.

## MCP tools (9)

### `trendsfast_global_trends` (~161 tokens)

Global trends

Query the shared saved trend index without Product DNA. Maximum 1 credit(s); zero provider calls. Results rank explicit popularity or measured growth first, then US, UK, Canada and Australia, then Europe, alternating sources. data.brief groups the items into trending now, audience conversations, creative references, search demand and references, and names coverage gaps and next steps. Each item's evidence_class, uses and caution give what it supports and what it does not establish. Saves a result and debits credits when charged. The same request_id returns that saved result without a second charge; a new request_id is a new billable query.

Input parameters:

- `input` (object, required)
- `max_credits` (integer, required)
- `request_id` (string, required)

Output parameters:

- `data` (object)
- `error` (string)
- `ok` (boolean)

### `trendsfast_niche_trends` (~471 tokens)

Niche trends

Rank evidence against confirmed project context or explicit temporary niche. Without product: maximum 3 credits and no new source research. A product needs the confirmed context_id: it first collects the brand's own sources fresh, then ranks through that product's lens: customers (Customers) 10 credits, niche (Trending) 25 credits, competitors (Competitors) 30 credits, formats (Formats) 20 credits, search (Search) 35 credits. A product on a typed niche is refused with PRODUCT_REQUIRES_CONTEXT and charges nothing; a typed niche is read without a product. Formats also reads the top TikTok and YouTube videos' transcripts, so each item's hook is its opening line. Search also asks ChatGPT, Claude, Gemini and Perplexity the category's buyer question (no brand is sent) and returns data.ai_answers: who each answer names, whether that includes the brand or its competitors, and the domains cited. A Customers or Trending call, or a read without product, also returns data.communities when the brand's confirmed communities have been read: each one's rules on self-promotion, links and AI-written posts (citing rule numbers), the formats it favours, what wins there over all time (winning_format, hook_pattern and avoid, read by Claude from its top posts), the moderators' pinned posts (pinned), and a play for taking part without breaking them. A Trending call may also give each item a topic_history: where its topic is in its life across days and channels (state, since, first_seen, peak_day, channels, 7-day velocity, as_of), or null until the topic has a lifecycle state; it is the only basis for saying when a topic started rising. new_research says whether the call collected or asked. CORE means a specific topic, problem, keyword or exact competitor-account match; sharing only a broad family such as AI is ADJACENT. A temporary niche may add communities, competitor_handles, competitor_domains and keywords for exact matching. data.brief and each item's evidence_class, uses and caution…

Input parameters:

- `input` (object, required)
- `max_credits` (integer, required)
- `request_id` (string, required)

Output parameters:

- `data` (object)
- `error` (string)
- `ok` (boolean)

### `trendsfast_discover_trends` (~98 tokens)

Discover trends

Answer one question across global, core and adjacent scope and every source channel in a single call. Maximum 5 credits; zero provider calls. Global scope needs no Product DNA. A channel with no permitted observation is reported UNAVAILABLE rather than empty. Saves a result and may debit credits. No new source research.

Input parameters:

- `input` (object, required)
- `max_credits` (integer, required)
- `request_id` (string, required)

Output parameters:

- `data` (object)
- `error` (string)
- `ok` (boolean)

### `trendsfast_ask_trends` (~149 tokens)

Ask about trends

Answer a bounded question using saved intelligence. Maximum 5 credits. Questions about competitors, customer complaints, feature requests, hooks and formats, or search keywords each need their own evidence: answer_status says ANSWERED, PARTIAL, INSUFFICIENT_EVIDENCE, NEEDS_CONTEXT or NOT_COLLECTED, findings cite each item with its kind, and missing_inputs and next_steps say what would complete the answer. An answer with no findings costs nothing. Saves a result and may debit credits. No provider or model calls, invented growth or hidden fresh research.

Input parameters:

- `input` (object, required)
- `max_credits` (integer, required)
- `request_id` (string, required)

Output parameters:

- `data` (object)
- `error` (string)
- `ok` (boolean)

### `trendsfast_video_outlier` (~233 tokens)

Video outlier check

Video outlier check: one TikTok, Instagram or YouTube video against its creator's recent posts. Maximum 5 credits, charged only when the video is found among them with a view count; NOT_FOUND (older than a month or outside the newest 20 posts) and NO_BASELINE cost nothing. A TikTok input.url names its creator; Instagram and YouTube need input.handle, or are refused before any charge. Reads the creator's public account, or reuses a read from the last six hours at no extra cost. data.video_outlier: status, outlier_score (views ÷ the creator's median views), performance_label (MEGA_VIRAL 10×+, VIRAL 3×+, ABOVE_AVERAGE 1.5×+, AVERAGE), weighted_score, percentile, z_score, median_views, mean_views, videos_analyzed, breakout (over 3×), basis; items are the creator's posts. Saves a result.

Input parameters:

- `input` (object, required)
- `max_credits` (integer, required)
- `request_id` (string, required)

Output parameters:

- `data` (object)
- `error` (string)
- `ok` (boolean)

### `trendsfast_read_result` (~68 tokens)

Read a saved result

Read a saved result, page it on next_cursor, or recover an exact accepted request ID. No credit debit or research. Source permissions, retention and context are rechecked.

Input parameters:

- `cursor` (string)
- `request_id` (string)
- `result_id` (string)

Output parameters:

- `data` (object)
- `error` (string)
- `ok` (boolean)

### `trendsfast_community_brief` (~113 tokens)

Community brief

Read TrendsFast's brief on one subreddit, from Claude Opus's reading of its top posts, replies and images: who is there and what they need, how far authority, expertise, being relatable and humor are rewarded, the winning post and reply, what fails, its rules, and what a good result is now. Without community, lists the communities that have one. rules.ai_written says whether a person must write the words. No credit debit or new research.

Input parameters:

- `community` (string)

Output parameters:

- `data`
- `error` (string)
- `ok` (boolean)

### `trendsfast_project_context` (~51 tokens)

Project context

Read the connected project name, ID and current confirmed niche context, or an explicit missing-context state. Returns the context_id that niche and Ask queries accept. No credit debit, context mutation or new research.

Output parameters:

- `data` (object)
- `error` (string)
- `ok` (boolean)

### `trendsfast_credit_balance` (~32 tokens)

Credit balance

Read the shared REST/MCP credit balance, monthly/prepaid split, reservations and pause state without spending credits.

Output parameters:

- `data` (object)
- `error` (string)
- `ok` (boolean)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-trendsfast-trends/api-mcp-v3#diagnostics

## Score history

- 2026-11-05: 66
- 2026-11-04: 65
- 2026-11-03: 65
- 2026-11-02: 65
- 2026-11-01: 64
- 2026-10-31: 64
- 2026-10-30: 63
- 2026-10-29: 63

## Common questions

### What is the TrendsFast MCP server?

TrendsFast is an MCP server listed in the public MCP registry as com.trendsfast/trends. Niche trend intelligence for agents: what is trending, what customers ask, with sources and dates. This page covers its hosted endpoint (https://trendsfast.com/api/mcp/v3).

### Is the TrendsFast MCP server safe to use?

TrendsFast scores 66 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 TrendsFast MCP server expose?

TrendsFast exposes 9 tools: trendsfast_global_trends, trendsfast_niche_trends, trendsfast_discover_trends, trendsfast_ask_trends, trendsfast_video_outlier, and 4 more. Their descriptions and schemas cost roughly 1,376 tokens of context every time the server is loaded.

### Does the TrendsFast MCP server require authentication?

No. We connected to TrendsFast without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the TrendsFast MCP server still maintained?

TrendsFast is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://trendsfast.com/api/mcp/v3
- Authorisation metadata: https://trendsfast.com/.well-known/oauth-protected-resource/api/mcp/v3
- Website: https://trendsfast.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-trendsfast-trends/api-mcp-v3.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-trendsfast-trends/api-mcp-v3.json
- HTML version of this page: https://verifymcp.io/servers/com-trendsfast-trends/api-mcp-v3