Codebase RAG MCP Server (bluewings1211/codebase-RAG) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 17 tools. No publisher has claimed this listing.

C
Emerging
74/100

Codebase RAG MCP Server

Enables AI agents to chat with codebases by indexing local directories or GitHub repositories into a vector database for semantic search and code retrieval.

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

bluewings1211

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

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.
// 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.
configQDRANT_HOST
configQDRANT_PORT
configOLLAMA_HOST
configMEMORY_WARNING_THRESHOLD_MB
configMEMORY_CLEANUP_INTERVAL
configFORCE_CLEANUP_THRESHOLD_MB
configDB_RETRY_ATTEMPTS
configDB_RETRY_DELAY
configOLLAMA_DEFAULT_EMBEDDING_MODEL
configmax_files_in_response
configDB_HEALTH_CHECK_INTERVAL
configINDEXING_BATCH_SIZE
configQDRANT_BATCH_SIZE
configRERANKER_ENABLED
configFALLBACK_MAX_CHUNK_CHARS
configFALLBACK_TARGET_LINES
configFALLBACK_OVERLAP_LINES
configEMBEDDING_PROVIDER
configMLX_FALLBACK_TO_OLLAMA
configEMBEDDING_BATCH_SIZE
configMAX_BATCH_CHARS
configEMBEDDING_MAX_RETRIES
configEMBEDDING_RETRY_BASE_DELAY
configEMBEDDING_RETRY_MAX_DELAY
configEMBEDDING_BACKOFF_MULTIPLIER
configEMBEDDING_METRICS_ENABLED
configLOG_SUCCESSFUL_BATCHES
configLOG_BATCH_INTERVAL
configLOG_LEVEL
configINDEXING_CONCURRENCY
configMLX_SERVER_URL
configMLX_BATCH_SIZE
configMLX_TIMEOUT
configMLX_MODEL_SIZE
configMLX_MAX_BATCH_CHARS
configMAX_DIRECTORY_DEPTH
configFOLLOW_SYMLINKS
configMAX_FILE_SIZE_MB
configQDRANT_MAX_RETRIES
configQDRANT_RETRY_DELAY
configQDRANT_MAX_BATCH_MEMORY_MB
configRERANKER_PROVIDER
configRERANKER_MODEL
configRERANKER_MAX_LENGTH
configRERANKER_BATCH_SIZE
configRERANK_TOP_K
configLOG_FILE_ENABLED
configLOG_FILE_PATH
configLOG_FILE_MAX_SIZE
configLOG_FILE_BACKUP_COUNT
configMCP_MINIMAL_OUTPUT
configMCP_DEBUG_LEVEL
// 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

17/17 tools missing one or more hints — health_check_tool (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); index_directory (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); search (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +14 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 test coverage

Only 4/17 tools referenced in tests (24%)

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 3 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/bluewings1211/codebase-rag)](https://m8ven.ai/mcp/bluewings1211/codebase-rag)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 339ec59b8a51226769cf619991b5badbbff9b8ba
code hash: bbbce162bdbb762d76f39c7b0c86ade2ffdbc2ada326f8b30c9d8217637cc177
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