Relatio CRM MCP Server (charbelkassab/relatio-crm) is an MCP server listed on the M8ven Trust Index. It scores 72 out of 100, grade C. It declares 18 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Caution
72/100

Relatio CRM MCP Server

Enables AI assistants to manage CRM prospects, activities, reminders, and mailbox via natural language commands through the Model Context Protocol.

→ charbelkassab/relatio-crm· listed on glama

Caution. Specific findings reduced this grade. They are listed on the page. 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

charbelkassab

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
⚠️
Known vulnerabilities in dependencies: 2 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
✅
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: API_KEY, IMAP_PASS, MCP_AUTH_SECRET, OPERATOR_PASSWORD, RESEND_API_KEY, SESSION_SECRET
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies2 high1 medium6 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

highnodemailer@6.9.16GHSA-p6gq-j5cr-w38f

Nodemailer: Message-level raw option bypasses disableFileAccess/disableUrlAccess, enabling arbitrary file read and full-response SSRF in the delivered message

highnodemailer@6.9.16GHSA-rcmh-qjqh-p98v

Nodemailer’s addressparser is vulnerable to DoS caused by recursive calls

mediumnodemailer@6.9.16GHSA-mm7p-fcc7-pg87

Nodemailer: Email to an unintended domain can occur due to Interpretation Conflict

lowmailparser@3.7.1GHSA-7gmj-h9xc-mcxc

mailparser vulnerable to Cross-site Scripting

lownodemailer@6.9.16GHSA-268h-hp4c-crq3

Nodemailer: CRLF injection in Nodemailer List-* header comments allows arbitrary message header injection

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// 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.
🔐 secretAPI_KEYOPERATOR_PASSWORD Dashboard login. Blank and no means open mode (localhost only).
configCOOKIE_SECURESESSION_SECRET, Cookie signing. Set COOKIE_SECURE=true on HTTPS.
configIMAP_HOST
🔐 secretIMAP_PASS
configIMAP_PORT
configIMAP_SECURE
configIMAP_USER
configMAIL_ADDRESSESComma-separated addresses this instance sends from and receives to.
configMAIL_FETCH_LIMIT
configMAIL_PROVIDERsmtp, resend, or blank (CRM-only).
configMAIL_SYNC
configMAIL_SYNC_INTERVAL_MS
🔐 secretMCP_AUTH_SECRETa-long-random-secret
configMCP_PUBLIC_URL
🔐 secretOPERATOR_PASSWORDthen edit .env, at minimum set DATABASE_URL and
configPGSSLrequire if your database needs SSL (most managed DBs do).
configPG_POOL_MAX
configPUBLIC_URLPORT, Listen port, and public origin for the MCP flow.
🔐 secretRESEND_API_KEYResend send plus inbound (for MAIL_PROVIDER=resend).
🔐 secretSESSION_SECRETany-long-random-string
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployDATABASE_URL
deployPORT
deploySMTP_HOST
deploySMTP_PASS
deploySMTP_PORT
deploySMTP_SECURE
deploySMTP_USER
// 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

18/18 tools missing one or more hints — crm_list_prospects (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); crm_get_prospect (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); crm_create_prospect (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +15 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 inputs are validated

15/18 tool handlers declare input schemas (83%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tests exist

No test files found

Add tests that exercise each declared tool.

Production dependencies are patched

0 critical, 2 high severity in production deps — nodemailer@6.9.16 (high), nodemailer@6.9.16 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

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 Verified](https://m8ven.ai/badge/mcp/charbelkassab/relatio-crm?variant=verified)](https://m8ven.ai/mcp/charbelkassab/relatio-crm)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: b56c47170aa1352efef53fae2f2aeeb726f0484d
code hash: 120a6e36dc65e7809c640fab183ed20fc85adf3c5c6ce39ea0a80d37563d2e83
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