M3Mgine (13auth/M3Mgine) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it: there is no public source to read and no endpoint we can reach, so there is nothing for us to inspect. No publisher has claimed this listing.

C
Limited view
71/100
2 months ago

M3Mgine

MCP server enabling AI agents to enforce corrected rules as durable pre-output checks, manage processed memory, and query a temporal knowledge graph.

Limited view. Automated analysis covers part of this stack. Findings reflect what we verified. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

Limited view: static analysis for Python is partially covered.

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

13auth

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

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 7 credentials: OAUTH_BRIDGE_SECRET, CCE_ENCRYPTION_KEY, RESEND_API_KEY, CCE_API_KEY, CCE_IYZICO_API_KEY, CCE_IYZICO_SECRET, CCE_WEBHOOK_SECRET
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.
configCCE_LOG
configCCE_HOST
configCCE_PORT
configCCE_MAX_BODY
configCCE_MAX_TEXT
configCCE_MAX_FACTS
configCCE_RATE_RPM
🔐 secretOAUTH_BRIDGE_SECRET
configCCE_EMBED_DIMwith RRF (recency + salience aware). HNSW index activates via at scale.
configCCE_INLINE_WORKER
configAPP_URL
configADMIN_EMAILScomma-separated admin emails
configCCE_DB
🔐 secretCCE_ENCRYPTION_KEY
configCCE_DETECTOR_MODEL
configCCE_LLM_MODEL
configCCE_MAX_KG_ENTITIES
configCCE_KG_RESOLVE_SCAN
configCCE_CANDIDATE_K
🔐 secretRESEND_API_KEY
configRESEND_FROM
configCCE_BASE
🔐 secretCCE_API_KEY
configCCE_MCP_HOST
configCCE_MCP_PORT
configCCE_IMPORT_MAX_EMB_DIM
configCCE_PAYMENT_PROVIDER
configCCE_CHECKOUT_RETURN_URL
configCCE_IYZICO_PLAN_
🔐 secretCCE_IYZICO_API_KEY
🔐 secretCCE_IYZICO_SECRET
configCCE_IYZICO_BASE
configCCE_JUDGE_VOTES
configCCE_JUDGE_RETRIES
configPOLICY_RULES
configCCE_IMPORT_MAX_RECORDS
configCCE_IMPORT_MAX_TOTAL
configCCE_STORE_BACKENDsqlite (default) or postgres
🔐 secretCCE_WEBHOOK_SECRETHMAC secret for billing webhooks
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
deployCCE_RLS_DSN
// 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 — enforce_check (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); remember (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); recall (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.

Tool handlers catch errors

Only 0/7 tool handlers wrap calls in try/catch (0%)

Wrap each tool handler body in try/catch and return a structured error response.

Tests exist

No test files found

Add tests that exercise each declared tool.

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 4 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/13auth-m3mgine-ndper2)](https://m8ven.ai/mcp/13auth-m3mgine-ndper2)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 0f5461d00f81782ef4535b5f3c418751916cd59f
code hash: 6c8e9ff20f66fe17b38aa50f6cd36ea93a4e82508f7fd0b63c6555b72edd77d8
verified: 6/20/2026, 9:13:12 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