# Viewlify (remote · viewlify.app)

TikTok videos that beat their creator's usual views, trends, hashtags and sounds by niche.

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

## Components

- remote · `viewlify.app`: 75/100 (this document), [markdown](https://verifymcp.io/servers/benjaminb10-viewlify/api-mcp.md), [page](https://verifymcp.io/servers/benjaminb10-viewlify/api-mcp)

## Channel facts

- Endpoint: `https://viewlify.app/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.3.1`

## 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**: 76/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 450 tokens (~112/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

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

Viewlify is a hosted endpoint at https://viewlify.app/api/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 benjaminb10-viewlify 'https://viewlify.app/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "benjaminb10-viewlify": {
      "url": "https://viewlify.app/api/mcp"
    }
  }
}
```

### VS Code

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

### Codex

```toml
[mcp_servers.benjaminb10-viewlify]
url = "https://viewlify.app/api/mcp"
```

### opencode

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

### OpenClaw

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

### Hermes

```yaml
mcp_servers:
  benjaminb10-viewlify:
    url: "https://viewlify.app/api/mcp"
```

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "benjaminb10-viewlify": {
      "type": "http",
      "url": "https://viewlify.app/api/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 75, +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-19 (score 74, +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-17 (score 73, +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-16 (score 72, −6)

- [security regression] Authorization: pass → partial
- [security] Tool “get_trending” rewrote its description, which is the text the model reads
- [security] Tool “get_trending_hashtags” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 76 → 112
- [functional] New tool “get_creator”

### 2026-11-14 (score 78, +15)

- [security improvement] Authorization: unverified → pass
- [functional] Server version: 1.3.0 → 1.3.1

### 2026-11-13 (score 63, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-12 (score 63)

First indexed and scored.

## MCP tools (4)

### `get_trending` (~105 tokens)

A full snapshot of what is breaking out on TikTok right now, optionally for one niche: the videos gaining views fastest (ranked by views per day, each with its creator, views and link), plus the 24 hashtags and 12 sounds that appear most often on those videos. Without an API key: 5 videos, 5 hashtags and 3 sounds.

Input parameters:

- `category` (string): Niche slug, e.g. beauty, gaming, food, fitness

### `get_outliers` (~107 tokens)

TikTok videos beating their own creator's usual views by the widest margin (the real breakouts), optionally for a niche or free-text search. Each result includes the outlier multiple and the creator's baseline (Pro and Agency keys; otherwise a 5-result preview without them).

Input parameters:

- `limit` (number): Max results (1-50)
- `niche` (string): Niche slug to focus on
- `search` (string): Free-text query (keyword, creator, hashtag)

### `get_creator` (~151 tokens)

One TikTok creator as Viewlify knows it: followers and their 30-day gain, usual views per video, engagement rate, posts per week, best breakout (views vs the usual views at the time), best posting day, most used hashtags and sounds, and their videos with views, likes, comments, shares and a vsUsual multiple. Reads Viewlify's base only; an account it has never seen returns found: false. Without an API key: stats plus 5 videos (the breakout and the most viewed); with a key: up to 50 videos, latest first.

Input parameters:

- `handle` (string, required): TikTok username, with or without @, or a TikTok profile or video link

### `get_trending_hashtags` (~87 tokens)

Hashtags only, no videos or sounds: up to 24 TikTok hashtags, each with the number of breaking-out videos that carry it, optionally for one niche (the niche's own keywords are left out, so the list shows the tags used alongside it). Without an API key: the top 10.

Input parameters:

- `category` (string): Niche slug to focus on

## Diagnostics

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

## Score history

- 2026-11-21: 75
- 2026-11-20: 74
- 2026-11-19: 74
- 2026-11-18: 73
- 2026-11-17: 73
- 2026-11-16: 72
- 2026-11-15: 78
- 2026-11-14: 78
- 2026-11-13: 63
- 2026-11-12: 63

## Common questions

### What is the Viewlify MCP server?

Viewlify is an MCP server listed in the public MCP registry as io.github.benjaminb10/viewlify. TikTok videos that beat their creator's usual views, trends, hashtags and sounds by niche. This page covers its hosted endpoint (https://viewlify.app/api/mcp).

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

Viewlify scores 75 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 Viewlify MCP server expose?

Viewlify exposes 4 tools: get_trending, get_outliers, get_creator, get_trending_hashtags. Their descriptions and schemas cost roughly 450 tokens of context every time the server is loaded.

### Does the Viewlify MCP server require authentication?

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

### Is the Viewlify MCP server still maintained?

Viewlify 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 Viewlify MCP server?

VerifyMCP ran 13 checks on Viewlify, 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://viewlify.app/api/mcp
- Repository: https://github.com/benjaminb10/viewlify-mcp
- Website: https://viewlify.app/tiktok-data-api
- Changelog RSS feed: https://verifymcp.io/servers/benjaminb10-viewlify/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/benjaminb10-viewlify/api-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/benjaminb10-viewlify/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/benjaminb10-viewlify/api-mcp
