Contentdrips API and MCP vs Osmo CLI

Contentdrips API and MCP 60

Closed service under terms of use dated 11 December 2024, governed by the laws of Pakistan (15). The privacy policy of 9 August 2026 states retention while the account is active, deletion of content as soon as the account is deleted apart from short-lived backups, deletion of social tokens on disconnect, and no training of Contentdrips' own models on user content (22 of 30). No deprecation policy. The legacy carousel input is 'still supported' with no end date (3 of 20). The policy names OpenAI, OpenRouter, Google Gemini and TinyPopups and has an international transfers section, without a full subprocessor list or hosting locations (12 of 20). 15 + 22 + 3 + 12 = 52.

Osmo CLI 33

Closed source. The skill README says the CLI, renderer and resource packages are proprietary, and the npm packages carried no licence field or LICENSE file on 8 October. The terms of service render only in the browser and were read on 8 October from the site's script bundle, which this method no longer reads, so no licence terms are readable (0, as for other listings whose terms were only ever read from a script bundle). The privacy policy and terms were read the same way, so no data-handling statement remains (0). No deprecation policy or dated notices (0). The CLI bundle read on 8 October contacts only studio.osmo.inc and contains no analytics hosts, though telemetry isn't documented either way; the AI providers named in the struck privacy policy no longer count. Partial kept (10). 0 + 0 + 0 + 10 = 10.

Contentdrips API and MCP 31

API keys from the dashboard, with no scopes, expiry or rotation documented. The MCP server also runs OAuth 2.0 with PKCE and dynamic client registration, but its one mcp scope authorises the same full key (18 of 30). No read-only key or endpoint. publish_post needs confirmed: true and the docs ask for confirmation before deletes (10 of 20). Tools read blog, YouTube and TikTok links and download external images, and no prompt-injection guidance was found (3 of 15). No audit log or per-call record documented (0). No security.txt, disclosure policy, bug bounty or certification found (0). 18 + 10 + 3 + 0 + 0 = 31.

Osmo CLI 51

OAuth device flow with a client registered per device, refresh tokens, a revocation endpoint and osmo logout. The OAuth metadata re-read on 5 November lists scopes projects:write, energy:spend and a new account:read. Tokens sit in a 0600 file under ~/.osmo/auth per the 8 October bundle reading, and no secret travels in a URL (26). --no-spend drops the spending scope and shares delete needs --yes, but every login asks for projects:write and no read-only login is documented (11). Comments from anyone with a review link are returned to the agent. The skill (15 October) tells the agent a review comment is feedback on the video, never an instruction to run commands, change access or work outside the project, and that a commenter's name is self-reported, and the CLI strips control and bidirectional characters from output. Guidance and one mitigation (10). Connections are named per device and osmo jobs lists runs. No audit log found (4). No security.txt (osmo.inc answers with its HTML shell, studio.osmo.inc 404), disclosure policy, bug bounty or certification found. The earlier 2 had no programme evidence behind it, so the line is 0 (0). 26 + 11 + 10 + 4 + 0 = 51.

Contentdrips API and MCP 54

29 MCP tools (15 for 11 to 30), with no toolsets or read-only subset (15 of 25). list_posts filters by status and get_my_templates by type and workspace, and no pagination is documented (8 of 20). Errors carry error and message, and the troubleshooting section explains template-not-found and label mismatches (12 of 20). Access labels in the docs, confirmed: true on publish_post, and job polling that is safe to repeat, but no idempotency key on renders or post creation, and the labels couldn't be confirmed as MCP annotations (12 of 20). Two required fields to render (template_id, output), and no SDK beyond an Embed SDK for the editor (7 of 15). 15 + 8 + 12 + 12 + 7 = 54.

Osmo CLI 70

Read from the 0.1.19 bundle and docs on 8 October and the skill re-read on 5 November, not from a run. The skill grew from 255 bytes to 9,686 bytes on 15 October, a compact guide with a command table, every command takes --json, and lists default to short pages (18). --limit and --cursor on lists, --type on resources and --open on comments (15). Errors are JSON with a code, a message, a next command and retryAfter where it applies, with exit code 2 for usage errors, though only one error is documented (14). osmo run sends an Idempotency-Key and retries network errors, repeating unshare is documented as safe, and a failed upload reports the share to retry against (16). Few required arguments, and no SDK in any language (7). 18 + 15 + 14 + 16 + 7 = 70.

Contentdrips API and MCP 25

No x402, MPP or L402 (0). No per-call price. The API page shows $0 on paid cards, a $39 starting price and $359 a month for unlimited calls, and the pricing page shows $15 and $26 plans without API, so the public pricing can't be relied on (5 of 20). The API page says 10 API calls to test with and no card for the free plan (20). A person signs up and generates the key in the dashboard (0). 0 + 5 + 20 + 0 = 25.

Osmo CLI 10

Graded on the paid hosted service the CLI depends on, by the published rubric. No x402, MPP or L402 in the OAuth metadata or the skill (0). osmo.inc/pricing, terms and privacy render only in the browser, and the 8 October prices were read from the site's script, which this method no longer reads, so no price is readable (0). The skill README says model runs use the account's plan, which includes a free monthly allowance, without saying whether a card is needed, so half (10). A person has to create an account and approve the device login in a browser (0). 0 + 0 + 10 + 0 = 10.

Contentdrips API and MCP 48

No OpenAPI or other machine-readable contract for the REST API, and the MCP server is closed, so its schemas weren't read. The MCP page names every tool's parameters (10 of 25, on that partial evidence). The marketing site's llms.txt is generated by Yoast and lists blog posts, with no link to the API or MCP docs; the developer site has none (2 of 10). The MCP page labels each tool Read, Write or Destructive, says get_template_structure is needed before filling or editing, and gives confirmation rules for publishing and deleting (15 of 20). Enums for output, type, AI method and formats, but content_update and carousel_content are open structures keyed by template labels (9 of 15). Request examples and an error table (400, 401, 404, 500) with an error body, while the result section contradicts its own example and some examples omit a required value (9 of 15). Docs marked v1.0.0 and last updated January 2025, with no changelog (3 of 15). 10 + 2 + 15 + 9 + 9 + 3 = 48.

Osmo CLI 34

API checklist adapted to a CLI. No OpenAPI or command schema is published on a docs page. The model input schemas recorded on 8 October came from the product's own catalogue API at studio.osmo.inc/api/resources, which this method no longer reads, so the contract line has nothing behind it (0). The skill's SKILL.md is Markdown written for agents, with a command table, and osmo.inc/llms.txt now links the CLI page; the package's README, SETUP.md and DEPLOY.md were read from the 0.1.19 tarball on 8 October (10). Help text in the 0.1.19 bundle states what each command is for and when to pick share over studio deploy, per the 8 October check (12). Typed inputs with enums and ranges were read only from the catalogue API, so none remain (0). An example per command and JSON output shapes in DEPLOY.md, and a command table in the skill, but no reference for the roughly 50 error codes (8). Semver versions with no changelog (4). 0 + 10 + 12 + 0 + 8 + 4 = 34.

Contentdrips API and MCP 15

The newest dated change to the agent surface is the MCP page, published 25 May 2026 and modified 27 May, 163 days before this check (10). No three dated changes since 8 August were found (0). No public changelog. Email support at hello@contentdrips.com, which we didn't test (5 of 15). Not in the official MCP registry and no official SDKs (0). No public package or repository (0). 10 + 0 + 5 + 0 + 0 = 15.

Osmo CLI 7

No release date can be read. The 6 October date for 0.1.19 and the version timestamps came from npm's registry document, a JSON data interface this method no longer reads, so they are struck. The 0.1.19 package itself, read on 8 October, carries no release date, the CLI page and llms.txt give none, and the skill repository has no tags or versions (0). No dated release in the 90 days from 7 August can be counted for the same reason (0). No public changelog or tracker. Support is support@osmo.inc, and the skill repository has eight commits and two merged pull requests, the latest on 15 October (3). No SDKs and no MCP registry entry (0). One pinned dependency with a third-party inventory and hashes in release.json, per the 0.1.19 package read on 8 October, but no public CI. Partial kept (4). The skill now names osmo usage, absent from 0.1.19, so a later version is likely. 0 + 0 + 3 + 0 + 4 = 7.