scholar-memory (byBasiliosP/RLM-Agent) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 9 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100
10 days ago

scholar-memory

Enables scientific literature research through multi-agent search, analysis, and semantic memory, exposing 9 MCP tools for querying, storing, and retrieving research findings.

→ byBasiliosP/RLM-Agent· 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

byBasiliosP

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
✅
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 7 credentials: TAVILY_API_KEY, BRAVE_API_KEY, SERPER_API_KEY, SCHOLAR_EMBEDDING_API_KEY, OPENAI_API_KEY, ANTHROPIC_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.
🔐 secretTAVILY_API_KEY
🔐 secretBRAVE_API_KEY
🔐 secretSERPER_API_KEY
configSCHOLAR_MEMORY_DIRData directory
configSCHOLAR_MEMORY_DBSQLite DB path
configSCHOLAR_STRONG_BACKENDBackend for analysis agents
configSCHOLAR_CHEAP_BACKENDBackend for Scout
configSCHOLAR_EMBEDDING_BACKENDopenai or lmstudio
configSCHOLAR_STRONG_MODELStrong model name
configSCHOLAR_CHEAP_MODELCheap model name
configSCHOLAR_LMSTUDIO_URLLM Studio endpoint (when backend=lmstudio)
configSCHOLAR_EMBEDDING_MODELEmbedding model
configSCHOLAR_EMBEDDING_BASE_URL
🔐 secretSCHOLAR_EMBEDDING_API_KEY
configSCHOLAR_PROJECT_ROOT
🔐 secretOPENAI_API_KEY(for embeddings — required by default) plus ANTHROPIC_API_KEY (for the strong model in normal/deep research), or
🔐 secretANTHROPIC_API_KEYOPENAI_API_KEY (for embeddings — required by default) plus (for the strong model in normal/deep research), or
🔐 secretGITHUB_TOKENOptional: for GitHub code search (otherwise you'll get 401s — non-fatal).
// 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

9/9 tools missing one or more hints — memory_lookup (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); memory_get (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); memory_research (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +6 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/bybasiliosp/rlm-agent)](https://m8ven.ai/mcp/bybasiliosp/rlm-agent)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 1dff72ed3201b92bb3e05ca16ccbc1d8978ae14a
code hash: f3a117125d39eaa52b82242dac0fb0a29f1fcc6f1b88b9791b1b32849791f0f2
verified: 9/3/2026, 4:46:06 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