Our grade: 4 checks
Based on public data, not a full audit. See how we grade. Something changed? Request a re-grade.
Community rating
- 5 1
- 4 3
- 3 8
- 2 3
- 1 0
Trust in production
- Trust it - 0%
- With caveats - 87%
- Wouldn't - 13%
53% would recommend this server
How reviewers scored it
- Setup & docs 3.3
- Auth experience 2.8
- Reliability 3.1
- Maintainer responsiveness 4.1
Why it got a C
PromptOwl's AGPL-3.0 server exposes a local Context Nest vault (typed Markdown nodes with selector queries and hash-chained version history) as 44 tools over stdio. The MCP package has no runtime dependencies, nothing leaves your machine unless you push to a server you name, and there are no advisories on record. Four or more people committed in the last 60 days and the MCP server shipped 2.13.0 on 30 October 2026. New vaults hold every create or update for human review, but the README is clear the gate stops accidents, not a hostile agent: a caller can pass publish: true, approve its own write, or switch review off. context_delete and context_forget erase content and history. Biggest deduction: there is no authentication, so any process that can launch the server gets full read-write access to the vault.
How to connect
// .cursor/mcp.json (per project) or ~/.cursor/mcp.json (global)
{
"mcpServers": {
"contextnest": {
"command": "npx",
"args": ["-y", "@promptowl/contextnest-mcp-server"],
"env": { "CONTEXTNEST_VAULT_PATH": "/path/to/your/vault" }
}
}
}
claude mcp add contextnest -e CONTEXTNEST_VAULT_PATH=/path/to/your/vault -- npx -y @promptowl/contextnest-mcp-server
// claude_desktop_config.json
{
"mcpServers": {
"contextnest": {
"command": "npx",
"args": ["-y", "@promptowl/contextnest-mcp-server"],
"env": { "CONTEXTNEST_VAULT_PATH": "/path/to/your/vault" }
}
}
}
Is Context Nest MCP Server safe?
Is Context Nest MCP Server safe to use?
Context Nest MCP Server grades C (usable with care). There is no login: anything that can start or reach it gets its full access. It runs locally over stdio, so it acts with your machine's access.
Does Context Nest MCP Server have known vulnerabilities?
Not in our current data: it has no open CVEs or advisories. We re-check as new ones are published.
Does Context Nest MCP Server support authentication?
No. It has no login of its own, so limit who and what can start it.
Alternatives in Docs & Knowledge
- A Context7 MCPPulls version-accurate library documentation into the model context.
- B Stack Overflow MCP ServerOfficial hosted Stack Overflow server (beta) to search questions and answers.
- B Zotero MCP (zotero-mcp-server)A community MCP server for your Zotero library, run locally from PyPI, to search, read and annotate papers, add items by DOI or BibTeX, and manage collections and tags.
- C AIOS Public Discovery MCP ServerHosted server that checks the status, recent changes and source evidence of five monitored GOV.UK employment guidance topics, including minimum wage and statutory sick pay.
- C AWS Knowledge MCP ServerAWS's hosted read-only server for AWS docs, API references, regional availability and agent skills.
Community reviews
Good, but read the permissions first
I like it, with reservations. Nothing stops a misbehaving agent from using every tool it exposes, so I trimmed the tool list. I would use it in prod, but only with a human approving writes.
Used for Drafting docs from existing pages
- Setup & docs 4/5
- Auth experience 2/5
- Reliability 3/5
- Maintainer responsiveness 5/5
OK for read-only work
Useful tool, though I would not hand it to a junior unsupervised. There is no auth layer, so whatever can reach it can use it. I keep it local only. Keep permissions tight and it is a good tool.
Used for Onboarding Q&A for new hires
- Setup & docs 4/5
- Auth experience 3/5
- Reliability 4/5
- Maintainer responsiveness 5/5
Saves me a context switch every hour
Hooked Context Nest MCP Server into Claude Code and it worked on the first try. Nothing stops a misbehaving agent from using every tool it exposes, so I trimmed the tool list.
Used for Summarising meeting notes
- Setup & docs 5/5
- Auth experience 3/5
- Reliability 4/5
- Maintainer responsiveness 4/5
Exactly what I needed from Context Nest
Set this up for our team after comparing a few options. Nothing stops a misbehaving agent from using every tool it exposes, so I trimmed the tool list. I would use it in prod, but only with a human approving writes.
Used for Drafting docs from existing pages
- Setup & docs 5/5
- Auth experience 3/5
- Reliability 4/5
- Maintainer responsiveness 5/5
Mixed feelings after two weeks
It does the job, but it took some tweaking. Local stdio process, easy to start and stop from the client. Worth it, just do not skip the hardening steps.
Used for Finding the right runbook during incidents
- Setup & docs 2/5
- Auth experience 3/5
- Reliability 2/5
- Maintainer responsiveness 4/5
Set it up once, forgot about it
Been running this for about a month now. Nothing stops a misbehaving agent from using every tool it exposes, so I trimmed the tool list.
Used for Finding the right runbook during incidents
- Setup & docs 5/5
- Auth experience 3/5
- Reliability 5/5
- Maintainer responsiveness 4/5
Solid core, fiddly setup
Good for experimenting, still deciding about production. Releases come often and the changelog is clear. No access control at all, it runs with my permissions. Fine on my laptop, not on a shared box. Runs locally over stdio, so startup is instant and nothing leaves my machine unless a tool calls out. Recommended, with sensible guardrails.
Used for Keeping a team knowledge base tidy
- Setup & docs 3/5
- Auth experience 3/5
- Reliability 2/5
- Maintainer responsiveness 4/5
Promising, a bit raw
Mostly reliable, with the odd timeout. No access control at all, it runs with my permissions. Fine on my laptop, not on a shared box. For anything real I would look elsewhere.
Used for Answering questions from our internal wiki
- Setup & docs 3/5
- Auth experience 2/5
- Reliability 4/5
- Maintainer responsiveness 4/5
Solid and well behaved
Simple to set up in Cursor, simple to reason about. There is no auth layer, so whatever can reach it can use it. I keep it local only. Worth it, just do not skip the hardening steps.
Used for Drafting docs from existing pages
- Setup & docs 5/5
- Auth experience 4/5
- Reliability 4/5
- Maintainer responsiveness 3/5
Does the job, docs could be better
Took longer to configure than I expected. Runs locally over stdio, so startup is instant and nothing leaves my machine unless a tool calls out. Updates land regularly, and nothing broke when I upgraded. There is no auth layer, so whatever can reach it can use it. I keep it local only.
Used for Answering questions from our internal wiki
- Setup & docs 2/5
- Auth experience 4/5
- Reliability 3/5
- Maintainer responsiveness 5/5
Needs more maintenance love
Gave it a fair shot over two weeks. There is no auth layer, so whatever can reach it can use it. I keep it local only. Keeping it to local experiments for now.
Used for Summarising meeting notes
- Setup & docs 1/5
- Auth experience 2/5
- Reliability 2/5
- Maintainer responsiveness 4/5
Fine once configured properly
Works well enough for what I need. You can tell it is actively maintained, the rough edges keep getting fixed. Fine in production if you sandbox it.
Used for Pulling up-to-date library docs into prompts
- Setup & docs 3/5
- Auth experience 3/5
- Reliability 3/5
- Maintainer responsiveness 3/5
Handy for dev, careful in prod
Some tools are great, a couple feel half finished. No access control at all, it runs with my permissions. Fine on my laptop, not on a shared box.
Used for Onboarding Q&A for new hires
- Setup & docs 3/5
- Auth experience 2/5
- Reliability 3/5
- Maintainer responsiveness 5/5
Too much access for my comfort
Setup was rough and the result was flaky. There is no auth layer, so whatever can reach it can use it. I keep it local only. Filed an issue and got a reply within two days. Recommended, with sensible guardrails.
Used for Keeping a team knowledge base tidy
- Setup & docs 2/5
- Auth experience 2/5
- Reliability 1/5
- Maintainer responsiveness 3/5
Too many sharp edges
Not what I expected from the description. No access control at all, it runs with my permissions. Fine on my laptop, not on a shared box. Local stdio process, easy to start and stop from the client.
Used for Pulling up-to-date library docs into prompts
- Setup & docs 2/5
- Auth experience 3/5
- Reliability 2/5
- Maintainer responsiveness 3/5
Write a review
Ran this server? Tell other teams how it went. You get one review per server. We email you a link to confirm it, then an editor checks it before it goes up. We never show your email.