# app.dailystudio/teleprompter

Send a shoot's worth of scripts to the Daily Studio teleprompter on iPhone, in one link.

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the content rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 1.0.0
- **Author:** app.dailystudio
- **License:** Unknown
- **Endpoints:** streamable-http https://dailystudio.app/mcp
- **Source:** https://dailystudio.app
- **Endpoint health:** reachable (last checked 2026-09-18T16:43:54.224Z, 4 samples) — uptime is not a security property and is not part of the trust score
- **Compatible clients:** claude-code, cursor, copilot, chatgpt, gemini (basis: transport)

## Trust

60/100 (B), scored on the content rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: clean
- Obfuscation scan: clean
- Evidence age: 1 day

## Security scan

- **Status:** clean
- **Scanned:** 2026-09-18T16:43:54.224Z
- **Version scanned:** live
- **CVEs:** no coverage — this entry has no package coordinates to query OSV against, so "no known CVEs" is NOT asserted for it.

## Tools

12 declared. Observed from a live `tools/list` probe.
- `send_script_to_teleprompter` — 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 th
- `list_connected_accounts` — 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
- `add_scripts_to_plan` — 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
- `list_planned_scripts` — 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 f
- `edit_planned_scripts` — 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
- `get_planned_scripts` — 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,
- `archive_planned_scripts` — 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 reco
- `reorder_planned_scripts` — 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 
- `list_collections` — 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
- `list_scheduled_posts` — 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
- `cancel_scheduled_post` — 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. Confi
- `retry_scheduled_post` — 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 ac

## Install

**Verdict: review** — Installable, but 2 things to check first: No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it.
**Cautions** (coverage gaps and advisories — never blocking)
- No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it.
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"teleprompter\": {\n      \"type\": \"http\",\n      \"url\": \"https://dailystudio.app/mcp\"\n    }\n  }\n}"
```

## Blast radius

Moderate to extensive — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: mutates data; runs on someone else's infrastructure.
- Floor 26, ceiling 50 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/app.dailystudio%2Fteleprompter
- Install plan: https://forgeregistry.com/api/v1/packages/app.dailystudio%2Fteleprompter/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/app.dailystudio%2Fteleprompter
- HTML page: https://forgeregistry.com/registry/app.dailystudio%2Fteleprompter
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.