Daily Studio Teleprompter
REMOTE · DAILYSTUDIO.APP · SCANNED OCT 3
Send a shoot's worth of scripts to the Daily Studio teleprompter on iPhone, in one link.
Available components
Recent critical change
Authorization (21 Aug 2026). See the changelog before you install this server.
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (cancel_scheduled_post). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability85
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1639 tokens (~126/item across 13 items; 12 tools + 1 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.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
Capabilities73
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
- Supports UI / widget rendering.Pass
How do I install the Daily Studio Teleprompter MCP server?
Daily Studio Teleprompter is a hosted endpoint at https://dailystudio.app/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 · dailystudio.app
claude mcp add --transport http app-dailystudio-teleprompter 'https://dailystudio.app/mcp'
{
"mcpServers": {
"app-dailystudio-teleprompter": {
"url": "https://dailystudio.app/mcp"
}
}
} {
"servers": {
"app-dailystudio-teleprompter": {
"type": "http",
"url": "https://dailystudio.app/mcp"
}
}
} [mcp_servers.app-dailystudio-teleprompter] url = "https://dailystudio.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"app-dailystudio-teleprompter": {
"type": "remote",
"url": "https://dailystudio.app/mcp",
"enabled": true
}
}
} openclaw mcp add app-dailystudio-teleprompter --url 'https://dailystudio.app/mcp' --transport streamable-http
mcp_servers:
app-dailystudio-teleprompter:
url: "https://dailystudio.app/mcp" {
"McpServers": {
"app-dailystudio-teleprompter": {
"Transport": "http",
"Url": "https://dailystudio.app/mcp"
}
}
} assistant mcp add app-dailystudio-teleprompter -t streamable-http -u 'https://dailystudio.app/mcp'
{
"mcpServers": {
"app-dailystudio-teleprompter": {
"type": "http",
"url": "https://dailystudio.app/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.
- 28 Sept 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
- 25 Sept 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
- 9 Sept 26 0
- Stability: 0.97 → pass security
- 8 Sept 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.
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Aug 26 0
- HTTPS: unverified → pass ▲ security
- 26 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
- 21 Aug 26 0
- Authorization: partial → fail ▼ critical
- New tool “cancel_scheduled_post”, which the server declares destructive security
- Tool “list_planned_scripts” rewrote its description, which is the text the model reads security
- Schema quality: 154 → 126 ▲ functional
- The server now declares the “prompts” capability functional
- Schema quality: good → excellent functional
- New prompt “plan_my_week” functional
- New prompt “whats_coming_up” functional
- New tool “archive_planned_scripts” functional
- New tool “edit_planned_scripts” functional
- New tool “get_planned_scripts” functional
- New tool “list_collections” functional
- New tool “list_scheduled_posts” functional
- New tool “reorder_planned_scripts” functional
- New tool “retry_scheduled_post” functional
- “add_scripts_to_plan” added an optional parameter “collection” cosmetic
- “list_planned_scripts” added an optional parameter “collection” cosmetic
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 3 Oct 2026 · Probed https://dailystudio.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=dailystudio.app | CN=WE1,O=Google Trust Services,C=US | 17 Sept 2026 | 16 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | f8061dcd50bf49d30e224689a0bef992 |
| SANs: dailystudio.app, www.dailystudio.app, *.www.dailystudio.app | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of dailystudio.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| dailystudio.app. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://dailystudio.app/mcp | Verified | 200 | |
| http (plaintext) | http://dailystudio.app/mcp | HTTPS enforced | 301 | https://dailystudio.app/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 →
add_scripts_to_plan Add scripts to the content plan ~244
Put finished 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.
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | – | Optional name for this batch as a group — a topic ('Customer questions'), a series ('Framing, part 1-5'), or what the week is about. The scripts show up grouped under it in the app and on the web, wh… |
| scripts | array | yes | The scripts to add, in the order they should sit in the plan. |
No output schema declared.
No examples provided.
archive_planned_scripts Archive planned scripts ~115
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ids | array | yes | The scripts to archive (or restore). Ids come from list_planned_scripts. |
| restore | boolean | – | true brings archived scripts back into the plan instead. Default false. |
No output schema declared.
No examples provided.
cancel_scheduled_post Cancel a scheduled post ~77
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The post's id, from list_scheduled_posts. |
No output schema declared.
No examples provided.
edit_planned_scripts Edit planned scripts ~134
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.
| Name | Type | Req | Description |
|---|---|---|---|
| edits | array | yes | The changes, one entry per script. Only the fields you send change; everything else stays. Get ids from list_planned_scripts. |
No output schema declared.
No examples provided.
get_planned_scripts Read scripts in full ~94
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ids | array | yes | The scripts to read in full, at most 20 per call. Ids come from list_planned_scripts. |
No output schema declared.
No examples provided.
list_collections List the plan's collections ~46
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_connected_accounts List connected social accounts ~73
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_planned_scripts Read the content plan ~178
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.
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | – | Only scripts in this collection. Omit to read the whole plan. |
| from | string | – | Only scripts dated on or after this day. |
| includeUndated | boolean | – | Include scripts with no date at all (the backlog). Default true. |
| to | string | – | Only scripts dated on or before this day. |
No output schema declared.
No examples provided.
list_scheduled_posts Read the publishing queue ~105
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.
| Name | Type | Req | Description |
|---|---|---|---|
| state | string | – | Only posts in this state. Omit for the whole queue, newest first. |
No output schema declared.
No examples provided.
reorder_planned_scripts Set the shoot order ~99
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ids | array | yes | Script ids in the order they should be recorded, first first. Scripts you leave out keep their current order, after the ones you name. |
No output schema declared.
No examples provided.
retry_scheduled_post Retry a failed post ~75
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The post's id, from list_scheduled_posts. |
No output schema declared.
No examples provided.
send_script_to_teleprompter Send script to teleprompter ~368
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.
| Name | Type | Req | Description |
|---|---|---|---|
| platform | string | – | Where the video will be published. Selects that platform's safe-zone overlay so on-screen UI never covers the creator. Omit to leave the user's choice alone. With `scripts`, applies to items that don… |
| scripts | array | – | A batch of scripts (in recording order) delivered as a single link — up to 100 of them, 400000 characters of script in total. The app queues them; after each recording it offers the next. Provide eit… |
| text | string | – | A single finished teleprompter script, plain UTF-8. Newlines allowed. Provide either this or `scripts`, not both. |
| title | string | – | Optional short label for `text`, e.g. 'Cold plunge hook'. |
| wpm | integer | – | Optional scroll speed in words per minute. Sets the app's teleprompter speed. Omit to leave the user's setting alone. With `scripts`, applies to items that don't set their own. |
No output schema declared.
No examples provided.
What is the Daily Studio Teleprompter MCP server?
Daily Studio Teleprompter is an MCP server listed in the public MCP registry as app.dailystudio/teleprompter. Send a shoot's worth of scripts to the Daily Studio teleprompter on iPhone, in one link. This page covers its hosted endpoint (https://dailystudio.app/mcp).
Is the Daily Studio Teleprompter MCP server safe to use?
Daily Studio Teleprompter scores 79 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 Daily Studio Teleprompter MCP server expose?
Daily Studio Teleprompter exposes 12 tools: send_script_to_teleprompter, list_connected_accounts, add_scripts_to_plan, list_planned_scripts, edit_planned_scripts, and 7 more. Their descriptions and schemas cost roughly 1,608 tokens of context every time the server is loaded.
Does the Daily Studio Teleprompter MCP server require authentication?
No. We connected to Daily Studio Teleprompter without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Daily Studio Teleprompter MCP server still maintained?
Daily Studio Teleprompter is still listed as active in the MCP registry. We last reached this channel on 3 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.