Novelty Research MCP (RobackaB/novelty-research-mcp) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it: we have no way to read this server ourselves. No publisher has claimed this listing.

Back to MCP Trust Indexm8ven
C
Limited view
69/100
25 days ago

Novelty Research MCP

Enables source-grounded prior-art and novelty research by searching patents, publications, and the web in one run, verifying evidence levels, and returning a structured report.

→ RobackaB/novelty-research-mcp· listed on glama

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

RobackaB

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 8 credentials: TAVILY_API_KEY, EXA_API_KEY, PUBMED_API_KEY, SEMANTIC_SCHOLAR_API_KEY, GOOGLE_CSE_API_KEY, GOOGLE_CUSTOM_SEARCH_API_KEY, CUSTOM_SEARCH_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.
🔐 secretTAVILY_API_KEY, EXA_API_KEY Web and patent search fallbacks
🔐 secretEXA_API_KEYTAVILY_API_KEY, Web and patent search fallbacks
configALPHA_CLI_PATH
🔐 secretPUBMED_API_KEY
🔐 secretSEMANTIC_SCHOLAR_API_KEYHigher rate limits for publication search
configRESEARCH_SESSION_DB
🔐 secretGOOGLE_CSE_API_KEY, GOOGLE_CSE_ID Primary web search backend
🔐 secretGOOGLE_CUSTOM_SEARCH_API_KEY
🔐 secretCUSTOM_SEARCH_API_KEY
🔐 secretGOOGLE_API_KEY
configGOOGLE_CSE_IDGOOGLE_CSE_API_KEY, Primary web search backend
configGOOGLE_CSE_CX
configGOOGLE_CUSTOM_SEARCH_ENGINE_ID
configGOOGLE_CUSTOM_SEARCH_CX
configCUSTOM_SEARCH_ENGINE_ID
configGOOGLE_CX
configMCP_HOST
configMCP_PORT
configMCP_PATH
configNO_COLOR
configMCP_PLAIN_UI
configTERM
configMCP_NO_UI
// 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

7/7 tools missing one or more hints — research_session_start (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); research_session_understand_query (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); patent_evidence_to_session (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +4 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 3/7 tool handlers wrap calls in try/catch (43%)

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

License file

No license file

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

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 5 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/robackab-novelty-research-mcp-1yrv7c)](https://m8ven.ai/mcp/robackab-novelty-research-mcp-1yrv7c)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 47bd3b29ecae327920ad65da9e3d988388fafb44
code hash: 7af68a8f5555a7803a3c3db6c9865f54432e2108771bf20b62815b3542671687
verified: 8/6/2026, 8:59:01 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