Svix MCP by usefulapi

Reviewed 1d ago.

• tools: 19 tools scanned
• metadata: scanned

No findings.

Tools (19)

• svix_list_applications

  List the applications (your tenants/customers) in the Svix environment. Svix REST: GET /api/v1/app.

• svix_get_application

  Fetch a single application by its Svix id or your own uid. Svix REST: GET /api/v1/app/{app_id}.

• svix_list_endpoints

  List the webhook endpoints registered for one application. Svix REST: GET /api/v1/app/{app_id}/endpoint.

• svix_get_endpoint

  Fetch a single webhook endpoint, including its URL, subscribed event types and channels. Svix REST: GET /api/v1/app/{app_id}/endpoint/{endpoint_id}.

• svix_get_endpoint_stats

  Read delivery statistics for one endpoint — counts of success, pending, sending and fail. The fastest way to see whether an endpoint is healthy. Svix REST: GET /api/v1/app/{app_id}/endpoint/{endpoint_id}/stats.

• svix_list_messages

  List the webhook messages sent for one application, newest first. Filter by event type, channel, tag or time window. Svix REST: GET /api/v1/app/{app_id}/msg.

• svix_get_message

  Fetch a single message, including its event type and payload. Svix REST: GET /api/v1/app/{app_id}/msg/{msg_id}.

• svix_list_attempts_by_message

  List every delivery attempt Svix made for one message, across endpoints — status, response code and body. This is the tool for answering 'why did this webhook not arrive?'. Svix REST: GET /api/v1/app/{app_id}/attempt/msg/{msg_id}.

• svix_list_attempts_by_endpoint

  List delivery attempts against one endpoint, newest first. Filter by status to find the failures. Svix REST: GET /api/v1/app/{app_id}/attempt/endpoint/{endpoint_id}.

• svix_list_endpoint_messages

  List the messages destined for one endpoint, with each message's delivery status. Svix REST: GET /api/v1/app/{app_id}/endpoint/{endpoint_id}/msg.

• svix_list_event_types

  List the event types defined in the environment — the catalogue endpoints can subscribe to. Svix REST: GET /api/v1/event-type.

• svix_get_event_type

  Fetch a single event type by name, including its description and JSON schema. Svix REST: GET /api/v1/event-type/{event_type_name}.

• svix_list_background_tasks

  List Svix background tasks (bulk replays, expunges, imports) with their status. Use it to follow up a recover or replay. Svix REST: GET /api/v1/background-task.

• svix_health

  Check that the Svix API is reachable and the API key works. Returns 200 with an empty body when healthy. Svix REST: GET /api/v1/health.

• svix_create_application

  Create a new application (one tenant/customer of yours) in the Svix environment. Svix REST: POST /api/v1/app.

• svix_create_endpoint

  Register a webhook endpoint URL for one application, optionally scoped to specific event types and channels. Svix REST: POST /api/v1/app/{app_id}/endpoint.

• svix_send_message

  Send a webhook message to every endpoint of an application subscribed to the event type. This delivers real traffic to your customers' URLs. Svix REST: POST /api/v1/app/{app_id}/msg.

• svix_resend_message

  Queue one message for redelivery to one endpoint. The usual fix after a customer's endpoint was down. Svix REST: POST /api/v1/app/{app_id}/msg/{msg_id}/endpoint/{endpoint_id}/resend.

• svix_recover_endpoint

  Replay every failed message for one endpoint since a timestamp. Runs as a background task — follow it with svix_list_background_tasks. Svix REST: POST /api/v1/app/{app_id}/endpoint/{endpoint_id}/recover.