Trigger.dev MCP by usefulapi
io.usefulapi/trigger-devusefulapi.iostreamable-httpv1.40.4Scanned
Debug background jobs — runs, traces, spans, schedules, queues and deployments.
22 tools: 7 can delete or cancel things, 1 do something that can't be undone and 14 change things.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 1
- 15 findings
The remote endpoint did not answer the last look. Remote posture
Anlyon alternative
22 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 Trigger.dev MCP by usefulapi can do
The Trigger.dev MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 22 tools. It can delete or cancel things (7 tools: trigger_cancel_run, trigger_replay_run, trigger_reschedule_run, trigger_add_run_tags and 3 more), do things that cannot be undone, such as sending, paying or publishing (trigger_list_runs) and create or change data (14 tools: trigger_get_run, trigger_get_run_trace, trigger_get_run_span, trigger_list_run_events and 10 more). None of its tools only reads.
1 tool can send data out of your system (trigger_list_runs).
The fixed checks matched 15 findings (annotation-conflict). Each one comes with the text it matched.
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.
22 tools
Deletes or cancels 7Claude Code: deny
trigger_activate_scheduleResume a paused schedule so it fires again.No findings
Why it is in this group
- The name "trigger_activate_schedule" says "trigger": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Resume a paused schedule so it fires again. Trigger.dev: POST /api/v1/schedules/{scheduleId}/activate.
Annotations the server declares
- title: Activate a schedule
- destructiveHint: true
trigger_add_run_tagsAttach tags to a run so you can filter for it later.No findings
Why it is in this group
- The name "trigger_add_run_tags" says "trigger": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Attach tags to a run so you can filter for it later. Additive and safe. Trigger.dev: POST /api/v1/runs/{runId}/tags.
Annotations the server declares
- title: Add tags to a run
- destructiveHint: true
trigger_cancel_runCancel an in-flight run.No findings
Why it is in this group
- The name "trigger_cancel_run" says "trigger": a word for a change.
- The description's first verb is "cancel": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Cancel an in-flight run. Note this is the one endpoint on API v2, not v1. Trigger.dev: POST /api/v2/runs/{runId}/cancel.
Annotations the server declares
- title: Cancel a run
- destructiveHint: true
trigger_deactivate_schedulePause a schedule so it stops firing.No findings
Why it is in this group
- The name "trigger_deactivate_schedule" says "trigger": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Pause a schedule so it stops firing. The usual first move when a scheduled task is misbehaving. Trigger.dev: POST /api/v1/schedules/{scheduleId}/deactivate.
Annotations the server declares
- title: Deactivate a schedule
- destructiveHint: true
trigger_pause_queuePause a queue so its runs stop being dequeued, or resume it.No findings
Why it is in this group
- The name "trigger_pause_queue" says "trigger": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Pause a queue so its runs stop being dequeued, or resume it. The containment move when a task is failing in a loop. Trigger.dev: POST /api/v1/queues/{queue}/pause.
Annotations the server declares
- title: Pause or resume a queue
- destructiveHint: true
trigger_replay_runRe-run one specific past run with the same payload.No findings
Why it is in this group
- The name "trigger_replay_run" says "trigger": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Re-run one specific past run with the same payload. This EXECUTES your production task again — the same side effects it had the first time. Trigger.dev: POST /api/v1/runs/{runId}/replay.
Annotations the server declares
- title: Replay a run
- destructiveHint: true
trigger_reschedule_runChange when a delayed run will execute.No findings
Why it is in this group
- The name "trigger_reschedule_run" says "trigger": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Change when a delayed run will execute. Only applies to runs that have not started. Trigger.dev: POST /api/v1/runs/{runId}/reschedule.
Annotations the server declares
- title: Reschedule a delayed run
- destructiveHint: true
Can't be undone 1Claude Code: ask
trigger_list_runsList task runs, filtered by status, task, tag, queue, schedule or a time window.Can send data out1 finding
Why it is in this group
- The name "trigger_list_runs" says "trigger": a word for a change.
- The input addresses people (input.to): what it sends cannot be taken back.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- outboundThe input takes a destination (input.to): what the tool writes goes there.
Findings
- Warn
The server marks "trigger_list_runs" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The name "trigger_list_runs" says "trigger": a word for a change.
Description, as the server wrote it List task runs, filtered by status, task, tag, queue, schedule or a time window. This is the main read for 'what ran, and what failed?'. Trigger.dev: GET /api/v1/runs.
Annotations the server declares
- title: List runs
- readOnlyHint: true
Changes things 14Claude Code: ask
trigger_get_batch_resultsFetch the outcome of every run in a batch.1 finding
Why it is in this group
- The name "trigger_get_batch_results" says "trigger": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "trigger_get_batch_results" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The name "trigger_get_batch_results" says "trigger": a word for a change.
Description, as the server wrote it Fetch the outcome of every run in a batch. Trigger.dev: GET /api/v1/batches/{batchId}/results.
Annotations the server declares
- title: Get a batch's results
- readOnlyHint: true
trigger_get_current_deploymentFetch the deployment currently serving the key's environment — its version, git ref and status.1 finding
Why it is in this group
- The name "trigger_get_current_deployment" says "trigger": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "trigger_get_current_deployment" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The name "trigger_get_current_deployment" says "trigger": a word for a change.
Description, as the server wrote it Fetch the deployment currently serving the key's environment — its version, git ref and status. Trigger.dev: GET /api/v1/deployments/current.
Annotations the server declares
- title: Get the current deployment
- readOnlyHint: true
trigger_get_queueFetch a single queue's concurrency limit, running count and queued count.1 finding
Why it is in this group
- The name "trigger_get_queue" says "trigger": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "trigger_get_queue" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The name "trigger_get_queue" says "trigger": a word for a change.
Description, as the server wrote it Fetch a single queue's concurrency limit, running count and queued count. Trigger.dev: GET /api/v1/queues/{queue}.
Annotations the server declares
- title: Get one queue
- readOnlyHint: true
trigger_get_runFetch a single run's outcome — its status, output, error and attempts.1 finding
Why it is in this group
- The name "trigger_get_run" says "trigger": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "trigger_get_run" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The name "trigger_get_run" says "trigger": a word for a change.
Description, as the server wrote it Fetch a single run's outcome — its status, output, error and attempts. Trigger.dev: GET /api/v1/runs/{runId}/result.
Annotations the server declares
- title: Get one run
- readOnlyHint: true
trigger_get_run_metadataFetch the mutable metadata a run has written about itself — progress, checkpoints and custom state.1 finding
Why it is in this group
- The name "trigger_get_run_metadata" says "trigger": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "trigger_get_run_metadata" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The name "trigger_get_run_metadata" says "trigger": a word for a change.
Description, as the server wrote it Fetch the mutable metadata a run has written about itself — progress, checkpoints and custom state. Trigger.dev: GET /api/v1/runs/{runId}/metadata.
Annotations the server declares
- title: Get a run's metadata
- readOnlyHint: true
trigger_get_run_spanFetch a single span from a run's trace, with its own logs and attributes.1 finding
Why it is in this group
- The name "trigger_get_run_span" says "trigger": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "trigger_get_run_span" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The name "trigger_get_run_span" says "trigger": a word for a change.
Description, as the server wrote it Fetch a single span from a run's trace, with its own logs and attributes. Trigger.dev: GET /api/v1/runs/{runId}/spans/{spanId}.
Annotations the server declares
- title: Get one span of a run
- readOnlyHint: true
trigger_get_run_traceFetch the full execution trace of a run — every span, with timings and nesting.1 finding
Why it is in this group
- The name "trigger_get_run_trace" says "trigger": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "trigger_get_run_trace" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The name "trigger_get_run_trace" says "trigger": a word for a change.
Description, as the server wrote it Fetch the full execution trace of a run — every span, with timings and nesting. The tool for 'where did this run spend its time, and where did it break?'. Trigger.dev: GET /api/v1/runs/{runId}/trace.
Annotations the server declares
- title: Get a run's trace
- readOnlyHint: true
trigger_get_scheduleFetch a single schedule with its cron expression, timezone and active state.1 finding
Why it is in this group
- The name "trigger_get_schedule" says "trigger": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "trigger_get_schedule" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The name "trigger_get_schedule" says "trigger": a word for a change.
Description, as the server wrote it Fetch a single schedule with its cron expression, timezone and active state. Trigger.dev: GET /api/v1/schedules/{scheduleId}.
Annotations the server declares
- title: Get one schedule
- readOnlyHint: true
trigger_list_bulk_actionsList bulk replay and cancel operations and their progress.1 finding
Why it is in this group
- The name "trigger_list_bulk_actions" says "trigger": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "trigger_list_bulk_actions" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The name "trigger_list_bulk_actions" says "trigger": a word for a change.
Description, as the server wrote it List bulk replay and cancel operations and their progress. Trigger.dev: GET /api/v1/bulk-actions.
Annotations the server declares
- title: List bulk actions
- readOnlyHint: true
trigger_list_env_varsList the environment variables configured for a project environment.1 finding
Why it is in this group
- The name "trigger_list_env_vars" says "trigger": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "trigger_list_env_vars" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The name "trigger_list_env_vars" says "trigger": a word for a change.
Description, as the server wrote it List the environment variables configured for a project environment. Values may be redacted depending on the key's permissions. READ ONLY — this server exposes no env-var writes. Trigger.dev: GET /api/v1/projects/{projectRef}/envvars/{env}.
Annotations the server declares
- title: List environment variables
- readOnlyHint: true
trigger_list_queuesList task queues with their concurrency limits and current depth — where you look when work is backing up.1 finding
Why it is in this group
- The name "trigger_list_queues" says "trigger": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "trigger_list_queues" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The name "trigger_list_queues" says "trigger": a word for a change.
Description, as the server wrote it List task queues with their concurrency limits and current depth — where you look when work is backing up. Trigger.dev: GET /api/v1/queues.
Annotations the server declares
- title: List queues
- readOnlyHint: true
trigger_list_run_eventsList the lifecycle events of one run — queued, dequeued, started, retried, completed.1 finding
Why it is in this group
- The name "trigger_list_run_events" says "trigger": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "trigger_list_run_events" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The name "trigger_list_run_events" says "trigger": a word for a change.
Description, as the server wrote it List the lifecycle events of one run — queued, dequeued, started, retried, completed. Trigger.dev: GET /api/v1/runs/{runId}/events.
Annotations the server declares
- title: List a run's events
- readOnlyHint: true
trigger_list_schedulesList the cron schedules configured for tasks, with their next run times.1 finding
Why it is in this group
- The name "trigger_list_schedules" says "trigger": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "trigger_list_schedules" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The name "trigger_list_schedules" says "trigger": a word for a change.
Description, as the server wrote it List the cron schedules configured for tasks, with their next run times. Trigger.dev: GET /api/v1/schedules.
Annotations the server declares
- title: List schedules
- readOnlyHint: true
trigger_list_waitpoint_tokensList outstanding waitpoint tokens — runs paused waiting for an external signal.1 finding
Why it is in this group
- The name "trigger_list_waitpoint_tokens" says "trigger": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "trigger_list_waitpoint_tokens" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The name "trigger_list_waitpoint_tokens" says "trigger": a word for a change.
Description, as the server wrote it List outstanding waitpoint tokens — runs paused waiting for an external signal. Trigger.dev: GET /api/v1/waitpoints/tokens.
Annotations the server declares
- title: List waitpoint tokens
- 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 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 out1
- 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.
Looked at Nov 20, 2026, 19:37 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
- 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: 22 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://trigger-dev.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://trigger-dev.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.
The server marks "trigger_list_runs" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The name "trigger_list_runs" says "trigger": a word for a change.
- Warntrigger_get_run
The server marks "trigger_get_run" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The name "trigger_get_run" says "trigger": a word for a change.
The server marks "trigger_get_run_trace" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The name "trigger_get_run_trace" says "trigger": a word for a change.
The server marks "trigger_get_run_span" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The name "trigger_get_run_span" says "trigger": a word for a change.
The server marks "trigger_list_run_events" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The name "trigger_list_run_events" says "trigger": a word for a change.
The server marks "trigger_get_run_metadata" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The name "trigger_get_run_metadata" says "trigger": a word for a change.
Show 9 more findingsShow fewer
The server marks "trigger_get_batch_results" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The name "trigger_get_batch_results" says "trigger": a word for a change.
The server marks "trigger_list_schedules" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The name "trigger_list_schedules" says "trigger": a word for a change.
The server marks "trigger_get_schedule" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The name "trigger_get_schedule" says "trigger": a word for a change.
The server marks "trigger_list_queues" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The name "trigger_list_queues" says "trigger": a word for a change.
The server marks "trigger_get_queue" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The name "trigger_get_queue" says "trigger": a word for a change.
The server marks "trigger_get_current_deployment" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The name "trigger_get_current_deployment" says "trigger": a word for a change.
The server marks "trigger_list_env_vars" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The name "trigger_list_env_vars" says "trigger": a word for a change.
The server marks "trigger_list_waitpoint_tokens" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The name "trigger_list_waitpoint_tokens" says "trigger": a word for a change.
The server marks "trigger_list_bulk_actions" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The name "trigger_list_bulk_actions" says "trigger": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
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: 22 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://trigger-dev.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://trigger-dev.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 trigger-dev https://trigger-dev.usefulapi.io/mcpclaude mcp add --transport http trigger-dev https://trigger-dev.usefulapi.io/mcpRun 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.
{
"permissions": {
"allow": [],
"ask": [
"mcp__trigger-dev__trigger_list_runs",
"mcp__trigger-dev__trigger_get_run",
"mcp__trigger-dev__trigger_get_run_trace",
"mcp__trigger-dev__trigger_get_run_span",
"mcp__trigger-dev__trigger_list_run_events",
"mcp__trigger-dev__trigger_get_run_metadata",
"mcp__trigger-dev__trigger_get_batch_results",
"mcp__trigger-dev__trigger_list_schedules",
"mcp__trigger-dev__trigger_get_schedule",
"mcp__trigger-dev__trigger_list_queues",
"mcp__trigger-dev__trigger_get_queue",
"mcp__trigger-dev__trigger_get_current_deployment",
"mcp__trigger-dev__trigger_list_env_vars",
"mcp__trigger-dev__trigger_list_waitpoint_tokens",
"mcp__trigger-dev__trigger_list_bulk_actions"
],
"deny": [
"mcp__trigger-dev__trigger_cancel_run",
"mcp__trigger-dev__trigger_replay_run",
"mcp__trigger-dev__trigger_reschedule_run",
"mcp__trigger-dev__trigger_add_run_tags",
"mcp__trigger-dev__trigger_activate_schedule",
"mcp__trigger-dev__trigger_deactivate_schedule",
"mcp__trigger-dev__trigger_pause_queue"
]
}
}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 trigger-dev. Review it before you use it.
Capability tags behind 1 rule
- mcp__trigger-dev__trigger_list_runs 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/io.usefulapi/trigger-dev/verify?hash=4b71c2c3a11bbf47b2accdc790b494802b0f9858c5f11f21f9a8e2aeea870249" | jq -e '.changed == false'Pinned hash 4b71c2c3a11b, from Oct 25, 2026, 23:19 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.usefulapi/trigger-dev/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.usefulapi/trigger-dev)Source: MCP Registry · repository. Synced Nov 18, 2026, 11:19 UTC.
Trigger.dev MCP by usefulapi: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Trigger.dev MCP by usefulapi safe?
- No scan can promise that. What its definitions show: 22 tools, 22 of which can change, send or delete something, and 15 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 Trigger.dev MCP by usefulapi delete data?
- Yes. 7 tools can delete, cancel or revoke something: trigger_cancel_run, trigger_replay_run, trigger_reschedule_run, trigger_add_run_tags, trigger_activate_schedule, trigger_deactivate_schedule and 1 more.
Can the Trigger.dev MCP by usefulapi do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: trigger_list_runs.
What tools does the Trigger.dev MCP by usefulapi have?
- 22 tools: 7 destructive, 1 irreversible, 14 write. trigger_cancel_run, trigger_replay_run, trigger_reschedule_run, trigger_add_run_tags, trigger_activate_schedule, trigger_deactivate_schedule, trigger_pause_queue, trigger_list_runs and 14 more.
Does the Trigger.dev MCP by usefulapi need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the Trigger.dev MCP by usefulapi send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): trigger_list_runs.
Has the Trigger.dev MCP by usefulapi changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.