Case file No.228 · pypi · stdio

Jabama

io.github.sepehr071/jabama-mcp · v0.4.0

Unofficial read-only Jabama: villas and stays with exact prices, group tours, events and theater.

Package ↗GitHub ↗Website ↗

Security score

93/100

Strong

Normalized over 100 points of available evidence.

Score breakdown

Known advisories40/40

0 affecting current version, 0 historical

Maintenance20/20

last push 2 days ago

Source transparency15/15

public repo, license MIT

Metadata stability15/15

0 risky metadata change(s) without a version bump

Adoption3/10

538 weekly downloads

Known advisories

source: OSV.dev

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

Metadata change timeline

rug-pull detection

v0.3.0 → v0.4.0Oct 19, 2026

version changed version bump
```
"0.3.0" → "0.4.0"
```
packages.0.version changed package version bump
```
"0.3.0" → "0.4.0"
```

packages.0.environmentVariables.0.description changed env var description edit

"Optional HTTP proxy URL for every request. System proxy settings are ignored." → "Optional HTTP proxy URL for every request, or a comma-separated list: one is used until it gets blocked or fails to connect, then the next. System proxy settings are ignored."

First snapshot (v0.3.0)Oct 17, 2026

Tool lists: not published by the registry — unknown.

FAQ

auto-generated from the data above

Is Jabama safe?

MCPWatch gives Jabama a heuristic security score of 93/100 (strong), based on 100 points of available evidence. This is an automated heuristic, not an audit.

Does Jabama have known CVEs or vulnerabilities?

No advisories were found in OSV.dev for the pypi package jabama-mcp. That is not proof of safety.

When was Jabama last updated?

The latest registry version is 0.4.0, published Oct 18, 2026. The last push to sepehr071/jabama-mcp was on Oct 18, 2026. MCPWatch last checked it on Oct 20, 2026.

What license does Jabama use?

GitHub reports the license of sepehr071/jabama-mcp as MIT.

Related servers

same publisher / similar score