MCP
Analyze how your spokesperson actually lands
Import their appearances, extract key quotes, and check delivered-message vs intended-message drift.
deep_contextrun_youtube_toolThe problem
The messaging doc says three pillars, approved language, bridge phrases for the hard questions. Then your spokesperson does eleven interviews, and somewhere between the doc and the delivery, drift happens: pillar two never comes up, an off-script analogy becomes their favorite line, and the hedge word they added to the revenue message is now in every telling. Nobody decided any of this. It accumulated.
Comms teams review appearances one at a time, warm from the studio — which catches disasters but never drift, because drift is invisible in any single performance. It only shows across the body of work: what's actually said, tallied against what was supposed to be said, across every appearance this quarter.
How veridive MCP helps
deep_context runs the drift analysis over your archived appearances (see the press-tour tracking use case for the collection habit): scope the quarter's imports and ask the audit questions — which pillars actually got airtime? what language replaced the approved phrasing? how does the spokesperson handle the acquisition question across tellings? Answers come back cited to the exact chunks, so the review runs on evidence.
run_youtube_tool's key-quotes supplies the per-appearance layer: the lines that actually landed — which, compared against the messaging doc, is the drift measurement itself. The output isn't a gotcha; it's the input media training never has: this is what you actually say, here are the eleven moments, and this is the line we're promoting to official because your version tests better than ours.
How to run it
- 1Connect veridive MCP
One-time setup: add the veridive MCP server to Claude, ChatGPT, Cursor or any MCP client and generate your API key. Takes about two minutes.
- 2Extract what was actually said
Key quotes from each archived appearance — the delivered message, appearance by appearance.
Pull key quotes from each of <spokesperson>'s imported appearances this quarter — the main messages as actually delivered. - 3Audit against the doc
Scope deep_context across the quarter's imports and tally delivery against intention — pillar coverage, language drift, hard-question handling.
Our intended messages were: <pillars/approved language>. Across the imported appearances: which got delivered, which never came up, and what off-script language recurs? Cite the moments. - 4Feed the findings forward
The drift report becomes next quarter's media-training input — and sometimes the messaging doc's revision.
Summarize the drift: pillars underdelivered, recurring off-script lines worth adopting or retiring, and the three moments to review in training — with citations.
Problems it solves
- Message drift is invisible per-appearance and only exists across the body of work nobody reviews whole.
- Media training runs on anecdote and memory instead of the spokesperson's actual delivered record.
- Off-script lines — good and bad — spread unnoticed until they're the de facto message.
- "Did we ever actually say the second pillar out loud?" has no answer without the tally.
Why it's valuable
- Drift becomes measurable: intended versus delivered, tallied across the quarter, cited.
- Training sessions start from the spokesperson's own moments, not hypotheticals.
- The good drift gets found too — the off-script line that outperforms the approved one.
- The messaging doc stops being fiction: it converges with what's actually said, deliberately.
Example prompts
Key quotes from each of <spokesperson>'s imported appearances this quarter.Intended: <pillars>. Across the imports: delivered vs missed vs off-script recurring language? Cited.Drift summary for training: underdelivered pillars, lines to adopt/retire, three moments to review.FAQ
What does this need in place first?
An archive of the spokesperson's appearances in your library — the press-tour tracking use case is the collection habit. deep_context then scopes the analysis to those imports (up to 20 per question).
Is this for catching the spokesperson out?
It works much better as a gift: concrete moments instead of vague feedback, and explicit recognition when their instincts beat the doc. Teams that frame it as calibration get spokespeople who ask for the report.
How often should the audit run?
Quarterly matches how messaging docs evolve; after a major launch or crisis, run an off-cycle pass — that's when drift moves fastest.
Related use cases
Sweep your executive's appearances, archive them, and keep the quotes-on-record list current.
Import a target's exec interviews and ask pointed questions — how do they talk about attrition, customers, each other?
Feed the exec's actual talk transcripts in, then draft posts that sound like them because they're built from them.
Run this in your own assistant
Connect the veridive MCP server to Claude, ChatGPT or Cursor and paste the prompts above — setup takes about two minutes.