Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"dossier": {
"args": [
"-y",
"@ai-dossier/mcp-server"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Stop writing brittle scripts. Start writing instructions that AI executes intelligently.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y '@ai-dossier/cli' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked @ai-dossier/cli against OSV.dev.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in productivity
Dynamic problem-solving through sequential thought chains
Persistent memory using a knowledge graph
mini cli search engine for your docs, knowledge bases, meeting notes, whatever. Tracking current sota approaches while being all local
Official Notion MCP Server
MCP Security Weekly
Get CVE alerts and security updates for Dossier MCP Server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Skills are easy to write. Dossiers make them trustworthy, versioned, and portable across every LLM tool.
Quick Concept A dossier is a skill — a reusable instruction set an AI executes — with trust, versioning, and cross-tool portability built in. Think npm or Docker Hub, but for AI skills: signed, versioned, shareable.
┌──────────────────────────────────────────────────────────────────────┐
│ │
│ Write instructions Verify integrity AI executes │
│ in Markdown (.ds.md) with checksums & the workflow │
│ signatures intelligently │
│ │
│ ┌──────────┐ sign ┌──────────┐ run ┌──────────┐ │
│ │ Author │ ─────────> │ Verify │ ────────> │ AI Agent │ │
│ └──────────┘ └──────────┘ └──────────┘ │
│ │ │ │ │
│ .ds.md file checksum + validated │
│ with JSON signature results with │
│ frontmatter verification evidence │
│ │
└──────────────────────────────────────────────────────────────────────┘
New here? → 5-min Quick Start | Using Claude Code? → MCP in 60 Seconds | Want to try now? → Get started in 30 seconds
flowchart LR
A["📝 Create\n.ds.md file"] --> B["🔏 Sign\nchecksum +\nsignature"]
B --> C["✅ Verify\nintegrity &\nauthenticity"]
C --> D["🤖 Execute\nAI runs the\nworkflow"]
D --> E["📋 Validate\nsuccess criteria\n& evidence"]
style A fill:#e3f2fd,stroke:#1565c0,color:#0d47a1
style B fill:#fce4ec,stroke:#c62828,color:#b71c1c
style C fill:#fff3e0,stroke:#ef6c00,color:#e65100
style D fill:#e8f5e9,stroke:#2e7d32,color:#1b5e20
style E fill:#f3e5f5,stroke:#6a1b9a,color:#4a148c
What: Skills (.ds.md files) any AI agent can run — signed, versioned, portable across tools
Why: A plain skill lives in one tool and anyone can tamper with it; a dossier is that same skill made verifiable, version-pinned, and shareable
Safety: Built-in checksums, cryptographic signatures, and CLI verification tools
Works with: Claude, ChatGPT, Cursor, any LLM — no vendor lock-in
Status: Protocol v1.0 (stable spec) | CLI v0.8.5 | 15+ example skills | Active development
File conventions: Dossiers use
.ds.md(immutable instructions) and.dsw.md(mutable working files). Frontmatter uses `---dossier