updated 2026-11-10 04:07 UTC

Appwrite MCP

Repository Website

Appwrite’s MCP server. Operating your backend has never been easier.

MCP Servers Python Listed MIT

Is Appwrite MCP safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 5.2 / 10
Provenance None
Signed commits 48%
Last push today
Compare Appwrite MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Appwrite MCP scores 63.8/100 (Grade C), ranked #576 of 1374 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 5.2/10; 48% of recent commits are signed; last pushed 2026-11-10. Every point is earned from checkable signals — never paid placement. How scoring works →

How Appwrite MCP could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Appwrite MCP and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/appwrite/mcp, MIT, last pushed 2026-11-10. 48% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 5.2/10 (scanned Nov 10, 2026). The checks that decide who can get a change released:

    • Code Review5
    • Branch Protection0
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies8
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 5
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 10
    Packaging 10
    Pinned-Dependencies 8
    SAST 0
    Security-Policy 10
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 0

  3. Published packages Not linked

    Without a build attestation, nothing proves the published files were built from this repository.

Changes to this chain

  • 2026-08-27 OSSF Scorecard: 4.7/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Appwrite MCP’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Appwrite MCP compares in MCP Servers

  1. #326 MCP Notion Server 63.9 +0.1
  2. #327 Red Hat Lightspeed MCP 63.8 ±0
  3. #328 Appwrite MCP 63.8 this agent
  4. #329 Paparats – Local Semantic Code Search MCP 63.5 −0.3
  5. #330 Apollo MCP Server 63.4 −0.4

Bars show each HVTrust score; the tick marks Appwrite MCP’s 63.8.

Where the 63.8 comes from

HVTrust dimensions vs the MCP Servers average

63.8 / 100 · 100.0% confidence

Appwrite MCP MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
8.9 / 25
1.9 below avg 10.8
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.9 below avg 13.7
Transparency50% declared license · 50% OSSF Scorecard
12.9 / 17
0.6 above avg 12.3
Maintenance60% last-push freshness · 40% commit activity
19.1 / 20
6.9 above avg 12.2
AdoptionLog-scaled stars · package downloads
10.9 / 20
3.3 above avg 7.6

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-11-08
Rank Moved
Rank dropped 12 spots (#565 → #577)
2026-11-06
Rank Moved
Rank dropped 15 spots (#555 → #570)
2026-11-04
Rank Moved
Rank rose 10 spots (#569 → #559)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.2/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Compare with another agent
View MCP Servers Report missing data
64.6
Activity sub-score · out of 100
#328
In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-11-10 04:07 UTC · Repo last pushed today

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
72
Forks
21
Last Push
2026-11-10
today
Commits (4 wk)
59
Downloads (7d)
64,216
pypi
HN mentions (30d)
—
Open Issues
1
Rank Change
=
was #576

Analysis

Activity Inputs

64.6 / 100
StarsRepository reach
11.2 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
22.2 / 25
CommunityFork signal
6.2 / 20

Common questions about Appwrite MCP

Appwrite MCP has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does Appwrite MCP publish package provenance?
No published build provenance is currently detected for Appwrite MCP. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Appwrite MCP have an OpenSSF Scorecard?
Appwrite MCP has an OpenSSF Scorecard score of 5.2/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Appwrite MCP actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Appwrite MCP use?
Appwrite MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Appwrite MCP's commits signed?
48% of the last 100 commits to Appwrite MCP are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
high confidence
Implemented
Appwrite MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
2 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
medium confidence
1 tags
Broad capability areas detected.
  • database
Detailed evidence is not shown in the public view.
Package Provenance Drift
low confidence
Unknown
Package source metadata is missing or inconclusive
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to Appwrite MCP's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-10-13
Provider Added
Runtime surface grew — new detected provider dependency: Redis
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: OpenAI
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented

Maintain Appwrite MCP?

For maintainers

HVTrust scores Appwrite MCP from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 26HVTrust 2Grade 2Surface 2Scorecard 1Delisted 1Listed 1MCP 1
2026-11-08
Rank Moved
Rank dropped 12 spots (#565 → #577)
2026-11-06
Rank Moved
Rank dropped 15 spots (#555 → #570)
2026-11-04
Rank Moved
Rank rose 10 spots (#569 → #559)
2026-11-03
Rank Moved
Rank rose 17 spots (#586 → #569)
2026-10-31
Rank Moved
Rank dropped 10 spots (#567 → #577)
2026-10-30
Rank Moved
Rank rose 26 spots (#593 → #567)
2026-10-29
Rank Moved
Rank rose 17 spots (#610 → #593)
2026-10-15
Rank Moved
Rank rose 15 spots (#616 → #601)
2026-10-13
Provider Added
Runtime surface grew — new detected provider dependency: Redis
2026-10-13
Rank Moved
Rank dropped 30 spots (#594 → #624)
2026-10-11
Rank Moved
Rank dropped 25 spots (#573 → #598)
2026-10-06
Rank Moved
Rank rose 15 spots (#590 → #575)
2026-10-04
Rank Moved
Rank dropped 10 spots (#577 → #587)
2026-10-03
Rank Moved
Rank dropped 14 spots (#563 → #577)
2026-09-28
Rank Moved
Rank dropped 11 spots (#546 → #557)
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: OpenAI
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Grade Changed
Trust grade D → C
2026-09-23
Rank Moved
Rank rose 249 spots (#786 → #537)
2026-09-23
HVTrust Changed
HVTrust up 33.9pts (29.1 → 63.0)
2026-09-22
Newly Listed
First tracked at rank #786
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-11
Rank Moved
Rank dropped 19 spots (#466 → #485)
2026-09-07
Rank Moved
Rank dropped 29 spots (#421 → #450)
2026-09-06
Rank Moved
Rank dropped 12 spots (#409 → #421)
2026-09-05
Rank Moved
Rank dropped 66 spots (#343 → #409)
2026-09-04
Rank Moved
Rank dropped 12 spots (#331 → #343)
2026-09-03
Rank Moved
Rank dropped 21 spots (#310 → #331)
2026-08-31
Rank Moved
Rank dropped 31 spots (#269 → #300)
2026-08-29
Rank Moved
Rank dropped 12 spots (#262 → #274)
2026-08-27
Scorecard Added
OSSF Scorecard: 4.7/10
2026-08-27
Grade Changed
Trust grade D → C
2026-08-27
Rank Moved
Rank rose 520 spots (#783 → #263)
2026-08-27
HVTrust Changed
HVTrust up 27.5pts (37.3 → 64.8)
2026-08-26
Rank Moved
Rank dropped 103 spots (#680 → #783)
2026-08-16
Rank Moved
Rank dropped 11 spots (#665 → #676)
GitHub → Website → PyPI: mcp-server-appwrite

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 63.8 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/appwrite-mcp.svg)](https://hvtracker.net/agents/appwrite-mcp)
HTML:
<a href="https://hvtracker.net/agents/appwrite-mcp"><img src="https://hvtracker.net/badge/appwrite-mcp.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON