ai.imboard/dossier
NPM · @AI-DOSSIER/MCP-SERVER
MCP server for dossier automation standard - enables LLMs to discover, verify, and execute dossiers
Available components
Last scanned (51 minutes ago)
Scores higher than 95% of npm servers
Category Workflow Automation
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 38 of 129 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to imboard-ai/ai-dossier). View diagnostics → Pass
- Clear OSI-approved license (AGPL-3.0-only).Pass
- Actively maintained (last published 13 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability87
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 706 tokens (~50/item across 14 items; 10 tools + 4 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 0
- Stability: 0.97 → pass security
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 −1
- Stability: pass → 0.93 functional
- 28 Oct 26 0
- Stability: 0.97 → pass security
- 27 Oct 26 0
- Stability: pass → 0.97 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 23 Oct 26 0
- CVE-2026-97058 no longer affects this package ▲ security
- Known CVEs: partial → pass ▲ security
- 21 Oct 26 0
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@ai-dossier/mcp-server@1.0.4
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | imboard-ai/ai-dossier |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/imboard-ai/ai-dossier/.github/workflows/publish-packages.yml@refs/heads/main |
| Rekor log index | 1056487612 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:44824b4c2650c71ef8cda289730639de4fc239524c28b94df438e7f44c7ef86d0d2061751687359a990b3c09d99db9cd1657829034713c5b7c4944c9f |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 129 packages
| Packages resolved | 129 |
|---|---|
| Stale | 38 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
cancel_journey ~51
Cancel an active journey session. Returns a summary of what completed before cancellation.
| Name | Type | Req | Description |
|---|---|---|---|
| journey_id | string | yes | Journey session ID (from start_journey) |
| reason | string | – | Optional reason for cancellation |
No output schema declared.
No examples provided.
get_journey_status ~48
Get the current state of a journey session: completed steps, current step, remaining steps, and collected outputs.
| Name | Type | Req | Description |
|---|---|---|---|
| journey_id | string | yes | Journey session ID (from start_journey) |
No output schema declared.
No examples provided.
list_dossiers ~58
Discover available dossiers in a directory. Scans for *.ds.md files and returns metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | – | Directory to search (default: current working directory) |
| recursive | boolean | – | Search subdirectories recursively (default: true) |
No output schema declared.
No examples provided.
read_dossier ~44
Read and parse a dossier file. Returns metadata and content. Should be called AFTER verify_dossier passes.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Path to dossier file (.ds.md) |
No output schema declared.
No examples provided.
resolve_graph ~64
Resolve a dossier dependency graph into an execution plan. Reads relationships (preceded_by, followed_by, conflicts_with) and produces a DAG with ordered phases, parallel groups, and conflict detection.
| Name | Type | Req | Description |
|---|---|---|---|
| dossier | string | yes | Path to dossier file (.ds.md) or registry name |
No output schema declared.
No examples provided.
search_dossiers ~55
Search the dossier registry for available dossiers by keyword. Returns matching dossiers with metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Filter by category (devops, database, development, security, etc.) |
| query | string | yes | Search keywords |
No output schema declared.
No examples provided.
start_journey ~62
Start a journey session from a resolved and verified graph. Creates a session, returns the first step's dossier content with any injected context. Call step_complete after executing each step.
| Name | Type | Req | Description |
|---|---|---|---|
| graph_id | string | yes | ID of a previously resolved graph (from resolve_graph) |
No output schema declared.
No examples provided.
step_complete ~104
Mark the current journey step as complete or failed. Advances to the next step and returns its dossier content with injected context from previous outputs. Returns a summary when the last step completes or a step fails.
| Name | Type | Req | Description |
|---|---|---|---|
| journey_id | string | yes | Journey session ID (from start_journey) |
| outputs | object | – | Key-value outputs collected during this step (e.g. { cluster_arn: "arn:..." }) |
| status | string | yes | Whether this step succeeded or failed |
No output schema declared.
No examples provided.
verify_dossier ~48
Security verification - Verify integrity (checksum) and authenticity (signature) of a dossier. Returns pass/fail with stage details.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Path to dossier file (.ds.md) |
No output schema declared.
No examples provided.
verify_graph ~84
Batch security verification for a dossier dependency graph. Verifies all dossiers in a resolved graph and returns an aggregate security report with per-dossier breakdown and overall recommendation.
| Name | Type | Req | Description |
|---|---|---|---|
| dossier | string | – | Path to dossier file (.ds.md) or registry name. Resolves and verifies in one shot. |
| graph_id | string | – | ID of a previously resolved graph (from resolve_graph) |
No output schema declared.
No examples provided.
How do I install the ai.imboard/dossier MCP server?
ai.imboard/dossier runs locally as an npm package, launched with npx -y @ai-dossier/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @ai-dossier/mcp-server
claude mcp add ai-imboard-dossier -- npx -y @ai-dossier/mcp-server
What is the ai.imboard/dossier MCP server?
ai.imboard/dossier is an MCP server listed in the public MCP registry as ai.imboard/dossier. MCP server for dossier automation standard - enables LLMs to discover, verify, and execute dossiers. This page covers its npm package (@ai-dossier/mcp-server).
Is the ai.imboard/dossier MCP server safe to use?
ai.imboard/dossier scores 92 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the ai.imboard/dossier MCP server expose?
ai.imboard/dossier exposes 10 tools: verify_dossier, read_dossier, list_dossiers, search_dossiers, resolve_graph, and 5 more. Their descriptions and schemas cost roughly 618 tokens of context every time the server is loaded.
Is the ai.imboard/dossier MCP server still maintained?
ai.imboard/dossier is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the ai.imboard/dossier MCP server under?
ai.imboard/dossier declares the AGPL-3.0-only licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.