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

Back to MCP Trust IndexM8ven
C
Emerging
74/100

Certus

Evidence-first workspace intelligence for long-lived document collections

→ sandeepbist/Certus· listed on github_repo_search

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

sandeepbist

Source: github_repo_search

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

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
✅
5 tools verified — handlers match their declared behaviour
3 read-only tools verified — handlers contain no write/delete/exec
✅
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 6 credentials: INTERNAL_SERVICE_TOKEN, OPENAI_API_KEY, NEO4J_PASSWORD, OBJECT_STORAGE_ACCESS_KEY, OBJECT_STORAGE_SECRET_KEY, WEBHOOK_ENCRYPTION_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.
🔐 secretINTERNAL_SERVICE_TOKEN
🔐 secretOPENAI_API_KEY
configOPENAI_EMBEDDING_MODEL
configWORKER_HEARTBEAT_STALE_SECONDS
configNEO4J_URI
configNEO4J_USER
🔐 secretNEO4J_PASSWORD
configEMBEDDING_GENERATION_EVAL_DATABASE_URL
configPGVECTOR_EVAL_DATABASE_URL
configOBJECT_STORAGE_BUCKET
🔐 secretOBJECT_STORAGE_ACCESS_KEY
🔐 secretOBJECT_STORAGE_SECRET_KEY
configOBJECT_STORAGE_SERVER_SIDE_ENCRYPTION
configOBJECT_STORAGE_KMS_KEY_ID
configOBJECT_STORAGE_BUCKET_KEY_ENABLED
configOBJECT_STORAGE_REGION
configOBJECT_STORAGE_ENDPOINT_URL
configEMBEDDING_DLQ_MAX_LENGTH
configEMBEDDING_PROCESSING_LEASE_SECONDS
configCERTUS_BUILD_REVISION
🔐 secretWEBHOOK_ENCRYPTION_KEY
configOUTBOX_PUBLISHED_RECOVERY_SECONDS
configMCP_TOOLS_URL
configMCP_SERVER_URL
configOPENAI_FAST_MODEL
configOPENAI_REASONING_MODEL
configOPENAI_GENERATION_TIMEOUT_SECONDS
configOPENAI_GENERATION_MAX_RETRIES
configAGENT_RUN_TOKEN_RESERVATION
configAGENT_RUN_RESERVATION_TTL_MINUTES
configORCHESTRATION_DB_POOL_MIN_SIZE
configORCHESTRATION_DB_POOL_MAX_SIZE
configORCHESTRATION_DB_POOL_ACQUIRE_TIMEOUT_SECONDS
configORCHESTRATION_DB_CONNECT_TIMEOUT_SECONDS
configORCHESTRATION_RETRIEVAL_PARALLEL_WORKERS
configORCHESTRATION_RETRIEVAL_STAGE_TIMEOUT_SECONDS
configORCHESTRATION_RETRIEVAL_STATEMENT_TIMEOUT_MS
configOPENAI_EMBEDDING_TIMEOUT_SECONDS
configOPENAI_EMBEDDING_MAX_RETRIES
configNEO4J_QUERY_TIMEOUT_SECONDS
configNEO4J_CONNECTION_TIMEOUT_SECONDS
configNEO4J_CONNECTION_ACQUIRE_TIMEOUT_SECONDS
configNEO4J_MAX_CONNECTION_POOL_SIZE
configRETRIEVAL_MIN_VECTOR_SIMILARITY
configMEMORY_MIN_SIMILARITY
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
deployDATABASE_URL
deployREDIS_URL
// quality suggestions

Secrets not logged

4 secret values sent to logger.error/logger.info

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 1 concrete improvement 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/sandeepbist/certus)](https://m8ven.ai/mcp/sandeepbist/certus)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: ab2879501ee3aeda7a022c610a1c396403c4be7f
code hash: 616a1ff85edfdbc890cb4ccb009ecbd9e59c0a186b5701c2fd888392618183c1
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