io.github.khan-ashifur/hooklayer
REMOTE · HOOKLAYER.DEV · SCANNED SEP 20
Viral-content intelligence for AI agents — 7 read-only MCP tools, evidence-layer scoring.
Available components
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 Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability61
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 3528 tokens (~294/item across 12 items; 12 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 13 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
How do I install the io.github.khan-ashifur/hooklayer MCP server?
io.github.khan-ashifur/hooklayer is a hosted endpoint at https://hooklayer.dev/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 · hooklayer.dev
claude mcp add --transport http khan-ashifur-hooklayer 'https://hooklayer.dev/api/mcp'
{
"mcpServers": {
"khan-ashifur-hooklayer": {
"url": "https://hooklayer.dev/api/mcp"
}
}
} {
"servers": {
"khan-ashifur-hooklayer": {
"type": "http",
"url": "https://hooklayer.dev/api/mcp"
}
}
} [mcp_servers.khan-ashifur-hooklayer] url = "https://hooklayer.dev/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"khan-ashifur-hooklayer": {
"type": "remote",
"url": "https://hooklayer.dev/api/mcp",
"enabled": true
}
}
} openclaw mcp add khan-ashifur-hooklayer --url 'https://hooklayer.dev/api/mcp' --transport streamable-http
mcp_servers:
khan-ashifur-hooklayer:
url: "https://hooklayer.dev/api/mcp" {
"McpServers": {
"khan-ashifur-hooklayer": {
"Transport": "http",
"Url": "https://hooklayer.dev/api/mcp"
}
}
} assistant mcp add khan-ashifur-hooklayer -t streamable-http -u 'https://hooklayer.dev/api/mcp'
{
"mcpServers": {
"khan-ashifur-hooklayer": {
"type": "http",
"url": "https://hooklayer.dev/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 14 Sept 26 −1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “watch_account” rewrote its description, which is the text the model reads security
- 13 Sept 26 0
- “viral_remix” reworded the description of “verified_product_facts” cosmetic
1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.
- 26 Aug 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
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Aug 26 0
- Schema quality: 309 → 278 ▲ functional
- New tool “get_changes” functional
- New tool “list_watches” functional
- New tool “watch_account” functional
- 15 Aug 26 0
- Tool “viral_remix” rewrote its description, which is the text the model reads security
- “viral_remix” added an optional parameter “platform” cosmetic
- “viral_remix” added an optional parameter “target_product” cosmetic
- “viral_remix” added an optional parameter “target_topic” cosmetic
- “viral_remix” added an optional parameter “verified_product_facts” cosmetic
- “viral_remix” reworded the description of “my_topic” cosmetic
- 11 Aug 26 0
- 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 20 Sept 2026 · Probed https://hooklayer.dev/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=hooklayer.dev | CN=YR2,O=Let's Encrypt,C=US | 12 Sept 2026 | 11 Dec 2026 | RSA 2048 | SHA256-RSA | 50f7396ae4c04e2b9859dd52e423380de2c |
| SANs: hooklayer.dev | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of hooklayer.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| hooklayer.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://hooklayer.dev/.well-known/oauth-protected-resource"
Bearer resource_metadata="https://hooklayer.dev/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Protected resource metadata
| Document | https://hooklayer.dev/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://hooklayer.dev |
| Authorisation server | https://hooklayer.dev |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://hooklayer.dev/api/mcp | Verified | 200 | |
| http (plaintext) | http://hooklayer.dev/api/mcp | HTTPS enforced | 308 | https://hooklayer.dev/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 →
analyze_account ~484
Analyze a TikTok, YouTube, or Instagram creator by handle or channel ID. Returns viral DNA scores (viral_dna_score, replicability_score, originality_score, consistency_score, audience_fatigue), content patterns, format fingerprint, top recent videos with transcripts, content gaps, a headline_insight object (the single largest quantified performance gap across length, hook, format, and cadence, plus its so_what), and suggested next research steps. Use when the user asks to analyze a creator, account, channel, or competitor. Supports TikTok (full transcript extraction), YouTube (Shorts and longform analysis with captions when available), and Instagram (Reels with best-effort transcripts).
| Name | Type | Req | Description |
|---|---|---|---|
| handle | string | yes | Creator handle (with or without @ prefix) or YouTube channel ID. Examples: "@mrbeast", "mrbeast", "UCX6OQ3DkcsbYNE6H8uQQuVA". |
| platform | string | – | Platform to analyze. "tiktok" (default) returns full pipeline with transcripts. "youtube" analyzes recent Shorts via YouTube Data API + Innertube caption extraction — videos with captions disabled or… |
| recent_only | boolean | – | When true, hard-cap the candidate pool to videos posted in the last 90 days. Stricter than `window=90d` because it never falls through to archival data on a thin recent corpus. |
| since | string | – | Optional ISO date (e.g. "2026-04-01"). Filter the candidate video pool to those posted on/after this date. Useful when the user asks "show me what they've done THIS month" — the route returns honest… |
| window | string | – | Recency sugar — same effect as `since` but takes a friendlier bucket. Maps to a since-cutoff at request time. Use either `since` or `window`, not both. |
| Name | Type | Req | Description |
|---|---|---|---|
| content_gaps | array | – | Untapped content opportunities the creator is missing |
| credits_remaining | number | – | Credits remaining after this call |
| format_fingerprint | object | – | Dominant content format patterns (durations, styles, edit types) |
| from_payg | boolean | – | Whether credits came from pay-as-you-go balance |
| from_subscription | boolean | – | Whether credits came from subscription |
| headline_insight | object | – | The largest quantified performance gap for this creator, plus its implication. Presentation-neutral data — the caller decides whether and how to surface it. |
| pattern_analysis | object | – | Content pattern breakdown (posting cadence, topic clusters) |
| profile | object | – | Creator profile (handle, bio, followers, following, total_likes, total_videos) |
| recent_videos | array | – | Top recent videos with view counts, transcripts, and engagement |
| recommended_chain | array | – | Suggested next tool calls with pre-filled parameters — advisory only, agent decides whether to execute |
| steal_map | array | – | Actionable elements to replicate from this creator |
| viral_dna | object | – | Five viral DNA scores (0-100 each) |
No examples provided.
brief_to_blueprint ~530
Turn a brand brief that just landed into a one-page creative blueprint the manager can forward to the creator and to the brand contact — hook + template + hashtag combo + trend-velocity check + shoot instructions, in one call. Use when a brand sends a product and needs content on a tight turnaround (e.g. "product arrived, need content in 48 hours") and the manager needs a defensible direction with no research time. Chains find_viral_template + trend_pulse + score_hook + predict_virality upstream but exposes them as one MCP tool so agents don't stitch them manually. Cost 7 credits (bundle discount vs firing the chain manually). Returns a blueprint object with verdict (GO | NEEDS_MORE_DATA | NO_GO) and verdict_reason, a hook (text + trend_still_alive: up-slope | plateau | fading | unknown), script, hashtags, shoot notes, risk flags, and manager talking points, plus a quality object (level + reason) describing completeness; when quality.level is not "full", or verdict is NEEDS_MORE_DATA or NO_GO, the blueprint is a starting point rather than a shippable direction.
| Name | Type | Req | Description |
|---|---|---|---|
| creator_handle | string | – | Optional creator handle (with or without @). If provided, the blueprint hook and script match THEIR voice patterns from recent videos. Highly recommended — a blueprint without creator context is gene… |
| deadline_hours | integer | – | How many hours until the video must be posted. Default 48. Affects trend-still-alive scoring — a 24-hour deadline needs a trend on the up-slope, not one that just plateaued. |
| niche | string | yes | One of the 17 supported niches. Loose names like "beauty" or "fitness" are auto-mapped. |
| platform | string | – | Target platform. Both TikTok and Instagram Reels supported (shipped 2026-07-06). When set to "instagram", the product-corpus lookup runs against Instagram Reels via ScrapeCreators, and the creator co… |
| product | string | yes | What the brand sent (name + one line, e.g. "Athletic Greens AG1 travel packs — 30-count individual sachets for travel") |
| product_category | string | yes | Umbrella category (e.g. "greens powder", "sunscreen", "protein bar") |
| region | string | – | Optional 2-letter ISO country code (US, GB, CA, etc.). Threads to niche + trend upstreams. |
| Name | Type | Req | Description |
|---|---|---|---|
| applied | object | – | Echo of parameters resolved after canonicalization |
| as_of | string | – | – |
| blueprint | object | – | – |
| credits_remaining | object | – | – |
| provenance | object | – | – |
| quality | object | – | – |
| stats | object | – | – |
| success | boolean | – | – |
No examples provided.
find_viral_template ~434
Find proven viral templates in a niche with example videos. Returns templates ranked by performance, including hook patterns, format structures, average views, and example URLs. Use when the user asks what's working in a niche or wants concrete copyable structures. Supports 17 niches with optional angle narrowing via query parameter for more specific results (e.g., "postpartum strength" within Fitness).
| Name | Type | Req | Description |
|---|---|---|---|
| min_views | integer | – | Optional filter — only return examples above this view count |
| niche | string | yes | One of the 17 supported niches. Loose names like "travel" or "fitness" are accepted but pass the canonical form when possible. |
| platform | string | – | Platform to source templates from. "tiktok" (default) uses the full niche-aggregator (YouTube + Reddit + TikTok hashtags). "instagram" (2026-07-06) is keyword-search-only — the Instagram niche-aggreg… |
| query | string | – | Optional angle narrowing within the niche. E.g. niche="Fitness & Health" + query="postpartum strength" returns only postpartum-strength templates, not generic gym. Templates are scored by query-token… |
| region | string | – | Optional 2-letter ISO country code (US, GB, BR, JP, IN, PH, etc.). Threads to YouTube Search regionCode + TikTok niche query. Reddit niche signals are global and ignore this param. Pass when the user… |
| window | string | – | Recency filter. Drops example videos older than the window. Note: TikTok hashtag-corpus rows often lack timestamps and are excluded when window is set — surfaces as a quality warning so callers can d… |
| Name | Type | Req | Description |
|---|---|---|---|
| credits_remaining | number | – | Credits remaining after this call |
| from_payg | boolean | – | Whether credits came from pay-as-you-go balance |
| from_subscription | boolean | – | Whether credits came from subscription |
| niche | string | – | The niche searched |
| templates | array | – | Ranked viral templates with hook patterns and example URLs |
No examples provided.
get_changes ~260
Detect what changed since the last saved baseline for a tracked creator. Runs a fresh analyze_account under the hood, compares against the most recent CreatorSnapshot, persists the new snapshot, and returns ONLY the meaningful shifts (format, viral DNA, engagement, hook pattern, topic pillars, outlier videos). Use when the user asks 'what changed with @creator', 'anything new', 'check this competitor again', 'what's different since last time', 'check my tracked creator', or 'has anything changed'. Requires a previously tracked creator (call analyze_account + watch_account first if there is no baseline yet). Costs 5 credits per call because the fresh analysis is genuine (not cached). Returns a top_action pointing at the single next tool worth calling given the detected change. Returns status='no_meaningful_change' honestly when nothing shifted — no fabricated deltas.
| Name | Type | Req | Description |
|---|---|---|---|
| handle | string | – | Creator handle (with or without @). Required if watch_id is not provided. |
| platform | string | – | Platform the tracked creator publishes on. Required if watch_id is not provided. |
| watch_id | string | – | Watch identifier returned by watch_account or list_watches. Preferred over (platform, handle) when you have it — the ownership check is exact. |
| Name | Type | Req | Description |
|---|---|---|---|
| changes | array | – | – |
| creator | string | – | – |
| credits_charged | number | – | – |
| current_snapshot_at | string | – | – |
| high_importance | number | – | – |
| meaningful_changes | number | – | Count of high + medium importance changes. |
| medium_importance | number | – | – |
| platform | string | – | – |
| previous_snapshot_at | string | – | – |
| snapshot_count | number | – | Total snapshots saved for this watch after this call. |
| status | string | – | changes_found = meaningful shifts detected; no_meaningful_change = fresh analysis ran, nothing shifted enough to matter; baseline_refreshed = prior snapshot used an incompatible schema, new baseline… |
| top_action | object | – | Single most useful next tool call given the detected changes. null when nothing meaningful shifted. |
No examples provided.
list_watches ~96
List every creator the authenticated user is tracking. Read-only, 0 credits. Returns each watch's id, platform, handle, when it was created + last updated, when the last snapshot was taken, and whether it's active. Does NOT return the snapshot payload itself — call watch_account (idempotent) to refresh a baseline. Use when the user asks 'what am I tracking', 'show my watches', 'list creators'.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| total | number | – | – |
| watches | array | – | – |
No examples provided.
match_voice ~115
Extract a creator's voice DNA from reference samples and rewrite a draft in their style. Requires at least 3 reference samples (video URLs or text). Returns voice profile (energy, humor, vocabulary, signature phrases), reusable prompt instructions, and the rewritten draft. Use when the user wants to write in another creator's style or match a specific voice.
| Name | Type | Req | Description |
|---|---|---|---|
| draft | string | yes | The text to rewrite |
| reference_samples | array | yes | At least 3 reference samples — TikTok/YouTube/Instagram URLs or raw text |
| Name | Type | Req | Description |
|---|---|---|---|
| credits_remaining | number | – | Credits remaining after this call |
| from_payg | boolean | – | Whether credits came from pay-as-you-go balance |
| from_subscription | boolean | – | Whether credits came from subscription |
| prompt_instructions | string | – | Reusable prompt to replicate this voice |
| rewritten_draft | string | – | The input draft rewritten in the matched voice |
| voice_profile | object | – | Extracted voice DNA profile |
No examples provided.
predict_virality ~109
Score a draft script for viral potential with adversarial verification. Returns a virality score, recommendation (ship/rework/no-go), viral DNA breakdown with evidence, attack vectors analysis, and calibration metrics. Use when the user has a finished draft and wants pre-publish verification. Pass either a script string or a video URL.
| Name | Type | Req | Description |
|---|---|---|---|
| niche | string | – | Niche context |
| script | string | yes | The draft script to predict on (or a video URL — auto-extracts transcript) |
| Name | Type | Req | Description |
|---|---|---|---|
| blueprint | object | – | Retention diagnosis with weak seconds identified |
| credits_remaining | number | – | Credits remaining after this call |
| from_payg | boolean | – | Whether credits came from pay-as-you-go balance |
| from_subscription | boolean | – | Whether credits came from subscription |
| share_reason | string | – | Why viewers would share this content |
| target_emotion | string | – | Primary emotion the content targets |
| viral_dna | object | – | Hook type, structure, emotional triggers breakdown |
| virality_score | number | – | Overall virality prediction (0-100) |
No examples provided.
score_hook ~124
Score a TikTok, Reels, or Shorts hook against proven viral patterns. Returns a 0-100 score, percentile rank, matched pattern, strengths, weaknesses, and three improved hook variations. Use when the user has a draft hook to validate, wants to compare alternatives, or needs feedback before publishing.
| Name | Type | Req | Description |
|---|---|---|---|
| niche | string | – | Optional niche context (e.g. "Beauty & Skincare", "Finance & Business") |
| platform | string | yes | Target platform — affects pattern matching |
| text | string | yes | The hook to score (3-200 chars typical) |
| Name | Type | Req | Description |
|---|---|---|---|
| breakdown | object | – | Sub-scores (0-100) for five quality dimensions |
| credits_remaining | number | – | Credits remaining after this call |
| from_payg | boolean | – | Whether credits came from pay-as-you-go balance |
| from_subscription | boolean | – | Whether credits came from subscription |
| pattern_match | string | – | Matched viral pattern name |
| percentile | number | – | Percentile rank vs all scored hooks |
| rewrites | array | – | Three rewritten versions at higher quality |
| score | number | – | Hook quality score (0-100) |
| strengths | array | – | What the hook does well |
| weaknesses | array | – | What could be improved |
| why | string | – | One-sentence verdict explaining the score |
No examples provided.
search_videos ~325
Search for short-form videos by keyword across TikTok or Instagram. Returns up to 20 videos ranked by engagement, with view counts, likes, shares, comments, hashtags, author info, and URLs. Use when the user asks to find videos about a topic or keyword. Supports optional filters for niche, minimum views, recency window, and region.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max videos to return after filtering. Default 12, max 20. |
| min_views | integer | – | Optional view-count floor. Default 0. |
| niche | string | – | Optional — only return videos whose description contains niche-related tokens. Loose niche strings work ("fitness", "Beauty & Skincare"). |
| platform | string | – | Which platform to search. "tiktok" (default) hits ScrapeCreators TikTok keyword search. "instagram" (2026-07-06) hits Instagram Reels search — note IG upstream ignores region/date_posted params, so r… |
| query | string | yes | Free-text search term. Examples: "morning routine", "iphone case", "passive income". |
| region | string | – | ISO country code (US, GB, BR, PH, JP, etc.). Note: corpus coverage varies by region — small regions may return zero results and a degraded quality flag. |
| window | string | – | Recency filter. Maps to the closest ScrapeCreators date bucket AND applies a client-side cutoff for defense-in-depth. |
| Name | Type | Req | Description |
|---|---|---|---|
| applied | object | – | Echo of the filters actually applied — useful for debugging when results look surprising |
| credits_remaining | number | – | Credits remaining after this call |
| filtered_count | number | – | Videos returned after filtering + cap |
| from_payg | boolean | – | – |
| from_subscription | boolean | – | – |
| quality | object | – | – |
| upstream_count | number | – | Videos returned by upstream before any filtering |
| videos | array | – | – |
No examples provided.
trend_pulse ~300
Research what is currently gaining traction in short-form content for a specific niche. Returns rising opportunities (formats, hooks, styles, topics) with growth signals, data sources, and saturated patterns to avoid. Use when the user asks what to post about, what's trending in a niche, or needs to validate a content idea against current trends. Supports 17 niches and optional region filtering.
| Name | Type | Req | Description |
|---|---|---|---|
| deadline_hours | integer | – | Optional (2026-07-06 magic-genie ritual): how many hours until the video posts. When set, each rising trend gets a trend_status (up-slope | plateau | fading | unknown) AND a deadline_verdict (safe |… |
| niche | string | – | One of the 17 supported niches. Loose names like "travel" or "fitness" are accepted but pass the canonical form when possible. Omit for broadly applicable trends. |
| region | string | – | Optional 2-letter ISO country code (US, GB, BR, JP, IN, PH, etc.). Threads to Google Trends geo + YouTube regionCode. Defaults to US when omitted. Reddit signals are global and ignore this param. |
| Name | Type | Req | Description |
|---|---|---|---|
| credits_remaining | number | – | Credits remaining after this call |
| from_payg | boolean | – | Whether credits came from pay-as-you-go balance |
| from_subscription | boolean | – | Whether credits came from subscription |
| niche | string | – | The niche these trends apply to |
| rising | array | – | Rising opportunities (format/hook/style) with qualitative growth labels + signal_strength numeric anchor (0-1) + suggestions |
| saturated | array | – | Saturated patterns to avoid |
No examples provided.
viral_remix ~364
Take a viral video and produce a fresh script that mirrors its structure and energy pattern for a new topic. Returns the extracted formula, scene-by-scene script with voiceover and visuals, camera directions, and text overlays. Use when the user finds a video they want to replicate the structure of. Pass either a video URL (TikTok, YouTube, or Instagram) or a transcript directly. When promoting a specific product, ALWAYS pass target_product + verified_product_facts so the generator does not fabricate product details.
| Name | Type | Req | Description |
|---|---|---|---|
| my_topic | string | – | DEPRECATED alias for target_topic. Legacy clients only. Normalized internally. |
| niche | string | – | Optional niche hint |
| platform | string | – | Target platform for the remix. Adjusts pacing and CTA style if provided. |
| source_url | string | – | TikTok/YouTube/Instagram URL — transcript will be auto-extracted |
| target_product | string | – | The product the remix should promote. When provided, the generator will NOT invent product names, prices, timelines, features, or customer stories. Combined with verified_product_facts, this forces o… |
| target_topic | string | – | What the remix should be about. Default: same niche as original. |
| transcript | string | – | Pre-extracted transcript (alternative to source_url, faster) |
| verified_product_facts | array | – | Facts the generator is allowed to cite about target_product (e.g. "runs inside ChatGPT and Claude", "12 tools for viral research"). Every specific product claim in the generated script is checked aga… |
| Name | Type | Req | Description |
|---|---|---|---|
| camera_shots | array | – | Phone-native camera direction per scene |
| credits_remaining | number | – | Credits remaining after this call |
| cta_archetype | string | – | Which CTA archetype the generator picked. Comment_gate is the failure-mode default for AI script generators; rotation tells you whether the prompt is working. |
| extracted_formula | string | – | The viral DNA formula extracted from the source |
| fresh_script | object | – | Complete scene-by-scene script mirroring the source structure |
| from_payg | boolean | – | Whether credits came from pay-as-you-go balance |
| from_subscription | boolean | – | Whether credits came from subscription |
| overlays | array | – | Text overlay suggestions per scene |
| structural_skeleton | string | – | Which structural skeleton the generator used (confession_to_result, mistake_to_correction, etc). Surfaces rotation across the fleet. |
| ugc_authenticity | object | – | Tripwire for ad-shaped drift. Detected via regex on the produced script, not the model self-grade. If level=ad_leaning, surface to the user before shipping. |
| verify_hook | object | – | The hook plus a suggested follow-up: the caller may pass it to score_hook for a structurally-independent score (the script generator deliberately does NOT self-rate). Informational only, not an instr… |
No examples provided.
watch_account ~219
Start tracking a creator so future calls can detect what changed. Creates a durable CreatorWatch + a baseline CreatorSnapshot capturing the creator's current viral DNA scores, format fingerprint, and top recent videos. Use when the user says 'track', 'watch', 'follow', 'keep an eye on' a creator/channel/handle. Idempotent — calling 'watch @same' twice with a fresh baseline in place returns the existing watch with credits_charged=0. Cost: 0 credits when a fresh existing watch snapshot or a compatible recent analyze_account cache can be reused. Otherwise a fresh baseline invokes analyze_account and costs 5 credits — this can happen even for an already-existing watch once freshness expires. Reuses the same 'analyze' permission as analyze_account — no new OAuth scope, no re-consent required.
| Name | Type | Req | Description |
|---|---|---|---|
| handle | string | yes | Creator handle (with or without @ prefix). Examples: "@mrbeast", "mrbeast". |
| platform | string | yes | Platform the creator publishes on. Same platforms as analyze_account. |
| Name | Type | Req | Description |
|---|---|---|---|
| baseline_created_at | string | – | ISO timestamp of the baseline snapshot |
| baseline_source | string | – | watch_snapshot = existing CreatorWatch already had a fresh snapshot (0 credits); analysis_cache = recent analyze_account response reused to build a new baseline (0 credits); fresh = analyze_account i… |
| creator | string | – | Normalized "@handle" the watch is stored under |
| credits_charged | number | – | – |
| data_age_days | number | – | Age in days of the newest video in the baseline |
| message | string | – | – |
| platform | string | – | – |
| snapshot_count | number | – | Total snapshots stored for this watch so far |
| status | string | – | – |
| watch_id | string | – | – |
No examples provided.
What is the io.github.khan-ashifur/hooklayer MCP server?
io.github.khan-ashifur/hooklayer is an MCP server listed in the public MCP registry as io.github.khan-ashifur/hooklayer. Viral-content intelligence for AI agents, 7 read-only MCP tools, evidence-layer scoring. This page covers its hosted endpoint (https://hooklayer.dev/api/mcp).
Is the io.github.khan-ashifur/hooklayer MCP server safe to use?
io.github.khan-ashifur/hooklayer scores 87 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 io.github.khan-ashifur/hooklayer MCP server expose?
io.github.khan-ashifur/hooklayer exposes 12 tools: analyze_account, watch_account, get_changes, list_watches, score_hook, and 7 more. Their descriptions and schemas cost roughly 3,360 tokens of context every time the server is loaded.
Does the io.github.khan-ashifur/hooklayer MCP server require authentication?
Yes. io.github.khan-ashifur/hooklayer asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the io.github.khan-ashifur/hooklayer MCP server still maintained?
io.github.khan-ashifur/hooklayer is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.