cliphou.se release videos
REMOTE · CLIPHOU.SE
Turns every release into a social video. Finds the selling points, picks the angle, writes the copy.
Available components
Last scanned (4 hours ago)
Scores higher than 89% of remote servers
Reachable. Last reached 5 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 Security83
- 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. 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 is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 3209 tokens (~458/item across 7 items; 6 tools + 1 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 Management73
- Stability observed for 22 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +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.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +2
- DNSSEC: fail → pass ▲ security
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 5 Nov 2026 · Probed https://cliphou.se/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=cliphou.se | CN=YE2,O=Let's Encrypt,C=US | 14 Oct 2026 | 12 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 61a52180014d5f41e51a6e562a358696030 |
| SANs: *.cliphou.se, cliphou.se | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of cliphou.se. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| se. | present | 59407 | 8 | Verified |
| cliphou.se. | present | 2371 | 13 | Verified |
| cliphou.se. | Verified address RRset verified with the apex keys |
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=31556926 |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://cliphou.se/mcp | Verified | 200 | |
| http (plaintext) | http://cliphou.se/mcp | HTTPS enforced | 301 | https://cliphou.se/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 →
build_edit_link Build editor link ~129
Validate filled-in props for a template and return a cliphou.se link that opens a live, editable preview of the customized video. The user can export the MP4 there. Invalid props return an error that names the field to fix.
| Name | Type | Req | Description |
|---|---|---|---|
| props | object | yes | The full props object from get_template_spec with edited texts, theme, and media. |
| searchId | string | – | The searchId returned by search_templates. Pass it through so picks can be measured. |
| templateVersion | integer | – | Only for older template versions. Usually omit. |
| variantId | string | yes | Template id. |
No output schema declared.
No examples provided.
get_template_spec Get template spec ~93
Get the editable fields of one template: current props, text roles with maxLength, theme colors, scenes, format, JSON Schema, and the source package for local rendering. Call before build_edit_link and start from the returned props.
| Name | Type | Req | Description |
|---|---|---|---|
| searchId | string | – | The searchId returned by search_templates. Pass it through so picks can be measured. |
| variantId | string | yes | Template id from search_templates. |
No output schema declared.
No examples provided.
render_preview Render personalized preview ~268
Render a poster image of a template filled with the user's props, in a few seconds, and return it with the editor link. Call after get_template_spec once the props are filled, and show the image to the user. Invalid props return an error that names the field to fix. If rendering is unavailable, poster is null and the editor link still works. With loop: true it also waits for a 4-second animated WebP loop of these props and returns it as video. A loop still rendering has video: null and videoPending: true; call again with the same props to get it. loop: "start" returns the poster now and starts the loop in the background. Show the loop as an image (Markdown ) where the host renders images.
| Name | Type | Req | Description |
|---|---|---|---|
| loop | – | – | true waits for a 4-second animated loop of these props and returns it as video. "start" only starts it. |
| props | object | yes | The full props object from get_template_spec with edited texts, theme, and media. |
| searchId | string | – | The searchId returned by search_templates. Pass it through so picks can be measured. |
| templateVersion | integer | – | Only for older template versions. Usually omit. |
| variantId | string | yes | Template id. |
No output schema declared.
No examples provided.
render_previews Render tailored previews ~367
Render posters of up to 4 templates at once, each filled with one brand description, so the user picks from options that already show their product. The server maps the brand onto each template's text fields and shortens text to fit. Returns, per template: id, title, poster URL (null if it was not ready in time), editor link, the tailored props to start from after the pick, and keptSample: text fields that still hold the template's sample text (fill them with real facts after the pick). Inline images follow the text, in the same order as the results. shortened lists brand texts that were cut to fit a field ({role, from, to, max}); rewrite them for that field after the pick. Animated loops (4-second animated WebP of each tailored template) take two calls. First call with loop: "start": it returns the posters as fast as without loops and starts the loops in the background. Show the posters. Then call again with the same arguments and loop: true: it waits for the loops and returns video (the loop URL) per template. A loop still rendering has video: null and videoPending: true; call once more to get it. Show each loop as an image (Markdown ) where the host renders images, so the options animate.
| Name | Type | Req | Description |
|---|---|---|---|
| brand | object | yes | The product facts from the user's project. Never invent numbers. |
| loop | – | – | "start" returns the posters now and starts 4-second animated loops in the background. true waits for the loops and returns them as video. |
| searchId | string | – | The searchId returned by search_templates. Pass it through so picks can be measured. |
| variantIds | array | yes | Template ids from search_templates. |
No output schema declared.
No examples provided.
search_templates Search video templates ~491
Find marketing video templates for a product, project, or announcement. Prefer a marketing goal and, when project facts support it, a release moment; then add a short product or style query. Returns a searchId, the selected moment, detectedMoments hints, and results with id, title, goals, moments, aspect, length, preview MP4, poster image, and editor URL. Engine details appear only when the engine filter is used.
| Name | Type | Req | Description |
|---|---|---|---|
| aspect | string | – | Only when the destination implies it: 9:16 vertical (Reels, TikTok, Shorts), 16:9 (YouTube, web), 1:1 or 4:5 (feeds). |
| engine | string | – | Advanced source-package filter. Omit unless the user explicitly asks for an engine. |
| goal | string | – | Marketing goal. One of: launch-product (Launch a product), announce-feature (Announce a feature), share-update (Share an update), grow-waitlist (Grow a waitlist), announce-integration (Announce an in… |
| limit | integer | – | Maximum results, default 6. |
| maxSeconds | integer | – | Maximum video length in seconds. |
| moment | string | – | Release moment backed by project facts. Filters and ranks templates for it. One of: most-requested-feature (Most-requested feature shipped), generally-available (Available to everyone), limit-raised… |
| music | boolean | – | true for beat-synced templates with a generated soundtrack, false for silent ones. |
| purpose | string | – | Exact catalog purpose, for example "Product launch". |
| query | string | – | Short product or style description, for example "developer tool" or "minimal logo". |
No output schema declared.
No examples provided.
upload_logo Upload brand logo ~180
Upload the product's logo once, then pass the returned logo object as brand.logo to render_previews, or as props.logo in templates that support a logo (their spec lists editableFields.logo). Templates with a logo show it wherever they show the brand name; the brand text stays as its alt text. Send an SVG as text in svg, or a PNG, JPEG, WebP, or SVG file as base64 in data. Up to 1 MB. Prefer the project's SVG logo (for example public/logo.svg) or a PNG with a transparent background. mono: true draws the logo in the template's text color, which keeps it readable on any theme; it needs a transparent background.
| Name | Type | Req | Description |
|---|---|---|---|
| data | string | – | The logo file as base64, or as a data: URL. |
| svg | string | – | The logo as SVG text. |
No output schema declared.
No examples provided.
How do I install the cliphou.se release videos MCP server?
cliphou.se release videos is a hosted endpoint at https://cliphou.se/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 · cliphou.se
claude mcp add --transport http se-cliphou-templates 'https://cliphou.se/mcp'
What is the cliphou.se release videos MCP server?
cliphou.se release videos is an MCP server listed in the public MCP registry as se.cliphou/templates. Turns every release into a social video. Finds the selling points, picks the angle, writes the copy. This page covers its hosted endpoint (https://cliphou.se/mcp).
Is the cliphou.se release videos MCP server safe to use?
cliphou.se release videos scores 84 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 cliphou.se release videos MCP server expose?
cliphou.se release videos exposes 6 tools: upload_logo, search_templates, get_template_spec, build_edit_link, render_preview, render_previews. Their descriptions and schemas cost roughly 1,528 tokens of context every time the server is loaded.
Does the cliphou.se release videos MCP server require authentication?
No. We connected to cliphou.se release videos without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the cliphou.se release videos MCP server still maintained?
cliphou.se release videos 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.