research-mcp (KB01111/research-mcp) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it: there is no public source to read and no endpoint we can reach, so there is nothing for us to inspect. No publisher has claimed this listing.

C
Limited view
71/100
22 days ago

research-mcp

MCP server that searches 9 sources, scrapes full content, reranks results, and synthesizes cited answers with free LLMs.

Limited view. Automated analysis covers part of this stack. Findings reflect what we verified. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

Limited view: static analysis for Python is partially covered.

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

KB01111

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 →

Install from

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.
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 10 credentials: FIRECRAWL_API_KEY, TAVILY_API_KEY, JINA_API_KEY, GROQ_API_KEY, GOOGLE_API_KEY, OPENROUTER_API_KEY, COHERE_API_KEY, TWITTERAPI_IO_KEY, SERPER_API_KEY, SERPAPI_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.
configLOG_LEVEL
configPLUGIN_PUBLIC_URL
configPLUGIN_HOST
configPLUGIN_PORT
configPLUGIN_RELOAD
configFIRECRAWL_API_URLFirecrawl (your fork) ✅ + optional FIRECRAWL_API_KEY Calls POST /v1/search
🔐 secretFIRECRAWL_API_KEYFirecrawl (your fork) ✅ FIRECRAWL_API_URL + optional Calls POST /v1/search
🔐 secretTAVILY_API_KEYTavily ✅ Primary fallback scraper, 1k/mo free
🔐 secretJINA_API_KEY
🔐 secretGROQ_API_KEY
🔐 secretGOOGLE_API_KEY
🔐 secretOPENROUTER_API_KEY
🔐 secretCOHERE_API_KEY
🔐 secretTWITTERAPI_IO_KEYX.com (Twitter) ❌ opt-in No free public X API
🔐 secretSERPER_API_KEYGoogle SERP ❌ opt-in or SERPAPI_API_KEY No free public SERP API
🔐 secretSERPAPI_API_KEYGoogle SERP ❌ opt-in SERPER_API_KEY or No free public SERP API
configSUMMARIZER_MODEL
configRERANKER_MODEL
configSCRAPER_METHOD
configMAX_RESULTS_PER_SOURCE
configMAX_CONCURRENT_SCRAPES
// 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

5/5 tools missing one or more hints — research (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); search_all (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); scrape_url (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +2 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.

Tool handlers catch errors

Only 0/5 tool handlers wrap calls in try/catch (0%)

Wrap each tool handler body in try/catch and return a structured error response.

Tests exist

No test files found

Add tests that exercise each declared tool.

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/kb01111-research-mcp-d57byu)](https://m8ven.ai/mcp/kb01111-research-mcp-d57byu)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: b69cb67ea8c4e8cb0433c497fa8e33bbf57807c3
code hash: dc2b97c16da5180c534630b9146fd4e1a165b123147f7c4b8bf406180c6bddb4
verified: 8/5/2026, 8:55:19 AM
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