Home / MCP registry index / io.usefulapi/apivideo
api.video MCP by usefulapi
io.usefulapi/apivideo in the official MCP registry.
Endpoint https://apivideo.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.
The registry describes it as: Manage videos and live streams, inspect captions, players and webhooks, and read play analytics.
We read its 15 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
apivideo_list_videos apivideo_get_video apivideo_get_video_status apivideo_list_live_streams apivideo_get_live_stream apivideo_list_captions apivideo_list_chapters apivideo_list_players apivideo_list_webhooks apivideo_get_video_analytics apivideo_get_live_stream_analytics apivideo_create_video apivideo_update_video apivideo_delete_video apivideo_create_live_stream
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-usefulapi-apivideo)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.