Directus (archawat) MCP Server

@archawat/mcp-directus npm v2.0.3

Published by @archawat — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

Model Context Protocol server for Directus projects.

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 96/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 4 = 96. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 43

Each tool and what it can reach — statically extracted from the published source.

  • directus_read_commentsingests untrusted input
  • directus_read_filesreads sensitive data
  • directus_read_flowsingests untrusted input
  • directus_read_itemsingests untrusted input
  • directus_read_presetsingests untrusted input
  • directus_count_itemsno sensitive capability
  • directus_create_collectionno sensitive capability
  • directus_create_fieldno sensitive capability
  • directus_create_flowno sensitive capability
  • directus_create_itemno sensitive capability
Show 33 more tools ↓
  • directus_create_operationno sensitive capability
  • directus_create_relationno sensitive capability
  • directus_delete_flowno sensitive capability
  • directus_delete_itemno sensitive capability
  • directus_delete_operationno sensitive capability
  • directus_delete_relationno sensitive capability
  • directus_get_item_summaryno sensitive capability
  • directus_get_promptsno sensitive capability
  • directus_helpno sensitive capability
  • directus_import_fileno sensitive capability
  • directus_list_collectionsno sensitive capability
  • directus_markdownno sensitive capability
  • directus_read_collection_schemano sensitive capability
  • directus_read_collectionsno sensitive capability
  • directus_read_fieldno sensitive capability
  • directus_read_fieldsno sensitive capability
  • directus_read_flowno sensitive capability
  • directus_read_foldersno sensitive capability
  • directus_read_operationno sensitive capability
  • directus_read_operationsno sensitive capability
  • directus_read_relationno sensitive capability
  • directus_read_relationsno sensitive capability
  • directus_read_usersno sensitive capability
  • directus_system_promptno sensitive capability
  • directus_trigger_flowno sensitive capability
  • directus_update_fieldno sensitive capability
  • directus_update_filesno sensitive capability
  • directus_update_flowno sensitive capability
  • directus_update_itemno sensitive capability
  • directus_update_operationno sensitive capability
  • directus_update_relationno sensitive capability
  • directus_upsert_commentno sensitive capability
  • directus_users_meno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v2.0.3 latest A 96/100 0 1.13.0 2026-09-06

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 96/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/archawat-mcp-directus/badge.svg)](https://mcptrustchecker.com/registry/archawat-mcp-directus)
HTML
<a href="https://mcptrustchecker.com/registry/archawat-mcp-directus"><img src="https://mcptrustchecker.com/registry/archawat-mcp-directus/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/archawat-mcp-directus/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan @archawat/mcp-directus --online

Use the free API → How scoring works

Other implementations of Directus 4

Independent packages implementing the same tool, scanned with the same engine. Compare all 5 side by side →

More in Content Management