Home / MCP registry index / io.usefulapi/depot
Depot MCP by usefulapi
io.usefulapi/depot in the official MCP registry.
Endpoint https://depot.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.
The registry describes it as: Inspect Depot builds, CI runs, job logs and Actions runners; retry or cancel CI runs.
We read its 24 tools on 2026-10-26. 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
depot_list_projects depot_get_project depot_list_builds depot_get_build depot_get_build_steps depot_get_build_step_logs depot_list_registry_images depot_get_usage depot_ci_list_runs depot_ci_get_run_status depot_ci_list_workflows depot_ci_get_job depot_ci_get_job_logs depot_ci_get_failure_diagnosis depot_gha_list_jobs depot_gha_search_logs depot_gha_get_analytics depot_gha_list_recommendations depot_cache_list_entries depot_cache_delete_entries depot_create_project depot_ci_retry_job depot_ci_retry_failed_jobs depot_ci_cancel_run
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-usefulapi-depot)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.