Back to MCP Trust Indexm8ven
C
Emerging
74/100
4 days ago

Claude Desktop Research MCP Server

Enables searching, retrieving, and reading academic papers from arXiv while analyzing citation networks via Semantic Scholar. It allows users to extract full-text content from PDFs and explore references or citations sorted by impact.

→ cholhwanjung/research-mcp· listed on glama

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

cholhwanjung

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Glama

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
🔐
You'll be asked for 3 credentials: RESEARCH_API_TOKEN, SS_API_KEY, GOOGLE_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configRESEARCH_SESSIONS_DB
configCORS_ORIGINS
configRESEARCH_MODEL./run-web.sh # .env 의 (미설정 시 Claude)
🔐 secretRESEARCH_API_TOKEN사용: 우상단 토큰칸에 값 입력(설정 시) → 채팅. 예: "BLIP-2 위키에 추가해줘" → 채팅에 tool 실행 흐름 표시 → Obsidian을 열어 노트·그래프 확인.
configCACHE_DIR
configOBSIDIAN_VAULT_PATH"": "/Users/you/Documents/research-wiki",
configPDF_PATH$OBSIDIAN_VAULT_PATH/pdfs PDF 원본 저장 위치
configGEMINI_MODEL
🔐 secretSS_API_KEY"": "<optional Semantic Scholar API key>"
🔐 secretGOOGLE_API_KEYVision 기반 figure / table 추출 — Gemini Vision으로 figure·table 영역을 crop한다. ( 필요)
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployNEXT_PUBLIC_API_URL
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

25/25 tools missing one or more hints — fn (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_tech_blog_posts (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); read_blog_post (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +22 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Tool test coverage

Only 2/25 tools referenced in tests (8%)

Write tests that reference each tool by name so every tool has at least one test.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 4 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/cholhwanjung-research-mcp-cgnp5m)](https://m8ven.ai/mcp/cholhwanjung-research-mcp-cgnp5m)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 27b499ad6d78960db2d8dfc771081a5c0a205a34
code hash: 1e2055ef4f0538eb7a27c060c4791b2c6d4f27dc3cd668903cb7d5f9dede6849
verified: 8/17/2026, 5:19:01 PM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client