PharosRAG (Laurent00TT/PharosRAG) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 7 tools. No publisher has claimed this listing.

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

PharosRAG

Pharos — local-first agentic RAG for your team's document library: multi-format ingest, hybrid retrieval, enterprise ACL, dual HTTP + MCP exits.

→ Laurent00TT/PharosRAG· listed on github_topic

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

Laurent00TT

Source: github_topic

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

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 2 credentials: PHAROS_API_KEY, DEEPSEEK_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.
🔐 secretPHAROS_API_KEYone key, identity bound at startup
configPHAROS_MAX_CONTEXT_TOKENS
configRAG_MAX_CONTEXT_TOKENS
configINFERENCE_WARMUP_RETRIES
configINFERENCE_WARMUP_BACKOFF
configINFERENCE_MAX_INFLIGHT
configINFERENCE_HOST
configINFERENCE_PORT
configPHAROS_EVAL_SRC
configRAG_EVAL_SRC
configPHAROS_EVAL_COLLECTION
configRAG_EVAL_COLLECTION
configPHAROS_EVAL_GEN_MODEL
configPHAROS_LLM_MODEL
configRAG_EVAL_GEN_MODEL
configPHAROS_EVAL_JUDGE_MODEL
configRAG_EVAL_JUDGE_MODEL
🔐 secretDEEPSEEK_API_KEY
configMINERU_REPO
configPHAROS_INFERENCE_URL
configINFERENCE_VLLM_URL
configINFERENCE_MODEL_PATH
configRERANK_PROXY_URL
configINFERENCE_DEFAULT_INSTRUCTION
configADAPTER_HOST
configADAPTER_PORT
configPHAROS_KB_ROOT
configPHAROS_KEYS_FILEeach request's X-API-Key yields its own identity (name + tenant + principals)
configPHAROS_
configRAG_
configPHAROS_INDEX_DIR
configPHAROS_CORPUS_DIR
configPHAROS_DENSE_MODEL_PATH
configPHAROS_RERANK_MODEL_PATH
configPHAROS_GPU_NAME
configPHAROS_HOST
configPHAROS_LOG_DIR
configPHAROS_LOG_QUERIES
configPHAROS_SMART_ASK
configPHAROS_LLM_BASE_URL
configPHAROS_LLM_API_KEY_ENV
configPHAROS_URL
configPHAROS_PORT
// 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 — _fn (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); retrieve (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_documents (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.

Secrets not logged

2 secret values sent to print

Redact or omit secret values from log output.

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/laurent00tt/pharosrag)](https://m8ven.ai/mcp/laurent00tt/pharosrag)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 162c7ca3e975440d0f345d0faca9194b4705d774
code hash: a994d1c5b9548db67cbd7bf09e7de5addc8c6b16dda3d1473c3be04e20b211ab
verified: 9/2/2026, 2:32:18 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