EspoCRM-MCP-Auth0 (megemini/EspoCRM-MCP-Auth0) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 48 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100

EspoCRM-MCP-Auth0

→ megemini/EspoCRM-MCP-Auth0· listed on modelscope

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

megemini

Source: ModelScope

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

ModelScopenot 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
✅
48 tools verified — handlers match their declared behaviour
22 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 5 credentials: FGA_CLIENT_SECRET, ESPOCRM_API_KEY, ESPOCRM_SECRET_KEY, OAUTH_CLIENT_SECRET, OAUTH_SECRET_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.
configFGA_API_URLFGA API endpoint (e.g., https://api.us1.fga.dev)
configFGA_STORE_IDYour FGA store ID
configFGA_CLIENT_IDYour FGA client ID
🔐 secretFGA_CLIENT_SECRETYour FGA client secret
configFGA_AUTHORIZATION_MODEL_IDThis creates the authorization model for EspoCRM entities and writes sample tuples. The script will output the authorization model ID - add this to your .env file as .
configFGA_API_ISSUER(Optional) Default is auth.fga.dev
configFGA_API_AUDIENCE(Optional) Default is derived from API URL
configESPOCRM_URL
🔐 secretESPOCRM_API_KEYSet to the generated API key
🔐 secretESPOCRM_SECRET_KEYSet both ESPOCRM_API_KEY and
configESPOCRM_AUTH_METHODSet =apikey
configAUTH0_DOMAIN
configAUTH0_AUDIENCE2. Set the API identifier as
configESPOCRM_TIMEOUT
configFGA_ENABLEDSet =true in your .env file
configOAUTH_ENABLED
configOAUTH_CLIENT_ID
🔐 secretOAUTH_CLIENT_SECRET
🔐 secretOAUTH_SECRET_KEY4. Generate :
configMCP_SERVER_URL
configCORS_ORIGINS
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// quality suggestions

Tool annotations

22/48 tools have annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

48/48 tools missing one or more hints — create_account (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); search_accounts (missing: destructiveHint, idempotentHint, openWorldHint); create_call (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +45 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/megemini/espocrm-mcp-auth0)](https://m8ven.ai/mcp/megemini/espocrm-mcp-auth0)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 058343de85ee1ccf798e2f36be98ea45c32f36c8
code hash: 544b85d927a5e7db83218580e96f0f502bef66b4589117b4e3299072de32b847
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