SendMock
NPM · SENDMOCK · 2 COMPONENTS
Test email, SMS, payments and webhooks locally: read messages, OTPs and webhook deliveries.
Available components
Last scanned (3 hours ago)
Scores higher than 41% of npm servers
Category Testing and QA
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 Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 0 of 6 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to shibbirweb/sendmock). View diagnostics → Pass
- Clear OSI-approved license (MIT OR Apache-2.0).Pass
- Actively maintained (last published 0 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 10479 tokens (~85/item across 123 items; 118 tools + 5 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
- 99% of tools have a non-trivial description (not blank, and not just the tool's name).Partial
- 89% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 30 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 120 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (15)
- 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
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Malware scan in Supply Chain SecurityMalware scan not yet available for this package.
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.
- 21 Nov 26 −14
- Malware scan: pass → unverified ▼ security
- Known CVEs: pass → unverified ▼ security
- Dependency health: 1.00 → unverified ▼ functional
- Package version: 1.2.0 → 1.3.1 functional
- Package version: 1.2.0 → 1.3.0 functional
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Nov 26 0
- Tool safety: pass → unverified ▼ security
- Stability: 0.03 → unverified ▼ security
- Tool coverage: 99 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Package version: 1.1.0 → 1.2.0 functional
- 16 Nov 26 +2
- Tool safety: pass → unverified ▼ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Tool coverage: 99 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Security disclosure: unverified → pass ▲ functional
- Package version: 1.0.0 → 1.1.0 functional
- 15 Nov 26 81
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/sendmock@1.3.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | shibbirweb/sendmock |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/shibbirweb/sendmock/.github/workflows/registry-publish.yml@refs/heads/main |
| Rekor log index | 4033864441 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:f0e0ea3752d5cc2634b8970b574e0e264b4296baa089273fab548081fdc413d25627a9d36c2f68802e971a8458691114727a912592a974fb1ec380d2a |
Background: How many MCP packages publish verified provenance →
Dependencies 6 packages
| Packages resolved | 6 |
|---|---|
| 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 →
sendmock_webhook_metrics ~47
Volume, success rate, latency and failures over a range.
| Name | Type | Req | Description |
|---|---|---|---|
| endpoint_id | string|null | – | Only this endpoint. |
| range | – | yes | 24h or 7d. |
No output schema declared.
No examples provided.
sendmock_webhook_render ~166
Render an unsaved endpoint's request against a message.
| Name | Type | Req | Description |
|---|---|---|---|
| email_id | string|null | – | Render against this email; without an email, SMS or request ID the sample event is used. |
| endpoint | – | – | The endpoint settings to render, saved or not; left out, the saved endpoint `endpoint_id` names is rendered as stored. |
| endpoint_id | string|null | – | A saved endpoint's own variables are used too; alone, its stored settings are rendered. |
| http_request_id | string|null | – | Render against this captured HTTP request. |
| sms_id | string|null | – | Render against this SMS. |
| variables | object|null | – | Send-time values by variable name (no `vars.`); they win for this render (WH-05.5). |
No output schema declared.
No examples provided.
sendmock_webhook_rule_create ~100
Add a rule.
| Name | Type | Req | Description |
|---|---|---|---|
| endpoint_id | string | yes | The endpoint deliveries go to. |
| events | array | yes | The events the rule listens to, e.g. `email.received`. |
| filter | – | yes | Only events whose message passes the filter fire; null passes every one. |
| is_enabled | boolean | yes | Off rules are kept but never fire. |
| name | string | yes | A name for the rule, shown in the list. |
No output schema declared.
No examples provided.
sendmock_webhook_rule_delete ~40
Delete a rule.
| Name | Type | Req | Description |
|---|---|---|---|
| rule_id | string | yes | The rule's ID, from `GET /api/v1/webhooks/rules`. |
No output schema declared.
No examples provided.
sendmock_webhook_rule_get ~43
One webhook rule with its filter.
| Name | Type | Req | Description |
|---|---|---|---|
| rule_id | string | yes | The rule's ID, from `GET /api/v1/webhooks/rules`. |
No output schema declared.
No examples provided.
sendmock_webhook_rule_list ~25
Which events go to which endpoint, checked from top to bottom.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
sendmock_webhook_rule_match ~221
Which webhooks an event would trigger, before an action fires it.
| Name | Type | Req | Description |
|---|---|---|---|
| data | object|null | – | Filter fields by name, for a message not stored yet or the values the event changes, e.g. `{ "to": ["support@app.test"], "header:x-tenant": ["acme"] }`; they win over the stored message's. |
| event_type | string | yes | The event the action fires, e.g. `email.bounced` or `sms.status`. |
| include_requests | boolean|null | – | Also render the request each matching endpoint would send for the event, with secrets masked (WH-14.1). |
| subject_id | string|null | – | The email, SMS, payment or push notification the event is about; its stored fields are what the rule filters read. |
| webhook_endpoint_ids | array|null | – | With `include_requests`, render these endpoints' requests too, as chosen for the action instead of the rules (IDs from `GET /api/v1/webhooks/endpoints`). |
No output schema declared.
No examples provided.
sendmock_webhook_rule_move ~69
Move a rule up or down; answers the reordered list.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | – | yes | `up` fires the rule one place earlier, `down` one place later. |
| rule_id | string | yes | The rule's ID, from `GET /api/v1/webhooks/rules`. |
No output schema declared.
No examples provided.
sendmock_webhook_rule_preview ~53
Which recent messages an unsaved rule would match.
| Name | Type | Req | Description |
|---|---|---|---|
| events | array | yes | The events of the unsaved rule. |
| filter | – | yes | The filter of the unsaved rule; null passes every message. |
No output schema declared.
No examples provided.
sendmock_webhook_rule_update ~85
Change a rule; send only the changed keys.
| Name | Type | Req | Description |
|---|---|---|---|
| endpoint_id | string|null | – | – |
| events | array|null | – | – |
| filter | – | – | – |
| is_enabled | boolean|null | – | – |
| name | string|null | – | – |
| rule_id | string | yes | The rule's ID, from `GET /api/v1/webhooks/rules`. |
No output schema declared.
No examples provided.
sendmock_webhook_saved_create ~46
Save a delivery's request under a name.
| Name | Type | Req | Description |
|---|---|---|---|
| delivery_id | string | yes | The delivery to save. |
| name | string | yes | A name for the saved delivery. |
No output schema declared.
No examples provided.
sendmock_webhook_saved_delete ~42
Delete a saved delivery.
| Name | Type | Req | Description |
|---|---|---|---|
| saved_id | string | yes | The saved delivery's ID, from `GET /api/v1/webhooks/saved`. |
No output schema declared.
No examples provided.
sendmock_webhook_saved_list ~22
Bookmarked requests, kept through pruning and reset.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
sendmock_webhook_saved_save_as_template ~62
Turn a saved request into a custom template.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The name of the new custom template. |
| saved_id | string | yes | The saved delivery's ID, from `GET /api/v1/webhooks/saved`. |
No output schema declared.
No examples provided.
sendmock_webhook_saved_send ~89
Send a saved request to its endpoint or another one.
| Name | Type | Req | Description |
|---|---|---|---|
| endpoint_id | string | yes | The endpoint to send it to. |
| rerender | boolean | yes | Renders again with the endpoint's template and variables; false sends the saved request as it was. |
| saved_id | string | yes | The saved delivery's ID, from `GET /api/v1/webhooks/saved`. |
No output schema declared.
No examples provided.
sendmock_webhook_saved_update ~52
Rename a saved delivery.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The new name. |
| saved_id | string | yes | The saved delivery's ID, from `GET /api/v1/webhooks/saved`. |
No output schema declared.
No examples provided.
sendmock_webhook_send ~199
Send a webhook for a chosen message or the sample, by hand.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string|null | – | An edited body, sent as written (WH-05.6). |
| email_id | string|null | – | Send this email as the event. |
| endpoint_id | string | yes | The webhook endpoint's ID, from `GET /api/v1/webhooks/endpoints`. |
| http_request_id | string|null | – | A captured HTTP request, sent as an `http.captured` event (HC-01.7). |
| request | – | – | A hand-written request replacing the endpoint's, from the composer. |
| sms_id | string|null | – | Send this SMS as the event. |
| template_id | string|null | – | A template used for this send instead of the endpoint's request. |
| variables | object|null | – | Send-time values by variable name (no `vars.`), for this send only (WH-05.5). |
No output schema declared.
No examples provided.
sendmock_webhook_template_list ~19
Built-in and custom payload templates.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the SendMock MCP server?
SendMock runs locally as an npm package, launched with npx -y sendmock 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 · sendmock
claude mcp add shibbirweb-sendmock -- npx -y sendmock mcp
What is the SendMock MCP server?
SendMock is an MCP server listed in the public MCP registry as io.github.shibbirweb/sendmock. Test email, SMS, payments and webhooks locally: read messages, OTPs and webhook deliveries. This page covers its npm package (sendmock).
Is the SendMock MCP server safe to use?
SendMock scores 70 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 SendMock MCP server expose?
SendMock exposes 118 tools: sendmock_status, sendmock_stats, sendmock_email_list, sendmock_email_delete_all, sendmock_email_latest, and 113 more. Their descriptions and schemas cost roughly 10,321 tokens of context every time the server is loaded.
Is the SendMock MCP server still maintained?
SendMock 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 SendMock MCP server under?
SendMock declares the MIT OR Apache-2.0 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 SendMock MCP server?
VerifyMCP ran 15 checks on SendMock, covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about SendMock: Malware scan. 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.