Server data from the Official MCP Registry
Viral-content intelligence for AI agents — 7 read-only MCP tools, evidence-layer scoring.
Viral-content intelligence for AI agents — 7 read-only MCP tools, evidence-layer scoring.
Remote endpoints: streamable-http: https://hooklayer.dev/api/mcp
Valid MCP server (2 strong, 1 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry.
7 tools verified · Open access · 1 issue found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Remote Plugin
No local installation needed. Your AI client connects to the remote endpoint directly.
Add this to your MCP configuration to connect:
{
"mcpServers": {
"io-github-khan-ashifur-hooklayer": {
"url": "https://hooklayer.dev/api/mcp"
}
}
}From the project's GitHub README.
Viral-content intelligence for AI agents. Drop the Hooklayer MCP server into Claude Desktop, Cursor, n8n, or any HTTP MCP client and your agent gets 7 read-only tools for scoring hooks, remixing viral videos, surfacing live trends, and analyzing TikTok creators. The flagship analyze_account tool includes a recommended_chain field with suggested follow-up calls the agent can review and execute.
7 read-only tools · all return structured JSON · no mutations · no side effects
v1.1.0 (2026-05-14): The evidence layer ships. Every score includes
signals[]with cited evidence, awould_fail_becausecounterfactual, and aqualityhealth field.predict_viralityruns an independent adversarial check.analyze_account.recommended_chainsteps now exposeconfidence,cost,action_class(authority taxonomy), andexpected_output. See CHANGELOG.md for the full ship.
Claude Desktop doesn't natively support remote HTTP MCP servers — it needs the mcp-remote bridge. Two ways to install:
Option 1 — Custom Connector (easiest, no config file edit)
In Claude's web/desktop UI: Settings → Connectors → Add custom connector → paste this URL:
https://hooklayer.dev/api/mcp
Claude.ai will walk you through OAuth (no manual key paste). Done.
Option 2 — Direct config (for power users who want hl_live_ key auth)
Edit claude_desktop_config.json:
~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.json{
"mcpServers": {
"hooklayer": {
"command": "npx",
"args": [
"-y",
"mcp-remote@0.1.38",
"https://hooklayer.dev/api/mcp",
"--header",
"Authorization:Bearer hl_live_..."
]
}
}
}
Get your free hl_live_ key at https://hooklayer.dev/auth/signup — 100 lifetime credits, no card required.
Restart Claude Desktop. The 7 Hooklayer tools appear in the 🔌 connector list.
~/.cursor/mcp.json:
{
"mcpServers": {
"hooklayer": {
"url": "https://hooklayer.dev/api/mcp",
"transport": "http",
"headers": {
"Authorization": "Bearer hl_live_..."
}
}
}
}
In your workflow, add an MCP Client node and configure as a remote HTTP MCP server:
https://hooklayer.dev/api/mcpHTTPAuthorization: Bearer hl_live_...All 7 tools appear in the node's "Tool" dropdown.
Hooklayer is fully OAuth 2.1 compliant — discovery, Dynamic Client Registration, PKCE, refresh token rotation. MCP clients that prefer OAuth over API keys work out of the box.
Discovery endpoints (no auth required, machine-readable):
# Authorization server metadata (RFC 8414)
curl https://hooklayer.dev/.well-known/oauth-authorization-server
# Protected resource metadata (RFC 9728)
curl https://hooklayer.dev/.well-known/oauth-protected-resource
Dynamic Client Registration (create a client without a manual signup form):
curl -X POST https://hooklayer.dev/oauth/register \
-H "Content-Type: application/json" \
-d '{
"client_name": "Your MCP client",
"redirect_uris": ["https://yourapp.com/oauth/callback"]
}'
# Returns: client_id, client_secret (for confidential clients)
Hitting tools/call without auth returns 401 plus a WWW-Authenticate header pointing at the resource metadata — Claude.ai, Cursor, and other MCP clients use this to auto-discover the OAuth flow.
Any HTTP MCP client. Protocol negotiates 2024-11-05 (broadest compat) or 2025-06-18 (Streamable HTTP + structuredContent).
# Quick test — initialize handshake works without auth:
curl -X POST https://hooklayer.dev/api/mcp \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize"}'
| Tool | Credits | What it does |
|---|---|---|
analyze_account | 5 | TikTok creator deep dive: viral DNA scores, format fingerprint, top 5 videos, content gaps, recommended_chain with suggested follow-up tools. |
score_hook | 1 | Score any hook 0-100 against proven viral patterns. Returns 3 rewrites at higher quality. |
viral_remix | 3 | URL or transcript → fresh script with mirrored viral DNA. Scene-by-scene with camera shots. |
trend_pulse | 1 | Real-time rising opportunities + saturated patterns per niche. 12-hour cache. |
find_viral_template | 1 | Niche-fit ranked templates with hook patterns + example URLs. |
match_voice | 2 | Extract a creator's voice DNA from 3+ samples, rewrite a draft in their style. |
predict_virality | 2 | Score a draft script for viral potential before publishing. Retention diagnosis. |
Full schemas + curl examples: https://hooklayer.dev/docs
analyze_account returns a recommended_chain field with suggested follow-up tools and pre-filled parameters. The agent decides whether and when to execute them:
{
"viral_dna_score": 87,
"steal_map": [...],
"recommended_chain": [
{
"tool": "match_voice",
"params": {
"draft": "<<<USER_DRAFT>>>",
"reference_samples": ["https://tiktok.com/...", "...", "..."]
},
"reason": "High-signal voice DNA — consistent across top 5 videos"
},
{
"tool": "trend_pulse",
"params": { "niche": "challenge_videos" },
"reason": "Verify their formula maps to current trends"
},
{
"tool": "viral_remix",
"params": { "source_url": "https://tiktok.com/..." },
"reason": "Their #2 video has the highest copyable structure"
}
]
}
The agent can review these suggestions and call the recommended tools if appropriate. Each tool still requires explicit invocation — nothing runs automatically without agent/user consent.
examples/typescript-example.ts — TypeScript usage via the MCP SDKexamples/python-example.py — Python usage via anthropic-mcp clientexamples/curl-test.sh — Raw curl tests for every endpointFull pricing: https://hooklayer.dev/pricing
Hosted MCP server (no stdio install needed):
Your agent (Claude/Cursor/n8n)
│
│ JSON-RPC 2.0 over HTTP
▼
https://hooklayer.dev/api/mcp
│
├── initialize / ping / tools/list (no auth)
└── tools/call (Bearer hl_live_*)
│
└── Routes internally to /v1/* REST endpoints
100K+ analyzed viral videos
ScrapeCreators + Whisper + Sonnet pipeline
Source code for the hosted server lives at hooklayer.dev (closed source — the analysis pipeline is the moat). This repo holds the public client docs, examples, and config snippets.
/.well-known/oauth-authorization-serverAll 7 tools are read-only. They analyze, score, and generate content — none of them create, modify, or delete any user data, accounts, or external resources. Every tool carries readOnlyHint: true and destructiveHint: false in its MCP annotations.
Authentication: tools/call requires a Bearer token (hl_live_* API key or OAuth 2.1 access token). Public methods (initialize, ping, tools/list) work without auth so MCP clients can handshake and discover tools before authentication.
recommended_chain is advisory only. The analyze_account response includes suggested follow-up tools with pre-filled parameters. These are data — the agent and user decide whether to execute them. No tool call ever triggers additional tool calls server-side.
Data handling: Hooklayer processes the inputs you send (handles, hooks, scripts, URLs) to return analysis results. We do not store your content beyond the request lifecycle except for anonymous usage metrics.
To report a security issue: GitHub Issues or email security@hooklayer.dev.
MIT — see LICENSE.
The MCP client examples and config snippets in this repo are MIT. The hosted Hooklayer service at hooklayer.dev is a commercial product with the pricing tiers listed above.
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
by mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.