research-hub (WenyuChiou/research-hub) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 96 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100

research-hub

AI-operable research workspace integrating Zotero, Obsidian, and NotebookLM. Search papers (arXiv/Semantic Scholar/PubMed/CrossRef), ingest into Zotero, sync per-paper notes to Obsidian, verify NotebookLM briefs. All three external tools optional.

→ WenyuChiou/research-hub· 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

WenyuChiou

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

Glamanot scored here

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
🚨
Secret credentials may flow to a network call
2 flows detected: ZOTERO_API_KEY. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 5 credentials: RESEARCH_HUB_API_TOKEN, ZOTERO_API_KEY, TAVILY_API_KEY, BRAVE_SEARCH_API_KEY, GOOGLE_CSE_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_HUB_MCP_INCLUDE_DEPRECATED
configRESEARCH_HUB_WORKFLOW_ROOT
configRESEARCH_HUB_NO_ZOTERO
🔐 secretRESEARCH_HUB_API_TOKEN
configRESEARCH_HUB_BATCH_LABEL
configRESEARCH_HUB_ALLOW_EXTERNAL_ROOT
configRESEARCH_HUB_CONFIG
configRESEARCH_HUB_ROOT
configRESEARCH_HUB_RAW
configRESEARCH_HUB_HUB
configRESEARCH_HUB_PROJECTS
configRESEARCH_HUB_LOGS
configRESEARCH_HUB_GRAPH
🔐 secretZOTERO_API_KEYSet ZOTERO_API_KEY and ZOTERO_LIBRARY_ID, then run research-hub doctor
configZOTERO_LIBRARY_IDSet ZOTERO_API_KEY and ZOTERO_LIBRARY_ID, then run research-hub doctor
configRESEARCH_HUB_ZOTERO_PARENT_COLLECTION
configRESEARCH_HUB_PERSONA
configRESEARCH_HUB_DISABLE_PDF_FALLBACK
configRESEARCH_HUB_EZPROXY_URL_TEMPLATE
configRESEARCH_HUB_EZPROXY_COOKIES_PATH
configRESEARCH_HUB_EZPROXY_HOST_SUFFIX
configUNPAYWALL_EMAIL
configRH_HOST
🔐 secretTAVILY_API_KEYWeb search backend (alternative to DDG)
🔐 secretBRAVE_SEARCH_API_KEY
🔐 secretGOOGLE_CSE_API_KEY
configGOOGLE_CSE_CX
configPYTEST_CURRENT_TEST
configRESEARCH_HUB_SKIP_ACL_HARDENING
// 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

96/96 tools missing one or more hints — web_search (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); cluster_rebind (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); propose_cluster_rebind (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +93 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.

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 2 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/wenyuchiou/research-hub)](https://m8ven.ai/mcp/wenyuchiou/research-hub)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: bb00775822bf856333cba8388631f16be3831ea4
code hash: f058738a527dc3f758f092098134f5ba449af9133de59384bdf8a1df28f48679
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