Case file No.444 · npm · stdio · streamable-http

Sendinel

ai.sendinel/mcp-server · v1.0.58

AI-controlled email ops for campaigns, contacts, segments, analytics, and sending.

Package ↗GitHub ↗Website ↗

Security score

89/100

Strong

Normalized over 80 points of available evidence.

Unknown: Maintenance

Score breakdown

Known advisories40/40

0 affecting current version, 0 historical

Source transparency10/15

public repo, license unknown/none

Metadata stability15/15

0 risky metadata change(s) without a version bump

Adoption6/10

1961 weekly downloads

Maintenanceunknown

Excluded from the score — no data available.

Known advisories

source: OSV.dev

No advisories found in OSV for this package name. (Not proof of safety.)

Metadata change timeline

rug-pull detection

v1.0.43 → v1.0.58Oct 21, 2026
- version changed version bump
```
"1.0.43" → "1.0.58"
```
- packages.0.version changed package version bump
```
"1.0.43" → "1.0.58"
```
v1.0.42 → v1.0.43Oct 16, 2026
- version changed version bump
```
"1.0.42" → "1.0.43"
```
- packages.0.version changed package version bump
```
"1.0.42" → "1.0.43"
```
First snapshot (v1.0.42)Oct 16, 2026

Tool lists: not published by the registry — unknown.

FAQ

auto-generated from the data above

Is Sendinel safe?

MCPWatch gives Sendinel a heuristic security score of 89/100 (strong), based on 80 points of available evidence; unknown: Maintenance. This is an automated heuristic, not an audit.

Does Sendinel have known CVEs or vulnerabilities?

No advisories were found in OSV.dev for the npm package @sendinel/mcp-server. That is not proof of safety.

When was Sendinel last updated?

The latest registry version is 1.0.58, published Oct 20, 2026. The last repository push is unknown. MCPWatch last checked it on Oct 21, 2026.

What license does Sendinel use?

Unknown — GitHub metadata was not available on the last refresh.

Related servers

same publisher / similar score