Is FreshContext MCP server safe?
Yes, with the usual care.
Safe to use. Minor gaps such as a missing repository or slower maintenance.
What to know before installing
- highWrite-action tools reachable without authentication
How FreshContext compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 81/100
- higher than 62% of 48,255 servers
- Tools that change things
- 5%
- typical: 0%. Fewer write tools means less an agent can break
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
What its tools let an agent do: 20 read · 1 change · 1 run or deploy
Release history: 3 versions in the registry since 2026-05-13, latest 2026-09-27, typically one every 131 days.
Public scan report
scanner v0.1.10 · 2026-10-31 · same rubric, same numbers if you re-run it
1 high
- Code scan82 source files scanned25/25
- Live reliabilityremote reachable in 1021ms20/20
- Tool poisoning22 tool descriptions checked15/15
- Auth qualityopen endpoint exposes 1 write-action tools with no auth3/15
- Maintenancelast push 31 days ago12/15
- Maintainer identityregistry namespace matches repository owner6/10
Findings (1)
- highWrite-action tools reachable without authentication
auth.open-write
Overall 81/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON