Case file No.003 · pypi · stdio · streamable-http

io.github.appwrite/mcp

io.github.appwrite/mcp · v1.0.21

Build and deploy backends: auth, Postgres/MySQL/vector databases, storage, functions, hosting, CDN

Package ↗GitHub ↗

Security score

100/100

Strong

Normalized over 100 points of available evidence.

Score breakdown

Known advisories40/40

0 affecting current version, 0 historical

Maintenance20/20

last push 0 days ago

Source transparency15/15

public repo, license MIT

Metadata stability15/15

0 risky metadata change(s) without a version bump

Adoption10/10

74372 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

v1.0.20 → v1.0.21Oct 20, 2026
- version changed version bump
```
"1.0.20" → "1.0.21"
```
- packages.0.version changed package version bump
```
"1.0.20" → "1.0.21"
```
v1.0.19 → v1.0.20Oct 19, 2026
- version changed version bump
```
"1.0.19" → "1.0.20"
```
- packages.0.version changed package version bump
```
"1.0.19" → "1.0.20"
```
First snapshot (v1.0.19)Oct 17, 2026

Tool lists: not published by the registry — unknown.

FAQ

auto-generated from the data above

Is io.github.appwrite/mcp safe?

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

Does io.github.appwrite/mcp have known CVEs or vulnerabilities?

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

When was io.github.appwrite/mcp last updated?

The latest registry version is 1.0.21, published Oct 20, 2026. The last push to appwrite/mcp was on Oct 20, 2026. MCPWatch last checked it on Oct 20, 2026.

What license does io.github.appwrite/mcp use?

GitHub reports the license of appwrite/mcp as MIT.

Related servers

same publisher / similar score