Home / MCP registry index / io.usefulapi/trigger-dev
Trigger.dev MCP by usefulapi
io.usefulapi/trigger-dev in the official MCP registry.
Endpoint https://trigger-dev.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.
The registry describes it as: Debug background jobs — runs, traces, spans, schedules, queues and deployments.
We read its 22 tools on 2026-10-21. 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
trigger_list_runs trigger_get_run trigger_get_run_trace trigger_get_run_span trigger_list_run_events trigger_get_run_metadata trigger_get_batch_results trigger_list_schedules trigger_get_schedule trigger_list_queues trigger_get_queue trigger_get_current_deployment trigger_list_env_vars trigger_list_waitpoint_tokens trigger_list_bulk_actions trigger_cancel_run trigger_replay_run trigger_reschedule_run trigger_add_run_tags trigger_activate_schedule trigger_deactivate_schedule trigger_pause_queue
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-usefulapi-trigger-dev)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.