Skip to content

api.video MCP by usefulapi

io.usefulapi/apivideousefulapi.iostreamable-httpv1.40.4Scanned

Manage videos and live streams, inspect captions, players and webhooks, and read play analytics.

15 tools: 4 can delete or cancel things and 11 only read.

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

The remote endpoint did not answer the last look. Remote posture

Anlyon alternative

4 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the api.video MCP by usefulapi can do

The api.video MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 15 tools. It can delete or cancel things (4 tools: apivideo_create_video, apivideo_update_video, apivideo_delete_video and apivideo_create_live_stream). 11 tools only read.

3 tools bring in text other people can write (apivideo_get_video, apivideo_get_live_stream and apivideo_list_captions).

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

Last scanned Oct 25, 2026, version 1.40.4.

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.

15 tools

Deletes or cancels 4Claude Code: deny
  • apivideo_create_live_streamWRITE.No findings

    Why it is in this group

    • The name "apivideo_create_live_stream" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    WRITE. Create a new live stream, returning a stream key and RTMP ingest URL to broadcast to. POST /live-streams.

    Annotations the server declares

    • title: Create live stream (write)
    • destructiveHint: true
  • apivideo_create_videoWRITE.No findings

    Why it is in this group

    • The name "apivideo_create_video" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    WRITE. Create a new video object. If `source` (a public video URL) is provided, api.video ingests the video from that URL — recommended for hosted use, since raw file bytes cannot stream through MCP. POST /videos.

    Annotations the server declares

    • title: Create video (write)
    • destructiveHint: true
  • apivideo_delete_videoWRITE.No findings

    Why it is in this group

    • The name "apivideo_delete_video" says "delete": a word for removing or ending something.
    • The description says "Permanently DELETE".
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    WRITE. Permanently DELETE a video and all its assets. This cannot be undone. DELETE /videos/{videoId}.

    Annotations the server declares

    • title: Delete video (write)
    • destructiveHint: true
  • apivideo_update_videoWRITE.No findings

    Why it is in this group

    • The name "apivideo_update_video" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    WRITE. Update fields on an existing video. Only the provided fields are changed. PATCH /videos/{videoId}.

    Annotations the server declares

    • title: Update video (write)
    • destructiveHint: true
Only reads 11Show 11 read-only tools
  • apivideo_get_live_streamGet a single live stream object by id (stream key, RTMP ingest, player URL).Reads text others writeNo findings

    Why it is in this group

    • The name "apivideo_get_live_stream" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "get" and "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Get a single live stream object by id (stream key, RTMP ingest, player URL). Read-only. GET /live-streams/{liveStreamId}.

    Annotations the server declares

    • title: Get live stream
    • readOnlyHint: true
  • apivideo_get_live_stream_analyticsAggregated play analytics for live streams over a date range, grouped by a dimension.No findings

    Why it is in this group

    • The name "apivideo_get_live_stream_analytics" says "get": a word for reading.
    Description, as the server wrote it
    Aggregated play analytics for live streams over a date range, grouped by a dimension. Read-only. GET /analytics/live-streams/plays.

    Annotations the server declares

    • title: Live stream analytics (plays)
    • readOnlyHint: true
  • apivideo_get_videoGet a single video object by id (title, assets, player URL, status flags).Reads text others writeNo findings

    Why it is in this group

    • The name "apivideo_get_video" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "get" and "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Get a single video object by id (title, assets, player URL, status flags). Read-only. GET /videos/{videoId}.

    Annotations the server declares

    • title: Get video
    • readOnlyHint: true
  • apivideo_get_video_analyticsAggregated play analytics for videos over a date range, grouped by a dimension.No findings

    Why it is in this group

    • The name "apivideo_get_video_analytics" says "get": a word for reading.
    Description, as the server wrote it
    Aggregated play analytics for videos over a date range, grouped by a dimension. Read-only. GET /analytics/videos/plays.

    Annotations the server declares

    • title: Video analytics (plays)
    • readOnlyHint: true
  • apivideo_get_video_statusGet encoding and ingest status for a video (upload progress, encoding qualities, playability).No findings

    Why it is in this group

    • The name "apivideo_get_video_status" says "get": a word for reading.
    Description, as the server wrote it
    Get encoding and ingest status for a video (upload progress, encoding qualities, playability). Read-only. GET /videos/{videoId}/status.

    Annotations the server declares

    • title: Get video status
    • readOnlyHint: true
  • apivideo_list_captionsList caption tracks for a video (language, source URL, default flag).Reads text others writeNo findings

    Why it is in this group

    • The name "apivideo_list_captions" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "list" and "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    List caption tracks for a video (language, source URL, default flag). Read-only. GET /videos/{videoId}/captions.

    Annotations the server declares

    • title: List captions
    • readOnlyHint: true
  • apivideo_list_chaptersList chapter tracks for a video.No findings

    Why it is in this group

    • The name "apivideo_list_chapters" says "list": a word for reading.
    Description, as the server wrote it
    List chapter tracks for a video. Read-only. GET /videos/{videoId}/chapters.

    Annotations the server declares

    • title: List chapters
    • readOnlyHint: true
  • apivideo_list_live_streamsList live streams in the account, with optional filters (streamKey, name) and sorting.No findings

    Why it is in this group

    • The name "apivideo_list_live_streams" says "list": a word for reading.
    Description, as the server wrote it
    List live streams in the account, with optional filters (streamKey, name) and sorting. Read-only. GET /live-streams.

    Annotations the server declares

    • title: List live streams
    • readOnlyHint: true
  • apivideo_list_playersList customized player themes in the account.No findings

    Why it is in this group

    • The name "apivideo_list_players" says "list": a word for reading.
    Description, as the server wrote it
    List customized player themes in the account. Read-only. GET /players.

    Annotations the server declares

    • title: List players
    • readOnlyHint: true
  • apivideo_list_videosList videos in the account, with optional filters (title, tags, metadata, description, liveStreamId) and sorting.No findings

    Why it is in this group

    • The name "apivideo_list_videos" says "list": a word for reading.
    Description, as the server wrote it
    List videos in the account, with optional filters (title, tags, metadata, description, liveStreamId) and sorting. Read-only. GET /videos.

    Annotations the server declares

    • title: List videos
    • readOnlyHint: true
  • apivideo_list_webhooksList webhooks configured in the account, optionally filtered by event name.No findings

    Why it is in this group

    • The name "apivideo_list_webhooks" says "list": a word for reading.
    Description, as the server wrote it
    List webhooks configured in the account, optionally filtered by event name. Read-only. GET /webhooks.

    Annotations the server declares

    • title: List webhooks
    • readOnlyHint: true

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

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

The remote endpoint did not answer the last look

Looked at Nov 20, 2026, 19:32 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
no
HTTP status of an anonymous initialize
not observed
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
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

The probe stopped: The server redirected a POST to a different request.

Posture changes

  1. Oct 29, 2026
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 4 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://apivideo.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://apivideo.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no 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. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 4 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://apivideo.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://apivideo.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Install

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

claude mcp add --transport http apivideo https://apivideo.usefulapi.io/mcp
claude mcp add --transport http apivideo https://apivideo.usefulapi.io/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": [
      "mcp__apivideo__apivideo_list_videos",
      "mcp__apivideo__apivideo_get_video",
      "mcp__apivideo__apivideo_get_video_status",
      "mcp__apivideo__apivideo_list_live_streams",
      "mcp__apivideo__apivideo_get_live_stream",
      "mcp__apivideo__apivideo_list_captions",
      "mcp__apivideo__apivideo_list_chapters",
      "mcp__apivideo__apivideo_list_players",
      "mcp__apivideo__apivideo_list_webhooks",
      "mcp__apivideo__apivideo_get_video_analytics",
      "mcp__apivideo__apivideo_get_live_stream_analytics"
    ],
    "ask": [],
    "deny": [
      "mcp__apivideo__apivideo_create_video",
      "mcp__apivideo__apivideo_update_video",
      "mcp__apivideo__apivideo_delete_video",
      "mcp__apivideo__apivideo_create_live_stream"
    ]
  }
}

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

Capability tags behind 3 rules
  • mcp__apivideo__apivideo_get_video untrusted-input
  • mcp__apivideo__apivideo_get_live_stream untrusted-input
  • mcp__apivideo__apivideo_list_captions untrusted-input

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/io.usefulapi/apivideo/verify?hash=fd3bf9b170486281a724960cadce47e92f8fdd74a88fe2ba791cf0f5fe574df8" | jq -e '.changed == false'

Pinned hash fd3bf9b17048, from Oct 25, 2026, 23:18 UTC.

Watch

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

https://radar.anlyon.com/servers/io.usefulapi/apivideo/changes.xml

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

Badge

Anlyon Radar badge for io.usefulapi/apivideo
[![Anlyon Radar](https://radar.anlyon.com/badge/io.usefulapi/apivideo.svg)](https://radar.anlyon.com/servers/io.usefulapi/apivideo)

Source: MCP Registry · repository. Synced Nov 18, 2026, 11:18 UTC.

api.video MCP by usefulapi: questions and answers

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

Is the api.video MCP by usefulapi safe?

No scan can promise that. What its definitions show: 15 tools, 4 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 api.video MCP by usefulapi delete data?

Yes. 4 tools can delete, cancel or revoke something: apivideo_create_video, apivideo_update_video, apivideo_delete_video and apivideo_create_live_stream.

Can the api.video MCP by usefulapi 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 api.video MCP by usefulapi have?

15 tools: 4 destructive, 11 read. apivideo_create_video, apivideo_update_video, apivideo_delete_video, apivideo_create_live_stream, apivideo_list_videos, apivideo_get_video, apivideo_get_video_status, apivideo_list_live_streams and 7 more.

Does the api.video MCP by usefulapi need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the api.video MCP by usefulapi send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the api.video MCP by usefulapi changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.