Inngest MCP by usefulapi

by usefulapi.io · remote · no sign-in to list tools · v1.16.4 · published by io.usefulapi

Trace events to function runs to the failing step, and bulk-cancel runs.

Deletes · 3

Compare Registry entry

11 tools: 3 can delete or cancel things and 8 only read.

Scanned Oct 22, 2026

Deletes or cancels3Claude Code: deny: see these tools
Can't be undone0Claude Code: ask
Changes things0Claude Code: ask
Only reads8Claude Code: allow: see these tools

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http inngest https://inngest.usefulapi.io/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

11 tools

Deletes or cancels 3Removes, cancels or revokes something.Claude Code: deny

inngest_create_cancellationCancel every run of one function that started within a time window, optionally narrowed by an event expression.No findings
Why it is in this group
- The name "inngest_create_cancellation" says "create": 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 every run of one function that started within a time window, optionally narrowed by an event expression. This STOPS IN-FLIGHT WORK across your production functions — scope the window tightly. Runs already finished are unaffected. Inngest: POST /v1/cancellations.
Annotations the server declares
- title: Bulk cancel function runs
- destructiveHint: true
inngest_delete_cancellationDelete a bulk-cancellation job so it stops cancelling further runs.No findings
Why it is in this group
- The name "inngest_delete_cancellation" says "delete": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
Delete a bulk-cancellation job so it stops cancelling further runs. Runs it already cancelled stay cancelled. Inngest: DELETE /v1/cancellations/{cancellationId}.
Annotations the server declares
- title: Stop a bulk cancellation
- destructiveHint: true
inngest_delete_webhookRemove a webhook ingress.No findings
Why it is in this group
- The name "inngest_delete_webhook" says "delete": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
Remove a webhook ingress. The external source stops producing events immediately. Inngest: DELETE /v1/webhooks/{webhookId}.
Annotations the server declares
- title: Delete a webhook
- destructiveHint: true

Only reads 8Looks things up and changes nothing.Claude Code: allow

inngest_get_eventFetch a single event with its name, payload and timestamp.No findings
Why it is in this group
- The name "inngest_get_event" says "get": a word for reading.
Description, as the server wrote it
Fetch a single event with its name, payload and timestamp. Inngest: GET /v1/events/{eventId}.
Annotations the server declares
- title: Get one event
- readOnlyHint: true
inngest_get_runFetch a single function run — its status, output and error.No findings
Why it is in this group
- The name "inngest_get_run" says "get": a word for reading.
Description, as the server wrote it
Fetch a single function run — its status, output and error. Inngest: GET /v1/runs/{runId}.
Annotations the server declares
- title: Get one function run
- readOnlyHint: true
inngest_get_webhookFetch a single webhook ingress with its URL and transform.Reads text others writeNo findings
Why it is in this group
- The name "inngest_get_webhook" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "fetch" and "url": it reads web pages, which anyone can write.
Description, as the server wrote it
Fetch a single webhook ingress with its URL and transform. Inngest: GET /v1/webhooks/{webhookId}.
Annotations the server declares
- title: Get one webhook
- readOnlyHint: true
inngest_list_cancellationsList bulk-cancellation jobs and their progress.No findings
Why it is in this group
- The name "inngest_list_cancellations" says "list": a word for reading.
Description, as the server wrote it
List bulk-cancellation jobs and their progress. Inngest: GET /v1/cancellations.
Annotations the server declares
- title: List bulk cancellations
- readOnlyHint: true
inngest_list_event_runsList every function run one event triggered, with each run's status.No findings
Why it is in this group
- The name "inngest_list_event_runs" says "list": a word for reading.
Description, as the server wrote it
List every function run one event triggered, with each run's status. This is the hop from 'this event arrived' to 'and here is what it did'. Inngest: GET /v1/events/{eventId}/runs.
Annotations the server declares
- title: List the runs an event started
- readOnlyHint: true
inngest_list_eventsList the events received in the key's environment, newest first.No findings
Why it is in this group
- The name "inngest_list_events" says "list": a word for reading.
Description, as the server wrote it
List the events received in the key's environment, newest first. Events are what start functions, so this is where an investigation begins. Inngest: GET /v1/events.
Annotations the server declares
- title: List events
- readOnlyHint: true
inngest_list_run_jobsList the individual steps (jobs) of one run, with their status and timing — how you find which step of a durable function failed.No findings
Why it is in this group
- The name "inngest_list_run_jobs" says "list": a word for reading.
Description, as the server wrote it
List the individual steps (jobs) of one run, with their status and timing — how you find which step of a durable function failed. Inngest: GET /v1/runs/{runId}/jobs.
Annotations the server declares
- title: List a run's steps
- readOnlyHint: true
inngest_list_webhooksList the webhook ingresses configured for the environment — the external sources that turn into events.No findings
Why it is in this group
- The name "inngest_list_webhooks" says "list": a word for reading.
Description, as the server wrote it
List the webhook ingresses configured for the environment — the external sources that turn into events. Inngest: GET /v1/webhooks.
Annotations the server declares
- title: List webhooks
- 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 outbound.

Reads private data0: Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1: Brings in text someone else can write: web pages, inbound email, messages, issues and comments.; inngest_get_webhook
Can send data out0: 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 Oct 22, 2026, 15:29 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable: yes
HTTP status of an anonymous initialize: 200
tools/list served without credentials: yes
Tools that change things, listed without credentials: 3
Protocol version: 2025-06-18
WWW-Authenticate on 401: not observed
resource_metadata in WWW-Authenticate: none
RFC 9728 protected resource metadata: https://inngest.usefulapi.io/.well-known/oauth-protected-resource/mcp
Authorization servers: https://inngest.usefulapi.io
Legacy HTTP+SSE transport: no
Dynamic client registration: yes
Client ID metadata documents: no

HighThe whole server
The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 destructive). Whether a call also works without credentials was not tested: tools are never called.
Matched text
https://inngest.usefulapi.io/mcp: tools/list returned 11 tools to an anonymous client, including inngest_create_cancellation (destructive), inngest_delete_cancellation (destructive), inngest_delete_webhook (destructive)
What this check looks for

Install

Pinned to version 1.16.4. Values in angle brackets are yours to fill in.

claude mcp add --transport http inngest https://inngest.usefulapi.io/mcp

Run 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.

.claude/settings.json

{
  "permissions": {
    "allow": [
      "mcp__inngest__inngest_list_events",
      "mcp__inngest__inngest_get_event",
      "mcp__inngest__inngest_list_event_runs",
      "mcp__inngest__inngest_get_run",
      "mcp__inngest__inngest_list_run_jobs",
      "mcp__inngest__inngest_list_cancellations",
      "mcp__inngest__inngest_list_webhooks",
      "mcp__inngest__inngest_get_webhook"
    ],
    "ask": [],
    "deny": [
      "mcp__inngest__inngest_create_cancellation",
      "mcp__inngest__inngest_delete_cancellation",
      "mcp__inngest__inngest_delete_webhook"
    ]
  }
}

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 inngest. Review it before you use it.

Capability tags behind 1 rule

mcp__inngest__inngest_get_webhook untrusted-input

Keep track

Get told when this server's tools change: a new tool, a new description, a new class.

https://anlyon.dev/servers/io.usefulapi/inngest/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Anlyon alternative

3 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 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 →

Compare with other servers for the same product.

Source: MCP Registry · repository. Synced Oct 22, 2026, 11:18 UTC.

For agents: Markdown · JSON · report this listing