Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/neryams/workspace-docs-mcpInstalling this writes the configuration, not the program: `journal-mcp` has to be on your PATH already, or the server will not start.
Wrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/neryams/workspace-docs-mcp/journal)<a href="https://agentmods.dev/mcp/neryams/workspace-docs-mcp/journal"><img src="https://agentmods.dev/badge/mcp/neryams/workspace-docs-mcp/journal/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/neryams/workspace-docs-mcp/journal"><img src="https://agentmods.dev/badge/mcp/neryams/workspace-docs-mcp/journal.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
journal scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"journal": {
"command": "journal-mcp",
"cwd": "${workspaceFolder}",
"env": {
"JOURNAL_RAG_WORKSPACE": "${workspaceFolder}"
}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 9 lines scan A 53f00da7f341
journal is an MCP server published in the GitHub repository neryams/workspace-docs-mcp (0 stars, last pushed 8d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-07.
Other mcp servers, from other repositories
mcp-obsidian-cli
Save chat notes from Claude Desktop to your vault — MCP on Obsidian CLI. Keep what matters. Runs locally from the mcp-obsidian-cli npm package. Needs 3 environment variables to run.
compendio-mcp
Indexes your project's markdown docs and serves them to any agent via local hybrid search. Runs locally from the compendio-mcp npm package.
lexomni-mcp
MCP server for local knowledge management with MD and PDF indexing. Runs locally from the lexomni-mcp npm package.
kb-mcp
Your private knowledge base: upload documents (.md, .txt, .docx, PDF, images), the platform indexes. Remote server at api.mcp.ai.
writespace-mcp
Persistent docs and memory for AI agents — read, write, organize & search a shared workspace. Remote server at app.writespace.io.
rootr-cli
Connect your team's living knowledge base — docs, data, issues, CRM — to Claude and ChatGPT. Remote server at rootr.io.