Is Corpus MCP server safe?
Yes, with the usual care.
Safe to use. Minor gaps such as a missing repository or slower maintenance.
No critical or high findings in the latest scan.
How Corpus compares
Against every graded Web search MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 83/100
- higher than 70% of 3,470 Web search servers
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- Uptime
- 100%
- of our recent checks; the typical remote Web search server answers 100%
What its tools let an agent do: 9 read
Public scan report
scanner v0.1.9 · 2026-09-24 · same rubric, same numbers if you re-run it
1 medium
- Code scan2 source files scanned20/25
- Live reliabilityremote reachable in 1710ms20/20
- Tool poisoning9 tool descriptions checked15/15
- Auth qualityopen endpoint, read-only tools10/15
- Maintenancelast push 33 days ago12/15
- Maintainer identitynamespace and repository owner differ; GitHub account older than a year6/10
Findings (1)
- mediumeval / new Function used
exec.evaldist/stdio.cjs: …ode, sch); const makeValidate = new Function(`${names_1.default.self}`, `${names_1.de…
Overall 83/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON
Other servers that do what Corpus does
- ArxivSearch arXiv papers, download full text, semantic search, citation graphs, and alerts via MCP.not reviewedWidely usedA
- SocraticodeMCP server for enterprise local codebase indexing, semantic search, and code dependency graphs.not reviewedEstablishedB
- PubmedSearch PubMed/Europe PMC, fetch articles and full text (PMC/EPMC/Unpaywall), citations, MeSH terms.not reviewedEstablishedA