io.usefulapi/trigger-dev
REMOTE · TRIGGER-DEV.USEFULAPI.IO · SCANNED OCT 4
Debug background jobs — runs, traces, spans, schedules, queues and deployments.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability85
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1594 tokens (~72/item across 22 items; 22 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 22 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 22 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.usefulapi/trigger-dev MCP server?
io.usefulapi/trigger-dev is a hosted endpoint at https://trigger-dev.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · trigger-dev.usefulapi.io
claude mcp add --transport http io-usefulapi-trigger-dev 'https://trigger-dev.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-trigger-dev": {
"url": "https://trigger-dev.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-trigger-dev": {
"type": "http",
"url": "https://trigger-dev.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-trigger-dev] url = "https://trigger-dev.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-trigger-dev": {
"type": "remote",
"url": "https://trigger-dev.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-trigger-dev --url 'https://trigger-dev.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-trigger-dev:
url: "https://trigger-dev.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-trigger-dev": {
"Transport": "http",
"Url": "https://trigger-dev.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-trigger-dev -t streamable-http -u 'https://trigger-dev.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-trigger-dev": {
"type": "http",
"url": "https://trigger-dev.usefulapi.io/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Oct 26 +60
- HTTPS: unverified → pass ▲ security
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.07 ▲ functional
- 3 Oct 26 −59
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- HTTPS: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 2 Oct 26 +59
- HTTPS: unverified → pass ▲ security
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- First check of Judged manipulation: pass security
- First check of Authorization: partial security
- MCP protocol: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: pass functional
- First check of Tool coverage: 100 functional
- 29 Sept 26 18
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Oct 2026 · Probed https://trigger-dev.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of trigger-dev.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://trigger-dev.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://trigger-dev.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://trigger-dev.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://trigger-dev.usefulapi.io/mcp |
| Authorisation server | https://trigger-dev.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://trigger-dev.usefulapi.io/mcp | Verified | 200 | |
| http (plaintext) | http://trigger-dev.usefulapi.io/mcp | HTTPS enforced | 301 | https://trigger-dev.usefulapi.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
trigger_activate_schedule Activate a schedule ~46
Resume a paused schedule so it fires again. Trigger.dev: POST /api/v1/schedules/{scheduleId}/activate.
| Name | Type | Req | Description |
|---|---|---|---|
| schedule_id | string | yes | The schedule to activate. |
No output schema declared.
No examples provided.
trigger_add_run_tags Add tags to a run ~66
Attach tags to a run so you can filter for it later. Additive and safe. Trigger.dev: POST /api/v1/runs/{runId}/tags.
| Name | Type | Req | Description |
|---|---|---|---|
| run_id | string | yes | The run to tag. |
| tags | array | yes | Tags to add. |
No output schema declared.
No examples provided.
trigger_cancel_run Cancel a run ~58
Cancel an in-flight run. Note this is the one endpoint on API v2, not v1. Trigger.dev: POST /api/v2/runs/{runId}/cancel.
| Name | Type | Req | Description |
|---|---|---|---|
| run_id | string | yes | The run to cancel. |
No output schema declared.
No examples provided.
trigger_deactivate_schedule Deactivate a schedule ~60
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.
| Name | Type | Req | Description |
|---|---|---|---|
| schedule_id | string | yes | The schedule to pause. |
No output schema declared.
No examples provided.
trigger_get_batch_results Get a batch's results ~52
Fetch the outcome of every run in a batch. Trigger.dev: GET /api/v1/batches/{batchId}/results.
| Name | Type | Req | Description |
|---|---|---|---|
| batch_id | string | yes | The batch's id (batch_...). |
No output schema declared.
No examples provided.
trigger_get_current_deployment Get the current deployment ~42
Fetch the deployment currently serving the key's environment — its version, git ref and status. Trigger.dev: GET /api/v1/deployments/current.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
trigger_get_queue Get one queue ~49
Fetch a single queue's concurrency limit, running count and queued count. Trigger.dev: GET /api/v1/queues/{queue}.
| Name | Type | Req | Description |
|---|---|---|---|
| queue | string | yes | The queue's name or id. |
No output schema declared.
No examples provided.
trigger_get_run Get one run ~57
Fetch a single run's outcome — its status, output, error and attempts. Trigger.dev: GET /api/v1/runs/{runId}/result.
| Name | Type | Req | Description |
|---|---|---|---|
| run_id | string | yes | The run's id (run_...). |
No output schema declared.
No examples provided.
trigger_get_run_metadata Get a run's metadata ~56
Fetch the mutable metadata a run has written about itself — progress, checkpoints and custom state. Trigger.dev: GET /api/v1/runs/{runId}/metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| run_id | string | yes | The run's id. |
No output schema declared.
No examples provided.
trigger_get_run_span Get one span of a run ~75
Fetch a single span from a run's trace, with its own logs and attributes. Trigger.dev: GET /api/v1/runs/{runId}/spans/{spanId}.
| Name | Type | Req | Description |
|---|---|---|---|
| run_id | string | yes | The run's id. |
| span_id | string | yes | The span's id, from the trace. |
No output schema declared.
No examples provided.
trigger_get_run_trace Get a run's trace ~74
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.
| Name | Type | Req | Description |
|---|---|---|---|
| run_id | string | yes | The run's id. |
No output schema declared.
No examples provided.
trigger_get_schedule Get one schedule ~53
Fetch a single schedule with its cron expression, timezone and active state. Trigger.dev: GET /api/v1/schedules/{scheduleId}.
| Name | Type | Req | Description |
|---|---|---|---|
| schedule_id | string | yes | The schedule's id (sched_...). |
No output schema declared.
No examples provided.
trigger_list_bulk_actions List bulk actions ~47
List bulk replay and cancel operations and their progress. Trigger.dev: GET /api/v1/bulk-actions.
| Name | Type | Req | Description |
|---|---|---|---|
| pageSize | integer | – | Page size, 1-100. |
No output schema declared.
No examples provided.
trigger_list_env_vars List environment variables ~89
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| environment | string | yes | Which environment's variables to list. |
| project_ref | string | yes | The project reference (proj_...). |
No output schema declared.
No examples provided.
trigger_list_queues List queues ~56
List task queues with their concurrency limits and current depth — where you look when work is backing up. Trigger.dev: GET /api/v1/queues.
| Name | Type | Req | Description |
|---|---|---|---|
| pageSize | integer | – | Page size, 1-100. |
No output schema declared.
No examples provided.
trigger_list_run_events List a run's events ~58
List the lifecycle events of one run — queued, dequeued, started, retried, completed. Trigger.dev: GET /api/v1/runs/{runId}/events.
| Name | Type | Req | Description |
|---|---|---|---|
| run_id | string | yes | The run's id. |
No output schema declared.
No examples provided.
trigger_list_runs List runs ~290
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.
| Name | Type | Req | Description |
|---|---|---|---|
| after | string | – | Cursor from the previous page's pagination. Omit for the first page. |
| batch | string | – | Only runs in this batch. |
| from | string | – | Epoch milliseconds lower bound on creation time. |
| isTest | boolean | – | Only test runs, or only real ones. |
| machine | array | – | Only runs on these machine presets. |
| pageSize | integer | – | Page size, 1-100. |
| period | string | – | Relative window, e.g. "1h", "24h", "7d". |
| queue | array | – | Only runs on these queues. |
| schedule | string | – | Only runs created by this schedule. |
| status | array | – | Only runs in these states, e.g. ["FAILED","CRASHED"]. Others include PENDING, EXECUTING, COMPLETED, CANCELED, TIMED_OUT. |
| tag | array | – | Only runs carrying these tags. |
| taskIdentifier | array | – | Only runs of these task ids. |
| to | string | – | Epoch milliseconds upper bound on creation time. |
| version | string | – | Only runs of this deployment version. |
No output schema declared.
No examples provided.
trigger_list_schedules List schedules ~62
List the cron schedules configured for tasks, with their next run times. Trigger.dev: GET /api/v1/schedules.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | 1-based page number. |
| pageSize | integer | – | Page size, 1-100. |
No output schema declared.
No examples provided.
trigger_list_waitpoint_tokens List waitpoint tokens ~75
List outstanding waitpoint tokens — runs paused waiting for an external signal. Trigger.dev: GET /api/v1/waitpoints/tokens.
| Name | Type | Req | Description |
|---|---|---|---|
| after | string | – | Cursor from the previous page's pagination. Omit for the first page. |
| pageSize | integer | – | Page size, 1-100. |
No output schema declared.
No examples provided.
trigger_pause_queue Pause or resume a queue ~78
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.
| Name | Type | Req | Description |
|---|---|---|---|
| paused | boolean | yes | true to pause, false to resume. |
| queue | string | yes | The queue's name or id. |
No output schema declared.
No examples provided.
trigger_replay_run Replay a run ~68
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.
| Name | Type | Req | Description |
|---|---|---|---|
| run_id | string | yes | The run to replay. |
No output schema declared.
No examples provided.
trigger_reschedule_run Reschedule a delayed run ~83
Change when a delayed run will execute. Only applies to runs that have not started. Trigger.dev: POST /api/v1/runs/{runId}/reschedule.
| Name | Type | Req | Description |
|---|---|---|---|
| delay | string | yes | New delay or timestamp, e.g. "1h" or an ISO-8601 datetime. |
| run_id | string | yes | The delayed run to move. |
No output schema declared.
No examples provided.
What is the io.usefulapi/trigger-dev MCP server?
io.usefulapi/trigger-dev is an MCP server listed in the public MCP registry as io.usefulapi/trigger-dev. Debug background jobs, runs, traces, spans, schedules, queues and deployments. This page covers its hosted endpoint (https://trigger-dev.usefulapi.io/mcp).
Is the io.usefulapi/trigger-dev MCP server safe to use?
io.usefulapi/trigger-dev scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.usefulapi/trigger-dev MCP server expose?
io.usefulapi/trigger-dev exposes 22 tools: trigger_list_runs, trigger_get_run, trigger_get_run_trace, trigger_get_run_span, trigger_list_run_events, and 17 more. Their descriptions and schemas cost roughly 1,594 tokens of context every time the server is loaded.
Does the io.usefulapi/trigger-dev MCP server require authentication?
Yes. io.usefulapi/trigger-dev asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the io.usefulapi/trigger-dev MCP server still maintained?
io.usefulapi/trigger-dev is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.