Directive Run MCP Server

@directive-run/mcp npm v0.6.28

Published by @directive-run — 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 that exposes Directive to AI clients — knowledge files, code examples, and Claude Code skill bundles today, with room to grow into runtime introspection and tooling. stdio for local clients (Claude Desktop, Cursor, MCP Inspec

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 22

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

  • get_exampleingests untrusted input
  • get_knowledgeingests untrusted input
  • get_migration_patterningests untrusted input
  • get_package_infoingests untrusted input
  • get_review_ruleingests untrusted input
  • get_skillingests untrusted input
  • fix_codeno sensitive capability
  • generate_moduleno sensitive capability
  • get_composable_packagesno sensitive capability
  • get_server_infono sensitive capability
Show 12 more tools ↓
  • list_examplesno sensitive capability
  • list_knowledgeno sensitive capability
  • list_migration_sourcesno sensitive capability
  • list_module_sectionsno sensitive capability
  • list_packagesno sensitive capability
  • list_review_rulesno sensitive capability
  • list_skillsno sensitive capability
  • playground_linkno sensitive capability
  • review_sourceno sensitive capability
  • run_in_sandboxno sensitive capability
  • search_examplesno sensitive capability
  • search_knowledgeno sensitive capability

What this scan could not see

Versions 10

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
v0.6.28 latest A 96/100 0 1.13.0 2026-09-07
v0.6.26 A 96/100 0 1.13.0 2026-09-01
v0.6.23 A 96/100 0 1.12.1 2026-08-21
v0.6.22 A 96/100 0 1.12.1 2026-08-20
v0.6.21 A 96/100 0 1.12.1 2026-08-19
Show 5 more versions ↓
v0.6.19 A 96/100 0 1.12.1 2026-08-18
v0.6.18 A 96/100 0 1.12.1 2026-08-16
v0.6.13 A 96/100 0 1.12.1 2026-08-15
v0.6.9 A 96/100 0 1.12.1 2026-08-14
v0.6.8 A 96/100 0 1.12.1 2026-08-13

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/directive-run-mcp/badge.svg)](https://mcptrustchecker.com/registry/directive-run-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/directive-run-mcp"><img src="https://mcptrustchecker.com/registry/directive-run-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/directive-run-mcp/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 @directive-run/mcp --online

Use the free API → How scoring works

More in Learning & Documentation