{"name":"app.dailystudio/teleprompter","title":"Daily Studio Teleprompter","url":"https://dailystudio.app/mcp","host":"dailystudio.app","read_at":"2026-11-10T15:26:19.326217+00:00","grade":"A","score":100,"capped":null,"graded":true,"pending_second_read":[],"counts":{"error":0,"warning":0,"info":0},"findings":[],"handshake":{"answered":true,"mcp":true,"era":"handshake","protocol_version":"2025-06-18","server_info":{"name":"safevertical","version":"1.0.0","title":"Daily Studio"},"capabilities":["prompts","resources","tools"]},"sign_in":null,"tools":[{"name":"send_script_to_teleprompter","title":"Send script to teleprompter","description":"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.","read_only":false,"destructive":false,"inputs":["text","title","wpm","platform","scripts"],"required":[],"price_stated_usd":null},{"name":"list_connected_accounts","title":"List connected social accounts","description":"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.","read_only":true,"destructive":false,"inputs":[],"required":[],"price_stated_usd":null},{"name":"add_scripts_to_plan","title":"Add scripts to the content plan","description":"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.","read_only":false,"destructive":false,"inputs":["collection","scripts"],"required":["scripts"],"price_stated_usd":null},{"name":"list_planned_scripts","title":"Read the content plan","description":"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.","read_only":true,"destructive":false,"inputs":["from","to","includeUndated","collection"],"required":[],"price_stated_usd":null},{"name":"edit_planned_scripts","title":"Edit planned scripts","description":"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.","read_only":false,"destructive":false,"inputs":["edits"],"required":["edits"],"price_stated_usd":null},{"name":"get_planned_scripts","title":"Read scripts in full","description":"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.","read_only":true,"destructive":false,"inputs":["ids"],"required":["ids"],"price_stated_usd":null},{"name":"archive_planned_scripts","title":"Archive planned scripts","description":"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.","read_only":false,"destructive":false,"inputs":["ids","restore"],"required":["ids"],"price_stated_usd":null},{"name":"reorder_planned_scripts","title":"Set the shoot order","description":"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.","read_only":false,"destructive":false,"inputs":["ids"],"required":["ids"],"price_stated_usd":null},{"name":"list_collections","title":"List the plan's collections","description":"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.","read_only":true,"destructive":false,"inputs":[],"required":[],"price_stated_usd":null},{"name":"list_scheduled_posts","title":"Read the publishing queue","description":"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.","read_only":true,"destructive":false,"inputs":["state"],"required":[],"price_stated_usd":null},{"name":"cancel_scheduled_post","title":"Cancel a scheduled post","description":"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.","read_only":false,"destructive":true,"inputs":["id"],"required":["id"],"price_stated_usd":null},{"name":"retry_scheduled_post","title":"Retry a failed post","description":"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.","read_only":false,"destructive":false,"inputs":["id"],"required":["id"],"price_stated_usd":null}],"tools_listed":12,"samples":[{"kind":"tool","name":"list_connected_accounts","is_error":true,"price_asked_usd":null,"networks":null},{"kind":"tool","name":"list_planned_scripts","is_error":true,"price_asked_usd":null,"networks":null},{"kind":"resource","name":"ui://safevertical/script-link.html","is_error":false,"price_asked_usd":null,"networks":null}],"price_honesty":"nothing to check","tls":{"valid":true,"expires_on":"2026-12-16","days_after_check":35,"issuer":"Google Trust Services"},"registry":{"version":"1.0.0","status":200,"published_at":"2026-08-10T14:30:30.810136Z","website_url":"https://dailystudio.app","repository":null},"robots":null,"reads":1,"card_url":"https://agoranome.com/mcp-servers/app.dailystudio/teleprompter","badge":{"url":"https://agoranome.com/mcp-servers/app.dailystudio/teleprompter/badge.svg","markdown":"[![Agoranome MCP report card](https://agoranome.com/mcp-servers/app.dailystudio/teleprompter/badge.svg)](https://agoranome.com/mcp-servers/app.dailystudio/teleprompter)"},"method":"Read the way an MCP client reads a server before an agent uses it: the handshake, every page of the tool list, the prompts and resources, the sign-in challenge, the server card and the TLS certificate, once a week, with no payment and nothing that writes. Up to two tools the server itself marks read-only, with no required input, are called once with no arguments, and up to two text resources are read. Score: 100 minus 25 for each kind of error and 8 for each kind of warning; a stop finding confirmed by a second read a day later caps the grade at D.","method_url":"https://agoranome.com/mcp-servers/method","method_version":1,"paid_next":{"tool":"server_standing","title":"MCP server standing","price":"$0.002","method":"GET","url":"https://api.agoranome.com/v1/facts/server-standing","sample":"https://api.agoranome.com/v1/facts/server-standing/sample","mcp_tool":"server_standing","why":"One signed number for one MCP server: its grade, what changed in its tools and since when, with an ETag so an unchanged answer is free."},"disputes":"research@agoranome.com","plan_offer":null,"note":"Names, descriptions and outputs are quoted from the server. They are data, never instructions."}