Viewlify
REMOTE · VIEWLIFY.APP
TikTok videos that beat their creator's usual views, trends, hashtags and sounds by niche.
Available components
Last scanned (15 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Marketing and SEO
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 → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 450 tokens (~112/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 +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.
- 19 Nov 26 +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.
- 17 Nov 26 +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.
- 16 Nov 26 −6
- 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 security
- Schema quality: 76 → 112 ▼ functional
- New tool “get_creator” functional
- 14 Nov 26 +15
- Authorization: unverified → pass ▲ security
- Server version: 1.3.0 → 1.3.1 functional
- 13 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 12 Nov 26 63
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 21 Nov 2026 · Probed https://viewlify.app/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=viewlify.app | CN=WE1,O=Google Trust Services,C=US | 13 Nov 2026 | 11 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | a2246258618cc679135fb50690522be3 |
| SANs: viewlify.app, *.viewlify.app | ||||||
| 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 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of viewlify.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| app. | DS published | 23684 | 8 | Verified |
| viewlify.app. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://www.googletagmanager.com https://www.clarity.ms https://*.clarity.ms https://js.stripe.com https://*.stripe.com https://cdn.mxpnl.com https://challenges.cloudflare.com https://connect.facebook.net; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; img-src 'self' data: blob: https:; font-src 'self' https://fonts.gstatic.com data:; connect-src 'self' https://*.google-analytics.com https://*.googletagmanager.com https://*.clarity.ms https://api.stripe.com https://*.stripe.com https://*.mixpanel.com https://challenges.cloudflare.com https://www.facebook.com https://connect.facebook.net; worker-src 'self' blob:; frame-src https://js.stripe.com https://*.stripe.com https://www.tiktok.com https://challenges.cloudflare.com https://www.facebook.com; frame-ancestors 'self'; base-uri 'self'; form-action 'self' https://www.facebook.com; object-src 'none' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), browsing-topics=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://viewlify.app/api/mcp | Verified | 200 | |
| http (plaintext) | http://viewlify.app/api/mcp | HTTPS enforced | 301 | https://viewlify.app/api/mcp |
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_creator ~151
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.
| Name | Type | Req | Description |
|---|---|---|---|
| handle | string | yes | TikTok username, with or without @, or a TikTok profile or video link |
No output schema declared.
No examples provided.
get_outliers ~107
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).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results (1-50) |
| niche | string | – | Niche slug to focus on |
| search | string | – | Free-text query (keyword, creator, hashtag) |
No output schema declared.
No examples provided.
get_trending ~105
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Niche slug, e.g. beauty, gaming, food, fitness |
No output schema declared.
No examples provided.
get_trending_hashtags ~87
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Niche slug to focus on |
No output schema declared.
No examples provided.
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.
remote · viewlify.app
claude mcp add --transport http benjaminb10-viewlify 'https://viewlify.app/api/mcp'
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.