# Jump on the Trend (remote · jumponthetrend.app)

Find viral AI video trends and templates, and put your face, a friend or your pet in them.

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

## Components

- remote · `jumponthetrend.app`: 78/100 (this document), [markdown](https://verifymcp.io/servers/app-jumponthetrend-jumponthetrend/jumponthetrend.md), [page](https://verifymcp.io/servers/app-jumponthetrend-jumponthetrend/jumponthetrend)

## Channel facts

- Endpoint: `https://jumponthetrend.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.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-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 854 tokens (~94/item across 9 items; 9 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 47/100
  - Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 87/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 60% of tool parameters carry a description.
- **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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Jump on the Trend MCP server?

Jump on the Trend is a hosted endpoint at https://jumponthetrend.app/mcp, 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 app-jumponthetrend-jumponthetrend 'https://jumponthetrend.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "app-jumponthetrend-jumponthetrend": {
      "url": "https://jumponthetrend.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "app-jumponthetrend-jumponthetrend": {
      "type": "http",
      "url": "https://jumponthetrend.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.app-jumponthetrend-jumponthetrend]
url = "https://jumponthetrend.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-jumponthetrend-jumponthetrend": {
      "type": "remote",
      "url": "https://jumponthetrend.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add app-jumponthetrend-jumponthetrend --url 'https://jumponthetrend.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  app-jumponthetrend-jumponthetrend:
    url: "https://jumponthetrend.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "app-jumponthetrend-jumponthetrend": {
      "Transport": "http",
      "Url": "https://jumponthetrend.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add app-jumponthetrend-jumponthetrend -t streamable-http -u 'https://jumponthetrend.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "app-jumponthetrend-jumponthetrend": {
      "type": "http",
      "url": "https://jumponthetrend.app/mcp"
    }
  }
}
```

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-21 (score 78, +1)

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

### 2026-11-18 (score 77, +1)

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

### 2026-11-16 (score 76, +1)

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

### 2026-11-14 (score 75, +1)

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

### 2026-11-12 (score 74, +1)

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

### 2026-11-10 (score 73, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: 82 → 94
- [functional] Server version: 1.0.0 → 1.1.0
- [functional] New tool “remake_video_link”

### 2026-11-09 (score 72, +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-11-08 (score 71, 0)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (9)

### `search_trends` (~170 tokens)

Search AI video trends

Search Jump on the Trend's live AI video trends and templates by name, meme, song, scene or topic (e.g. 'locker room', 'dog bartender', 'christmas', 'couple dance'). Optional filters: category and who's in it. Returns each trend's name, what happens in it, who can star, length, price and page link. An empty query lists the current top trends.

Input parameters:

- `category` (string): Optional category id or name from list_categories (e.g. 'pets', 'dance', 'christmas', 'memes').
- `limit` (integer)
- `query` (string): Words to look for: a trend or meme name, a song, a scene, a topic.
- `who` (string): Optional: who stars in it.

### `get_trend` (~87 tokens)

Get one trend

Everything about one trend: what it is and where it came from, the original clip, the sound, who can star, the versions and prices, photo tips, ideas for who to cast, common questions, and the page link where the person adds their photo for a free preview.

Input parameters:

- `trend` (string, required): The trend's id (slug), its name, or its page URL.

### `top_trends` (~41 tokens)

Top trends right now

The trends doing best on Jump on the Trend right now, best first, with what's hot, rising and new this week.

Input parameters:

- `limit` (integer)

### `list_categories` (~34 tokens)

List categories

The categories trends are filed under (pets, dance, couples, memes, seasons in season...) with how many trends each has.

### `how_it_works` (~28 tokens)

How it works and prices

How making a video works on Jump on the Trend, what's free, and today's prices.

### `remake_video_link` (~140 tokens)

Put yourself in a video you have a link to

For a person who has a link to one specific video and wants to be in it ("put me in this TikTok", "swap my face into this Reel"). Returns a Jump on the Trend page with that video loaded: they add a photo there, pick who to replace, see a free preview still, then make up to 30 seconds of it with their face in. Works with public TikTok, Instagram, YouTube, X, Facebook, Threads, Reddit, Snapchat and Vimeo video links. Nothing is made from chat; give the person the link.

Input parameters:

- `url` (string, required): The link to the video the person wants to be in.

### `suggest_trend` (~81 tokens)

Suggest a missing trend

Send the team a TikTok, Instagram or YouTube link to a trend that isn't on Jump on the Trend yet. It is reviewed by hand; nothing is promised. Only use it when the person wants a trend that search_trends didn't find.

Input parameters:

- `url` (string, required): A TikTok, Instagram or YouTube link to an example of the trend.

### `search` (~31 tokens)

Search

Search Jump on the Trend's AI video trends. Returns ids to pass to fetch.

Input parameters:

- `query` (string, required)

### `fetch` (~27 tokens)

Fetch

Fetch one trend's full page text by the id search returned.

Input parameters:

- `id` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/app-jumponthetrend-jumponthetrend/jumponthetrend#diagnostics

## Score history

- 2026-11-21: 78
- 2026-11-20: 77
- 2026-11-19: 77
- 2026-11-18: 77
- 2026-11-17: 76
- 2026-11-16: 76
- 2026-11-15: 75
- 2026-11-14: 75
- 2026-11-13: 74
- 2026-11-12: 74
- 2026-11-11: 73
- 2026-11-10: 73
- 2026-11-09: 72
- 2026-11-08: 71
- 2026-11-07: 71

## Common questions

### What is the Jump on the Trend MCP server?

Jump on the Trend is an MCP server listed in the public MCP registry as app.jumponthetrend/jumponthetrend. Find viral AI video trends and templates, and put your face, a friend or your pet in them. This page covers its hosted endpoint (https://jumponthetrend.app/mcp).

### Is the Jump on the Trend MCP server safe to use?

Jump on the Trend scores 78 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 Jump on the Trend MCP server expose?

Jump on the Trend exposes 9 tools: search_trends, get_trend, top_trends, list_categories, how_it_works, and 4 more. Their descriptions and schemas cost roughly 639 tokens of context every time the server is loaded.

### Does the Jump on the Trend MCP server require authentication?

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

### Is the Jump on the Trend MCP server still maintained?

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

### What did VerifyMCP test on the Jump on the Trend MCP server?

VerifyMCP ran 13 checks on Jump on the Trend, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://jumponthetrend.app/mcp
- Website: https://jumponthetrend.app/
- Changelog RSS feed: https://verifymcp.io/servers/app-jumponthetrend-jumponthetrend/jumponthetrend.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-jumponthetrend-jumponthetrend/jumponthetrend/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/app-jumponthetrend-jumponthetrend/jumponthetrend.json
- HTML version of this page: https://verifymcp.io/servers/app-jumponthetrend-jumponthetrend/jumponthetrend
