Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

PrePublish - YouTube script QA

REMOTE · MCP.PREPUBLISH.AI · SCANNED SEP 20

Audit a YouTube script before recording: hook, pacing, drop-off risk, copy-paste rewrites.

+3 this week 70 Trust /100
Trust breakdown (7 categories)

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 Security63
Transport & Reachability100
Schema Quality & AI Usability69
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1332 tokens (~222/item across 6 items; 6 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 Management33
  • Stability observed for 10 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 7 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
Install

How do I install the PrePublish - YouTube script QA MCP server?

PrePublish - YouTube script QA is a hosted endpoint at https://mcp.prepublish.ai/, 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 · mcp.prepublish.ai

# add to Claude Code
claude mcp add --transport http ai-prepublish-script-audit 'https://mcp.prepublish.ai/'
// .cursor/mcp.json
{
  "mcpServers": {
    "ai-prepublish-script-audit": {
      "url": "https://mcp.prepublish.ai/"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "ai-prepublish-script-audit": {
      "type": "http",
      "url": "https://mcp.prepublish.ai/"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.ai-prepublish-script-audit]
url = "https://mcp.prepublish.ai/"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-prepublish-script-audit": {
      "type": "remote",
      "url": "https://mcp.prepublish.ai/",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add ai-prepublish-script-audit --url 'https://mcp.prepublish.ai/' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  ai-prepublish-script-audit:
    url: "https://mcp.prepublish.ai/"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "ai-prepublish-script-audit": {
      "Transport": "http",
      "Url": "https://mcp.prepublish.ai/"
    }
  }
}
# add to Vellum
assistant mcp add ai-prepublish-script-audit -t streamable-http -u 'https://mcp.prepublish.ai/'
// mcp.json
{
  "mcpServers": {
    "ai-prepublish-script-audit": {
      "type": "http",
      "url": "https://mcp.prepublish.ai/"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 20 Sept 26 0
    • “audit_hook” reworded the description of “email” cosmetic
    • “audit_script” reworded the description of “email” cosmetic

    2 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.

  • 18 Sept 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.

  • 16 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Sept 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “audit_script” rewrote its description, which is the text the model reads security
    • Tool “script_runtime” rewrote its description, which is the text the model reads security
    • Tool “get_audit” changed its title: Collect a PrePublish audit by id → Collect a Prepublish audit by id cosmetic
  • 12 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Sept 26 0
    • Stability: unverified → 0.03 functional
  • 10 Sept 26 66

    First indexed and scored.

Diagnostics

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://mcp.prepublish.ai

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.prepublish.ai CN=YR1,O=Let's Encrypt,C=US 10 Sept 2026 9 Dec 2026 RSA 4096 SHA256-RSA 6f3c135df811013de14770e9ea48594c1df
SANs: mcp.prepublish.ai
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
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 mcp.prepublish.ai. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 3799 8 Verified
prepublish.ai. absent 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=31536000; includeSubDomains
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://cloud.umami.is https://analytics.prepublish.ai https://www.clarity.ms https://scripts.clarity.ms https://analytics.ahrefs.com https://www.redditstatic.com https://static.ads-twitter.com https://analytics.twitter.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob: https:; font-src 'self' data:; connect-src 'self' https://api.prepublish.ai https://cloud.umami.is https://analytics.prepublish.ai https://*.prepublish.ai https://analytics.ahrefs.com https://www.clarity.ms https://*.clarity.ms https://*.reddit.com https://www.redditstatic.com https://analytics.twitter.com https://t.co; frame-src 'self' https://analytics.twitter.com https://t.co; frame-ancestors 'none'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.prepublish.ai Verified 200
http (plaintext) http://mcp.prepublish.ai HTTPS enforced 301 https://mcp.prepublish.ai/
MCP tools · 6 exposed · ~1,215 tokens

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 →

Tool Tokens
audit_hook ~235

Score just the opening lines of a YouTube script: how much attention each sentence pulls, whether it opens a curiosity gap, how far away the payoff sits, plus the top issues and rewritten alternatives. Choose this when the user shares only a hook or opening paragraph, or wants a fast second opinion before auditing a whole draft. Cheaper and narrower than audit_script. This is a text-only check of an unrecorded script. It maps relative attention risk inside the draft. It does not measure or predict published YouTube retention, and it cannot account for delivery, editing, thumbnail, topic or distribution.

NameTypeReqDescription
emailstringOnly needed once the free anonymous hook check for the day is used. Ask the user; never invent it. When the caller is authenticated with a Prepublish API key the result comes back in the conversation…
hook_textstringyesThe opening lines exactly as written, ideally the first 15 to 30 seconds of speech.
nichestringChannel niche, only if the user said it. Sharpens the comparison.

No output schema declared.

No examples provided.

audit_script ~354

Run Prepublish's full audit on a YouTube script the user has already written. Returns hook, structure and pacing scores, a script-level attention-risk map naming the passages most likely to lose viewers, and a copy-paste rewrite for each flagged passage. Choose this when the user has a finished or near-finished draft and wants to know what is weak before they record. Do not use it to generate a script, to review a published video, or to check grammar. A free result is released by email, so ask the user for an address rather than guessing one. This is a text-only check of an unrecorded script. It maps relative attention risk inside the draft. It does not measure or predict published YouTube retention, and it cannot account for delivery, editing, thumbnail, topic or distribution.

NameTypeReqDescription
audiencestringTarget audience, only if the user said it.
categorystringVideo category, only if the user said it.
emailstringWhere the free result is sent. Required for every anonymous audit: the backend rejects the request without it. Ask the user; never invent it. When the caller is authenticated with a Prepublish API ke…
script_textstringyesThe script text as the user wrote it. Paste it verbatim; do not rewrite, summarise or clean it first.
video_duration_secondsintegerIntended runtime in seconds, only if the user stated one. Used for pacing; never assumed.
video_titlestringyesThe title the user plans to publish under. The audit checks whether the script delivers this promise.

No output schema declared.

No examples provided.

check_authenticity ~150

Check a script against YouTube's inauthentic-content expectations: whether it reads as mass-produced, templated or repetitive, which signals fire, and what to change. Returns a score, a risk level, the firing signals with quotes, and remediation steps. Choose this when the user worries about reused content, AI-sounding scripts, or a channel that repeats a formula. This reports text-level signals only; it is not a monetisation decision and does not speak for YouTube.

NameTypeReqDescription
script_textstringyesThe script text as the user wrote it. Paste it verbatim; do not rewrite, summarise or clean it first.
video_titlestringyesThe planned title.

No output schema declared.

No examples provided.

get_audit ~127

Fetch the current state of an audit that was started earlier, using the analysis_id that audit_script returned. Use this when a previous audit was still running, or when the user refers back to an audit from earlier in the conversation. It performs no new analysis and costs nothing. This is a text-only check of an unrecorded script. It maps relative attention risk inside the draft. It does not measure or predict published YouTube retention, and it cannot account for delivery, editing, thumbnail, topic or distribution.

NameTypeReqDescription
analysis_idstringyesThe analysis_id returned by audit_script.

No output schema declared.

No examples provided.

policy_preflight ~174

Check a script before recording for the YouTube policy categories it may touch: which category families are implicated, the consequence family for each, a verdict and flag counts. Each category cites YouTube's own published policy page. Choose this when the user is writing about sensitive subject matter and asks whether it is safe to monetise. The quoted passages and their suggested rewrites are part of the paid audit, so the free result may return counts with locked quotes. It reports risk against published policy text; it is not a monetisation guarantee and does not speak for YouTube.

NameTypeReqDescription
scriptstringyesThe script text as written, at least 200 characters. Below that there is not enough context for a policy read.
titlestringThe planned title, if the user has one. Titles are checked too.

No output schema declared.

No examples provided.

script_runtime ~175

Convert a word count, or a pasted script, into a spoken runtime range, and convert a target runtime back into a word budget. Rates come from Prepublish's own measurement of 349 videos: 25th percentile 160 words per minute, median 181, 75th percentile 201. Choose this for "how long will this script run" or "how many words for a ten-minute video". It is arithmetic on speaking rate only: it excludes pauses, B-roll and demonstrations, so a finished edit usually runs longer.

NameTypeReqDescription
script_textstringA script to count. Provide this or word_count or target_minutes.
target_minutesnumberA target runtime in minutes, to convert into a word budget.
word_countintegerA word count, if the user already knows it.

No output schema declared.

No examples provided.

Common questions

What is the PrePublish - YouTube script QA MCP server?

PrePublish - YouTube script QA is an MCP server listed in the public MCP registry as ai.prepublish/script-audit. Audit a YouTube script before recording: hook, pacing, drop-off risk, copy-paste rewrites. This page covers its hosted endpoint (https://mcp.prepublish.ai).

Is the PrePublish - YouTube script QA MCP server safe to use?

PrePublish - YouTube script QA scores 70 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 PrePublish - YouTube script QA MCP server expose?

PrePublish - YouTube script QA exposes 6 tools: audit_script, get_audit, audit_hook, check_authenticity, policy_preflight, script_runtime. Their descriptions and schemas cost roughly 1,215 tokens of context every time the server is loaded.

Does the PrePublish - YouTube script QA MCP server require authentication?

No. We connected to PrePublish - YouTube script QA without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the PrePublish - YouTube script QA MCP server still maintained?

PrePublish - YouTube script QA 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.