mcpbeat Sign in

Svix MCP by usefulapi MCP Server

answering

Svix MCP by usefulapi is answering right now. Last checked 12 min ago. It exposes 19 tools. Last commit 12 Oct 2026.

Send and debug webhooks — applications, endpoints, messages, delivery attempts and replays.

Uptime history 13 days of history
13 days agonow
100.0%
Uptime 24h
91 of 91 checks
19
Tools
read from the server
100 ms
Response time
average over 24h
0
Stars
last commit 12 Oct 2026

What changed 6

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 1 October 2026. No other catalogue keeps this.

9 Oct a tool changed version4 times that day
8 Oct a tool changed version
1 Oct a tool changed version
and 3 more, back to 1 October 2026

Nothing serious here today

Today is the operative word: we check Svix MCP by usefulapi every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.

run in your terminal
claude mcp add svix --transport http https://svix.usefulapi.io/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "svix": {
      "url": "https://svix.usefulapi.io/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.svix]
url = "https://svix.usefulapi.io/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "svix": {
      "url": "https://svix.usefulapi.io/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "svix": {
      "url": "https://svix.usefulapi.io/mcp"
    }
  }
}

Available tools 19

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

svix
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_get_application
Fetch a single application by its Svix id or your own uid. Svix REST: GET /api/v1/app/{app_id}.
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_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_get_message
Fetch a single message, including its event type and payload. Svix REST: GET /api/v1/app/{app_id}/msg/{msg_id}.
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_list_applications
List the applications (your tenants/customers) in the Svix environment. Svix REST: GET /api/v1/app.
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_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_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_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_endpoints
List the webhook endpoints registered for one application. Svix REST: GET /api/v1/app/{app_id}/endpoint.
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_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_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.
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_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.

Endpoints

URLTransportStateLatencyChecked
https://svix.usefulapi.io/mcp streamable-http answering 73 ms 12 min ago

Alternatives to Svix MCP by usefulapi

same job, measured the same way
BulkSMS MCP by usefulapi
by usefulapi

Read BulkSMS messages, replies, profile and webhooks; send SMS to up to 10 numbers.

8 tools answering
Missive MCP by usefulapi
by usefulapi

Read email/chat conversations, messages, contacts and teams; draft, send and update threads.

19 tools answering
Railhook
by vadymkykalo

Webhooks for AI agents: send events, manage endpoints, inspect and retry deliveries.

383 installs/wk answering
api.video MCP by usefulapi
by usefulapi

Manage videos and live streams, inspect captions, players and webhooks, and read play analytics.

15 tools answering
Re:amaze MCP by usefulapi
by usefulapi

Manage Re:amaze conversations, messages, contacts and help articles.

17 tools answering
Customer.io MCP by usefulapi
by usefulapi

Query people, segments, campaigns, and message deliveries; send transactional email or broadcasts.

13 tools answering
Stream MCP by usefulapi
by usefulapi

Query channels, search messages, and read threads, users and reactions in your Stream Chat app.

13 tools answering
Messente MCP by usefulapi
by usefulapi

Read Messente balance, prices, delivery status and statistics; send SMS to up to 10 numbers.

9 tools answering

Svix MCP by usefulapi — questions

Answers built from our own checks of this server.

What can Svix MCP by usefulapi do?
It exposes 19 tools, read directly from the server on our last check. Among them: svix_create_application, svix_create_endpoint, svix_get_application, svix_get_endpoint, svix_get_endpoint_stats, svix_get_event_type and 13 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Svix MCP by usefulapi working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 100 ms. The bar chart above shows every period we have measured.
How do I connect Svix MCP by usefulapi?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Svix MCP by usefulapi need an API key?
No. Svix MCP by usefulapi completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 19 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Svix MCP by usefulapi?
It answers our handshake in 100 ms on average, which is faster than 85% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Svix MCP by usefulapi open source?
Yes — it is published under the MIT licence, written in JavaScript, 0 stars on GitHub and 1 open issue. The source link is on this page, so you can read exactly what it does with your data before you connect it.