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

Back to MCP Trust IndexM8ven
C
Emerging
74/100

deep-research-agent

自动化深度研究多智能体系统（基于 hello-agents）：TODO 驱动流水线 · FunctionCall 规划 · Reflection 报告双审 · 多领域数据源 · 三类型记忆 · MCP/A2A

→ Neko2048/deep-research-agent· listed on github_repo_search

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

Neko2048

Source: github_repo_search

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

GitHub

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
✅
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: LLM_API_KEY, S2_API_KEY, GITHUB_TOKEN
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.
configLLM_MODEL_ID模型名
🔐 secretLLM_API_KEYcustom provider 时的密钥与地址
configLLM_BASE_URLcustom provider 时的密钥与地址
configLOCAL_LLM
configLLM_PROVIDERollama（本地）/ lmstudio（本地）/ custom（OpenAI 兼容 API）
configLMSTUDIO_BASE_URL
configOLLAMA_BASE_URL
configMAX_WEB_RESEARCH_LOOPS检索轮次（透传给检索器）
configFETCH_FULL_PAGE是否把页面全文（截断后）纳入上下文
configSTRIP_THINKING_TOKENS是否剥离模型输出的 <think> 段落
configENABLE_REPORT_REFLECTION报告 Reflection 双审：报告生成后由「报告评审专家」critic，必要时自动 revise（ 可关）
configSEARCH_API数据源：web(duckduckgo/tavily/perplexity/searxng/advanced) · 论文(arxiv/semantic_scholar) · 代码(github)
configENABLE_NOTES任务笔记黑板开关与目录
configNOTES_WORKSPACE任务笔记黑板开关与目录
configENABLE_MEMORY跨会话记忆（三类型 + 巩固）：任务结果沉淀为 episodic、报告结论沉淀为 semantic、会话结束 consolidate 消化 working；新研究自动召回历史记忆注入规划与报告（ 可关）
configMEMORY_STORE_PATH记忆持久化 JSON 路径
configMAX_CONTEXT_TOKENSGSSC 上下文预算：检索上下文按 做 token 预算压缩（tiktoken 精确计数，离线回退字符估算），超限自动截断并标注
🔐 secretS2_API_KEY
🔐 secretGITHUB_TOKEN
// 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

3/3 tools missing one or more hints — research_search (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); research_memory_recall (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); deepresearchsearch (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint). 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

2/3 tools referenced in tests (67%)

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/neko2048/deep-research-agent)](https://m8ven.ai/mcp/neko2048/deep-research-agent)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: a2f0836720ad0ffbcc704cd6eeab48917a309e00
code hash: 9be7cb39ad7547c0ef82ce0e3d4c62eb2b507e170f227c3695477ef94bc7182c
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