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

MCP Platform Framework

A framework for building MCP servers with built-in enterprise capabilities such as authentication, authorization, telemetry, audit logging, and data classification, allowing domain developers to focus on business logic while maintaining governance and compliance.

→ Edouard-Legoupil/mcp-platform-framework· listed on glama

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

Edouard-Legoupil

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

Glama

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.
🔐
You'll be asked for 3 credentials: AZURE_CLIENT_SECRET, CATALOG_API_KEY, KEY_VAULT_TOKEN
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.
configMCP_DOMAIN
configMCP_ENVIRONMENT
configFUNCTIONS_WORKER_RUNTIME
configAZURE_FUNCTIONS_ENVIRONMENT
configMCP_ENABLE_TELEMETRY
configMCP_ENABLE_AUDIT
configMCP_ENABLE_AUTH
configMCP_ENABLE_AUTHORIZATION
configMCP_ENABLE_CLASSIFICATION
configMCP_AUTO_DISCOVER_TOOLS
configAZURE_TENANT_ID
configAZURE_CLIENT_ID
🔐 secretAZURE_CLIENT_SECRET
configAZURE_CERTIFICATE_THUMBPRINT
configCATALOG_ENDPOINT
🔐 secretCATALOG_API_KEY
configCATALOG_TIMEOUT
configCATALOG_RETRY_COUNT
configCATALOG_RETRY_BACKOFF
configCATALOG_BATCH_SIZE
configMCP_VERSION
configAZURE_KEY_VAULT_URI
configKEY_VAULT_NAME
configKEY_VAULT_ENDPOINT
configKEY_VAULT_USE_MANAGED_IDENTITY
configKEY_VAULT_CACHE_ENABLED
configKEY_VAULT_CACHE_TTL_SECONDS
configKEY_VAULT_MAX_RETRIES
configKEY_VAULT_RETRY_DELAY_SECONDS
configKEY_VAULT_TIMEOUT_SECONDS
🔐 secretKEY_VAULT_TOKEN
configKEY_VAULT_TOKEN_FILE
// 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

5/5 tools missing one or more hints — get_donor_pipeline (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_donor_pipeline (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_donor_portfolio_health (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +2 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/5 tool handlers wrap calls in try/catch (0%)

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

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Tool test coverage

Only 0/5 tools referenced in tests (0%)

Write tests that reference each tool by name so every tool has at least one test.

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 Score](https://m8ven.ai/badge/mcp/edouard-legoupil-mcp-platform-framework-1a8qvm)](https://m8ven.ai/mcp/edouard-legoupil-mcp-platform-framework-1a8qvm)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: b90574ea13c4d8bc4afa0e79ec95a29e85f32b07
code hash: 78fc3dce4552d1efa977d3e928322b38af48c33f0f60aff3ed69400fa3639fba
verified: 8/13/2026, 7:55:57 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