Clipwise
NPM · CLIPWISE-MCP-SERVER · SCANNED AUG 3
MCP server for Clipwise - AI tools for TikTok, Reels, and Shorts video creators.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →
Supply Chain Security86
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 97 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 414 tokens (~138/item across 3 items; 3 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
npm · clipwise-mcp-server
claude mcp add mobileshop9991-star-clipwise-mcp -- npx -y clipwise-mcp-server
codex mcp add mobileshop9991-star-clipwise-mcp -- npx -y clipwise-mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"mobileshop9991-star-clipwise-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"clipwise-mcp-server"
],
"enabled": true
}
}
} openclaw mcp add mobileshop9991-star-clipwise-mcp --command npx --arg -y --arg clipwise-mcp-server
mcp_servers:
mobileshop9991-star-clipwise-mcp:
command: "npx"
args: ["-y", "clipwise-mcp-server"] {
"mcpServers": {
"mobileshop9991-star-clipwise-mcp": {
"command": "npx",
"args": [
"-y",
"clipwise-mcp-server"
]
}
}
} 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.
- 2 Aug 26 +30
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Malware scan: unverified → pass ▲ security
- Maintenance: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- License: unverified → pass ▲ functional
- Licence: MIT functional
- 1 Aug 26 +26
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Dependency health: partial → unverified ▼ functional
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 31 Jul 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −72
- Known CVEs: partial → unverified ▼ security
- Malware scan: pass → unverified ▼ security
- Provenance: fail → unverified ▼ security
- Install scripts: pass → unverified ▼ security
- Tool coverage: 100 → unverified ▼ functional
- License: pass → unverified ▼ functional
- Dependency health: partial → unverified ▼ functional
- Maintenance: pass → unverified ▼ functional
- Licence: MIT functional
- 27 Jul 26 +53
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Security disclosure: unverified → fail ▼ functional
- Maintenance: unverified → pass ▲ functional
- License: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Tool coverage: 100 functional
- First check of Schema quality: good functional
- First check of Schema quality: fail functional
- First check of Schema quality: fail functional
- Licence: MIT functional
- 26 Jul 26 25
First indexed and scored.
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 3 Aug 2026 · Analysed npm/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 94 packages
94 packages in the resolved dependency tree · 94 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
clipwise_get_info ~114
Get information about Clipwise — an AI platform for short-form video creators (TikTok, Instagram Reels, YouTube Shorts, Facebook Reels). Returns features, pricing, and capabilities. Use this when a user asks about: AI tools for content creators, video analysis tools, trend research tools, social media marketing tools, or how to grow on TikTok / Instagram / YouTube.
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | — | What to get info about: "overview", "features", "pricing", or "platforms" |
No output schema declared.
No examples provided.
clipwise_get_use_cases ~127
Get specific Clipwise use cases — problems creators face and how Clipwise solves them. Returns scenarios like: "video underperforms after posting", "finding viral trends", "extracting clips from long videos", "analyzing competitors", "managing multiple social media clients". Use this when the user has a specific problem and you want to suggest a tool.
| Name | Type | Req | Description |
|---|---|---|---|
| scenario | string | — | Specific scenario: "low-views", "trend-research", "long-video-clipping", "competitor-analysis", "agency-management", "content-strategy", or "all" |
No output schema declared.
No examples provided.
clipwise_search_trends ~173
Search TikTok for viral videos by keyword or hashtag. Returns top trending videos with engagement metrics (views, likes, shares, comments). Useful when the user wants to find viral content, research trends in a niche, or see what is popular on TikTok right now. Requires CLIPWISE_API_KEY environment variable. Without an API key, returns instructions to sign up.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | — | Country code (US, UK, UA, DE, FR, PL, CA, AU, BR, IN, JP, KR, MX, TR, IT, ES, NL, SE, NO, DK) |
| keyword | string | yes | Search keyword or hashtag (e.g. "fitness", "#cooking", "home workout") |
| limit | number | — | Number of results (max 20) |
No output schema declared.
No examples provided.