io.github.mrfentmen/svix-mcp
NPM · SVIX-MCP
MCP server for Svix: applications, endpoints, MCP: real tools for real work.
Available components
Last scanned (20 hours ago)
Scores higher than 39% of npm servers
Category Communication
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 31 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 19 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1605 tokens (~61/item across 26 items; 26 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
- Stability observed for 13 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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_application" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 26 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Nov 26 63
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 21 Nov 2026 · Analysed npm/svix-mcp@1.0.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
create_application ~43
Create a Svix application. Body usually contains name and optionally uid, rateLimit and metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | yes | Svix JSON request body, passed through unchanged |
No output schema declared.
No examples provided.
create_endpoint ~66
Create a webhook endpoint on a Svix application. Body requires url and optionally description, filterTypes, channels, rateLimit and disabled.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Svix application id (app_...) |
| body | object | yes | Svix JSON request body, passed through unchanged |
No output schema declared.
No examples provided.
create_integration ~51
Create an integration on an application. Body requires name.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Svix application id (app_...) |
| body | object | yes | Svix JSON request body, passed through unchanged |
No output schema declared.
No examples provided.
create_message ~65
Send a message to the endpoints of an application. Body requires eventType and payload; eventId, channels and tags are optional.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Svix application id (app_...) |
| body | object | yes | Svix JSON request body, passed through unchanged |
No output schema declared.
No examples provided.
delete_application ~43
Permanently delete a Svix application and every endpoint and message it owns. This cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Svix application id (app_...) |
No output schema declared.
No examples provided.
delete_endpoint ~58
Delete a webhook endpoint. Messages already delivered stay in the log, but no further deliveries are attempted.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Svix application id (app_...) |
| endpoint_id | string | yes | Svix endpoint id (ep_...) |
No output schema declared.
No examples provided.
delete_integration ~47
Delete an integration from an application.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Svix application id (app_...) |
| integ_id | string | yes | Svix integration id (integ_...) |
No output schema declared.
No examples provided.
get_application ~32
Fetch a single Svix application by id.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Svix application id (app_...) |
No output schema declared.
No examples provided.
get_attempt ~69
Fetch one delivery attempt, including the response body returned by the receiver.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Svix application id (app_...) |
| attempt_id | string | yes | Svix delivery attempt id (atmpt_...) |
| msg_id | string | yes | Svix message id (msg_...) |
No output schema declared.
No examples provided.
get_endpoint ~46
Fetch a single webhook endpoint by id.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Svix application id (app_...) |
| endpoint_id | string | yes | Svix endpoint id (ep_...) |
No output schema declared.
No examples provided.
get_endpoint_secret ~56
Read an endpoint's webhook signing secret, which is used to verify Svix signatures.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Svix application id (app_...) |
| endpoint_id | string | yes | Svix endpoint id (ep_...) |
No output schema declared.
No examples provided.
get_endpoint_stats ~89
Get delivery counts (success, pending, fail) for an endpoint, optionally within a time window.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Svix application id (app_...) |
| endpoint_id | string | yes | Svix endpoint id (ep_...) |
| since | string | – | ISO 8601 start of the window |
| until | string | – | ISO 8601 end of the window |
No output schema declared.
No examples provided.
get_integration ~47
Fetch a single integration by id.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Svix application id (app_...) |
| integ_id | string | yes | Svix integration id (integ_...) |
No output schema declared.
No examples provided.
get_integration_key ~53
Read the key an integration uses to authenticate with Svix.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Svix application id (app_...) |
| integ_id | string | yes | Svix integration id (integ_...) |
No output schema declared.
No examples provided.
get_message ~50
Fetch a single message, including its payload, by id.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Svix application id (app_...) |
| msg_id | string | yes | Svix message id (msg_...) |
No output schema declared.
No examples provided.
list_applications ~63
List Svix applications in the current environment. Use the returned iterator to page further.
| Name | Type | Req | Description |
|---|---|---|---|
| iterator | string | – | Pagination cursor copied from a previous response's iterator |
| limit | integer | – | Page size, 1-250 (Svix default is 50) |
No output schema declared.
No examples provided.
list_endpoint_attempts ~88
List delivery attempts made to one endpoint across all messages.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Svix application id (app_...) |
| endpoint_id | string | yes | Svix endpoint id (ep_...) |
| iterator | string | – | Pagination cursor copied from a previous response's iterator |
| limit | integer | – | Page size, 1-250 (Svix default is 50) |
No output schema declared.
No examples provided.
list_endpoints ~72
List the webhook endpoints registered on a Svix application.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Svix application id (app_...) |
| iterator | string | – | Pagination cursor copied from a previous response's iterator |
| limit | integer | – | Page size, 1-250 (Svix default is 50) |
No output schema declared.
No examples provided.
list_integrations ~76
List the integrations (Slack, Discord and similar) configured on an application.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Svix application id (app_...) |
| iterator | string | – | Pagination cursor copied from a previous response's iterator |
| limit | integer | – | Page size, 1-250 (Svix default is 50) |
No output schema declared.
No examples provided.
list_message_attempts ~89
List the delivery attempts made for one message, newest first.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Svix application id (app_...) |
| iterator | string | – | Pagination cursor copied from a previous response's iterator |
| limit | integer | – | Page size, 1-250 (Svix default is 50) |
| msg_id | string | yes | Svix message id (msg_...) |
No output schema declared.
No examples provided.
list_messages ~69
List messages sent through a Svix application.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Svix application id (app_...) |
| iterator | string | – | Pagination cursor copied from a previous response's iterator |
| limit | integer | – | Page size, 1-250 (Svix default is 50) |
No output schema declared.
No examples provided.
rotate_endpoint_secret ~79
Rotate an endpoint's signing secret. Optionally pass { key } to set your own secret instead of a generated one.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Svix application id (app_...) |
| body | object | – | Svix JSON request body, passed through unchanged |
| endpoint_id | string | yes | Svix endpoint id (ep_...) |
No output schema declared.
No examples provided.
rotate_integration_key ~53
Rotate an integration's key, invalidating the previous one.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Svix application id (app_...) |
| integ_id | string | yes | Svix integration id (integ_...) |
No output schema declared.
No examples provided.
update_application ~59
Update a Svix application. Send the full application body, including the name you want to keep.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Svix application id (app_...) |
| body | object | yes | Svix JSON request body, passed through unchanged |
No output schema declared.
No examples provided.
update_endpoint ~73
Update a webhook endpoint. Send the full endpoint body, including the url you want to keep.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Svix application id (app_...) |
| body | object | yes | Svix JSON request body, passed through unchanged |
| endpoint_id | string | yes | Svix endpoint id (ep_...) |
No output schema declared.
No examples provided.
update_integration ~69
Rename or reconfigure an integration. Send the full integration body.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Svix application id (app_...) |
| body | object | yes | Svix JSON request body, passed through unchanged |
| integ_id | string | yes | Svix integration id (integ_...) |
No output schema declared.
No examples provided.
How do I install the io.github.mrfentmen/svix-mcp server?
io.github.mrfentmen/svix-mcp runs locally as an npm package, launched with npx -y svix-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · svix-mcp
claude mcp add mrfentmen-svix-mcp -- npx -y svix-mcp
What is the io.github.mrfentmen/svix-mcp server?
io.github.mrfentmen/svix-mcp is listed in the public MCP registry as io.github.mrfentmen/svix-mcp. MCP server for Svix: applications, endpoints, MCP: real tools for real work. This page covers its npm package (svix-mcp).
Is the io.github.mrfentmen/svix-mcp server safe to use?
io.github.mrfentmen/svix-mcp scores 69 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 2026. It declares no install or post-install scripts. 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.github.mrfentmen/svix-mcp server expose?
io.github.mrfentmen/svix-mcp exposes 26 tools: list_applications, create_application, get_application, update_application, delete_application, and 21 more. Their descriptions and schemas cost roughly 1,605 tokens of context every time the server is loaded.
Is the io.github.mrfentmen/svix-mcp server still maintained?
io.github.mrfentmen/svix-mcp is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.mrfentmen/svix-mcp server under?
io.github.mrfentmen/svix-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the io.github.mrfentmen/svix-mcp server?
VerifyMCP ran 16 checks on io.github.mrfentmen/svix-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.