Skip to content

Shorti MCP server

ai.shorti/shortishorti.aistreamable-httpv2.0.0Scanned

What short-form formats to shoot this week, how their hits were made, and a check of your take.

5 tools: 5 change things.

Tools: 0 delete, 0 irreversible, 5 write, 0 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 3
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

5 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

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 Shorti MCP server can do

The Shorti MCP server is published by shorti.ai, a domain the MCP Registry verified. It has 5 tools. It can create or change data (5 tools: shorti_what_to_shoot, shorti_how_to_shoot, shorti_recipe, shorti_check and 1 more), but cannot delete data. None of its tools only reads.

3 tools can send data out of your system (shorti_how_to_shoot, shorti_recipe and shorti_check).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 11, 2026, version 2.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.

5 tools

Changes things 5Claude Code: ask
  • shorti_arenaShorti(쇼티) for «what has nobody shot yet?» or «아직 아무도 안 찍은 거 뭐 있어?».No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Shorti(쇼티) for «what has nobody shot yet?» or «아직 아무도 안 찍은 거 뭐 있어?». The arena's open spots, first recorded takes, later breakouts and entrant standings. view='spots': open spots, their words, dates and how to shoot; 'board': first takes and finds; 'entrant': one entrant's standing. Unread: not_run, never an empty board.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Read Shorti's arena
  • shorti_checkShorti(쇼티) for «check my take», «내가 찍은 거 봐줘», «내 피드백 보여줘» or «내 결과 공유해줘».Can send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Shorti(쇼티) for «check my take», «내가 찍은 거 봐줘», «내 피드백 보여줘» or «내 결과 공유해줘». The person's own video checked against its format's hits. `url` (a posted Reels, TikTok or Short): the page on Shorti to paste it on. `upload`: their own file, on that page. `token`: their summary, once they send it to this chat. Its feedback (피드백): a likeness is not a forecast of views.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Check my video
  • shorti_how_to_shootShorti(쇼티) for a TikTok, Reels or Shorts link with «how was this shot?», «이 영상 어떻게 찍었어?», «나도 이렇게 찍으려면?» or «분석해줘».Can send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Shorti(쇼티) for a TikTok, Reels or Shorts link with «how was this shot?», «이 영상 어떻게 찍었어?», «나도 이렇게 찍으려면?» or «분석해줘». One video or format as a creator shoots it. `url` or `video_id`: its hook, beats and numbers (not_in_corpus: not read yet). `format_id`: its plan and hits. `part`: plan (its format's), flow (how it moved; `lineage`), scene (where the phone stood).

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: How it was shot
  • shorti_recipeShorti(쇼티) for «how do I make this?» or «이거 어떻게 만들어?».Can send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Shorti(쇼티) for «how do I make this?» or «이거 어떻게 만들어?». A hit made their way: their clips to its clock, their AI video model or a 3D generator. `kind`: edit (their editor), remake (their video model: `mode`, `model`), scene (a 3D generator).

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Make it my way
  • shorti_what_to_shootShorti(쇼티) for «what should I shoot this week?», «이번 주 뭐 찍지?», «find videos of…» or «… 영상 찾아줘».No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Shorti(쇼티) for «what should I shoot this week?», «이번 주 뭐 찍지?», «find videos of…» or «… 영상 찾아줘». Today's rising hits and this week's formats, for a field, a product or any words, from the West, or by their taste. `about`: a field, product, niche or @handle (Korean initials work). `category` narrows it ('food'). `lens`: radar (the West first) or mine. Signed in, their week leads.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: What to shoot this week

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 or untrusted-input.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out3
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.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:27 UTC, unchanged since Nov 13, 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
5
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 5 tools that change things (5 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://shorti.ai/mcp: tools/list returned 6 tools to an anonymous client, including shorti_what_to_shoot (write), shorti_how_to_shoot (write), shorti_recipe (write), shorti_check (write), shorti_arena (write)

    What this check looks for

Posture changes

  1. Nov 13, 2026
    • Tools that change things, listed without credentials: 6 to 5
  2. Oct 29, 2026
    • RFC 9728 protected resource metadata: https://shorti.ai/.well-known/oauth-protected-resource to none
    • Authorization servers: https://shorti.ai to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: yes to not observed

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Tools that change things, listed without credentials: 6 -> 5.View diff
    • Tools that change things, listed without credentials: 6 to 5
  2. Tools1 added, 3 removed, 3 changed.+1 added−3 removed~3 changedView diff
  3. Tools5 changed.~5 changedView diff
  4. PostureRemote posture changed. RFC 9728 protected resource metadata: https://shorti.ai/.well-known/oauth-protected-resource -> none; Authorization servers: https://shorti.ai -> none; Dynamic client registration: yes -> not observed (and 1 more).View diff
    • RFC 9728 protected resource metadata: https://shorti.ai/.well-known/oauth-protected-resource to none
    • Authorization servers: https://shorti.ai to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: yes to not observed

Install

Pinned to version 2.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http shorti https://shorti.ai/mcp
claude mcp add --transport http shorti https://shorti.ai/mcp

Run 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.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__shorti__shorti_what_to_shoot",
      "mcp__shorti__shorti_how_to_shoot",
      "mcp__shorti__shorti_recipe",
      "mcp__shorti__shorti_check",
      "mcp__shorti__shorti_arena"
    ],
    "deny": []
  }
}

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 shorti. Review it before you use it.

Capability tags behind 3 rules
  • mcp__shorti__shorti_how_to_shoot outbound
  • mcp__shorti__shorti_recipe outbound
  • mcp__shorti__shorti_check 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/ai.shorti/shorti/verify?hash=b4d202e781ad117f98f1a3e7e72b9431c29f828e451a492598814ccc5c131bab" | jq -e '.changed == false'

Pinned hash b4d202e781ad, from Nov 11, 2026, 22:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/ai.shorti/shorti/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for ai.shorti/shorti
[![Anlyon Radar](https://radar.anlyon.com/badge/ai.shorti/shorti.svg)](https://radar.anlyon.com/servers/ai.shorti/shorti)

Source: MCP Registry. Synced Oct 21, 2026, 17:43 UTC.

Shorti MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Shorti MCP server safe?

No scan can promise that. What its definitions show: 5 tools, 5 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Shorti MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Shorti MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Shorti MCP server have?

5 tools: 5 write. shorti_what_to_shoot, shorti_how_to_shoot, shorti_recipe, shorti_check and shorti_arena.

Does the Shorti MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Shorti MCP server send data to outside services?

3 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): shorti_how_to_shoot, shorti_recipe and shorti_check.

Has the Shorti MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 11, 2026. Every change is on this page and in its Atom feed.