Daily Studio Teleprompter MCP server
app.dailystudio/teleprompterdailystudio.appstreamable-httpv1.0.0Scanned
Send a shoot's worth of scripts to the Daily Studio teleprompter on iPhone, in one link.
12 tools: 2 can delete or cancel things, 1 do something that can't be undone, 4 change things and 5 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 2
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here can delete or cancel things and 1 does something that can't be undone. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Daily Studio Teleprompter MCP server can do
The Daily Studio Teleprompter MCP server is published by dailystudio.app, a domain the MCP Registry verified. It has 12 tools. It can delete or cancel things (2 tools: archive_planned_scripts and cancel_scheduled_post), do things that cannot be undone, such as sending, paying or publishing (send_script_to_teleprompter) and create or change data (4 tools: add_scripts_to_plan, edit_planned_scripts, reorder_planned_scripts and retry_scheduled_post). 5 tools only read.
1 tool brings in text other people can write (list_scheduled_posts); 2 tools can send data out of your system (send_script_to_teleprompter and retry_scheduled_post).
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 12, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
12 tools
Deletes or cancels 2Claude Code: deny
archive_planned_scriptsArchive scripts out of the user's working plan, by id — or restore archived ones with `restore: true`.1 finding
Why it is in this group
- The name "archive_planned_scripts" says "archive": a word for removing or ending something.
- The server marks it not destructive (destructiveHint: false), but an annotation never lowers a class.
Findings
- Warn
The server marks "archive_planned_scripts" not destructive (destructiveHint: false), and its own name, description or input give the class "destructive".
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "archive_planned_scripts" says "archive": a word for removing or ending something.
Description, as the server wrote it Archive scripts out of the user's working plan, by id — or restore archived ones with `restore: true`. Archiving is reversible and keeps the script and any recorded video; it is the right way to clear finished or shelved work. Permanent deletion is deliberately not available to assistants — the user does that themselves.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
cancel_scheduled_postCancel one post that is waiting to go out, by id from list_scheduled_posts.No findings
Why it is in this group
- The name "cancel_scheduled_post" says "cancel": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Cancel one post that is waiting to go out, by id from list_scheduled_posts. Only works while the post is still waiting; the take becomes approvable again. Confirm with the user before calling this — it withdraws something they approved.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
Can't be undone 1Claude Code: ask
send_script_to_teleprompterTurn one or more finished video scripts into a single one-tap link that opens the user's Daily Studio app with the script(s) loaded into the teleprompter and the right platform saf…Can send data outNo findings
Why it is in this group
- The name "send_script_to_teleprompter" says "send": a word for sending, and what is sent cannot be taken back.
What it can reach
- outboundThe name "send_script_to_teleprompter" says "send": it sends or publishes something to other people.
Description, as the server wrote it Turn one or more finished video scripts into a single one-tap link that opens the user's Daily Studio app with the script(s) loaded into the teleprompter and the right platform safe-zones selected, ready to record. For one script use `text`; for a batch the user will record back-to-back (a day's 3-4 videos, or a whole content plan — up to 100), use `scripts` — they land as an in-app shoot queue in order, and ONE link carries them all. Call this only once the scripts are final. Returns a link the user taps on their iPhone; on a desktop it opens a page with a QR code to scan.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
Changes things 4Claude Code: ask
add_scripts_to_planPut finished talking-head scripts into the user's Daily Studio content plan, each with the day it should go out.No findings
Why it is in this group
- The name "add_scripts_to_plan" says "add": a word for a change.
Description, as the server wrote it Put finished talking-head scripts into the user's Daily Studio content plan, each with the day it should go out. Use this when the user asks you to PLAN — a week, a month, a series — rather than to hand them something to record right now. The plan lives on their account: it shows up in the app, on dailystudio.app/plan, and stays there. Calling this twice with the same scripts is safe; duplicates are skipped. Requires a connected Daily Studio account with the plan turned on. To record something immediately, use `send_script_to_teleprompter` instead — that is a delivery, this is a plan. Default to about 45 seconds of natural speech directly to camera: a hook, one clear idea and a short closing. Preserve the creator's voice and verified facts.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
edit_planned_scriptsChange scripts already in the user's Daily Studio content plan, by id and in bulk: move them to other days, group them into collections, retitle or rewrite them.No findings
Why it is in this group
- The name "edit_planned_scripts" says "edit": a word for a change.
Description, as the server wrote it Change scripts already in the user's Daily Studio content plan, by id and in bulk: move them to other days, group them into collections, retitle or rewrite them. This is the tool for 'these contents go on these days, grouped like this' when the content already exists — read the plan first with list_planned_scripts, then send one call with all the changes. Only the fields you send change; one bad entry never drops the batch.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
reorder_planned_scriptsSet the order the user's camera walks through their scripts — pass ids first-to-record first.No findings
Why it is in this group
- The description's first verb is "set": a word for a change.
Description, as the server wrote it Set the order the user's camera walks through their scripts — pass ids first-to-record first. Scripts you leave out keep their current order after the ones you name. Use it when the user says what to shoot first, or after planning a batch that should be recorded in sequence.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
retry_scheduled_postPut one failed post back in the queue, due now — by id from list_scheduled_posts.Can send data outNo findings
Why it is in this group
- The name "retry_scheduled_post" says "post": a word for a change.
What it can reach
- outboundThe name "retry_scheduled_post" says "post": it sends or publishes something to other people.
Description, as the server wrote it Put one failed post back in the queue, due now — by id from list_scheduled_posts. Use it after the cause in the failure sentence is fixed (say, a reconnected account). The post goes out within about five minutes.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 5Show 5 read-only tools
get_planned_scriptsRead the full text of specific scripts in the user's content plan, by id — the words themselves, not just titles.No findings
Why it is in this group
- The name "get_planned_scripts" says "get": a word for reading.
Description, as the server wrote it Read the full text of specific scripts in the user's content plan, by id — the words themselves, not just titles. Use it before rewriting or reviewing a script, or when the user asks about one ('check the hook on Tuesday's'). Up to 20 per call.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_collectionsList the collections (piles) the user already groups their scripts into, with counts.No findings
Why it is in this group
- The name "list_collections" says "list": a word for reading.
Description, as the server wrote it List the collections (piles) the user already groups their scripts into, with counts. Call it before grouping anything so you reuse their existing names instead of inventing near-duplicates.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_connected_accountsList the social accounts the user has connected to Daily Studio, so you know where a video could be published and under which handle.No findings
Why it is in this group
- The name "list_connected_accounts" says "list": a word for reading.
Description, as the server wrote it List the social accounts the user has connected to Daily Studio, so you know where a video could be published and under which handle. Requires a connected Daily Studio account — the first time you call this, the user is asked to connect one, and the call is retried automatically afterwards. Nothing is published by this tool.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_planned_scriptsRead what is already in the user's Daily Studio content plan — each script's id, title, collection, the day it goes out, its place in the shoot order, and how far it has got (writt…No findings
Why it is in this group
- The name "list_planned_scripts" says "list": a word for reading.
Description, as the server wrote it Read what is already in the user's Daily Studio content plan — each script's id, title, collection, the day it goes out, its place in the shoot order, and how far it has got (written, recorded, uploaded, scheduled, published, or failed). Call this before adding to a plan so you do not repeat what is there, before editing so you hold real ids, and whenever the user asks what they have coming up. Nothing is changed by this tool.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_scheduled_postsRead what the user has approved for publishing and what happened to it: waiting, going up now, published (with the link), failed (with the reason in plain words), or cancelled.Reads text others writeNo findings
Why it is in this group
- The name "list_scheduled_posts" says "list": a word for reading.
What it can reach
- untrusted-inputThe name "list_scheduled_posts" says "list" and "post": it reads posts, which other people can write.
Description, as the server wrote it Read what the user has approved for publishing and what happened to it: waiting, going up now, published (with the link), failed (with the reason in plain words), or cancelled. Call it when the user asks 'did my post go out?' or 'why not?'. Nothing is changed by this tool, and new posts cannot be scheduled from here.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out2
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:29 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 7
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://dailystudio.app/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://dailystudio.app
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- yes
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 7 tools that change things (2 destructive, 1 irreversible, 4 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://dailystudio.app/mcp: tools/list returned 12 tools to an anonymous client, including archive_planned_scripts (destructive), cancel_scheduled_post (destructive), send_script_to_teleprompter (irreversible), add_scripts_to_plan (write), edit_planned_scripts (write) and 2 more
Findings
Matches of fixed checks, with the text they matched.
The server marks "archive_planned_scripts" not destructive (destructiveHint: false), and its own name, description or input give the class "destructive".
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "archive_planned_scripts" says "archive": a word for removing or ending something.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http teleprompter https://dailystudio.app/mcpclaude mcp add --transport http teleprompter https://dailystudio.app/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__teleprompter__list_connected_accounts",
"mcp__teleprompter__list_planned_scripts",
"mcp__teleprompter__get_planned_scripts",
"mcp__teleprompter__list_collections",
"mcp__teleprompter__list_scheduled_posts"
],
"ask": [
"mcp__teleprompter__send_script_to_teleprompter",
"mcp__teleprompter__add_scripts_to_plan",
"mcp__teleprompter__edit_planned_scripts",
"mcp__teleprompter__reorder_planned_scripts",
"mcp__teleprompter__retry_scheduled_post"
],
"deny": [
"mcp__teleprompter__archive_planned_scripts",
"mcp__teleprompter__cancel_scheduled_post"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as teleprompter. Review it before you use it.
Capability tags behind 3 rules
- mcp__teleprompter__send_script_to_teleprompter outbound
- mcp__teleprompter__list_scheduled_posts untrusted-input
- mcp__teleprompter__retry_scheduled_post outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/app.dailystudio/teleprompter/verify?hash=080c347be155589e5868ec3ff89e2000256d703b426b4beaa39dec50171ecfed" | jq -e '.changed == false'Pinned hash 080c347be155, from Nov 12, 2026, 00:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/app.dailystudio/teleprompter/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/app.dailystudio/teleprompter)Source: MCP Registry. Synced Oct 21, 2026, 17:44 UTC.
Daily Studio Teleprompter MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Daily Studio Teleprompter MCP server safe?
- No scan can promise that. What its definitions show: 12 tools, 7 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Daily Studio Teleprompter MCP server delete data?
- Yes. 2 tools can delete, cancel or revoke something: archive_planned_scripts and cancel_scheduled_post.
Can the Daily Studio Teleprompter MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: send_script_to_teleprompter.
What tools does the Daily Studio Teleprompter MCP server have?
- 12 tools: 2 destructive, 1 irreversible, 4 write, 5 read. archive_planned_scripts, cancel_scheduled_post, send_script_to_teleprompter, add_scripts_to_plan, edit_planned_scripts, reorder_planned_scripts, retry_scheduled_post, list_connected_accounts and 4 more.
Does the Daily Studio Teleprompter MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Daily Studio Teleprompter MCP server send data to outside services?
- 2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): send_script_to_teleprompter and retry_scheduled_post.
Has the Daily Studio Teleprompter MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 12, 2026.