sageleaf (sage-eco/sageleaf) is an MCP server listed on the M8ven Trust Index. It scores 44 out of 100, grade D. It declares 9 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
D
Caution
44/100

sageleaf

Circular economy information app

→ sage-eco/sageleaf· listed on github_code

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

sage-eco

Source: github_code

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
🚨
Known vulnerabilities in dependencies: 1 critical, 8 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 8 credentials: DO_SPACES_KEY, DO_SPACES_SECRET, GOOGLE_CLIENT_SECRET, JWT_SECRET, MISTRAL_API_KEY, POSTHOG_API_KEY, TYPESENSE_API_KEY, WINDMILL_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// tools this server exposes9 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

begin_change
create_source
edit_change
graphql_introspection
graphql_query
propose_edit
propose_refs
search_catalog
whoami

Return the identity of the currently authenticated user making this MCP request.

// known CVEs in dependencies1 critical8 high1 medium6 low

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

critical@mikro-orm/core@6.6.6GHSA-gwhv-j974-6fxm

MikroORM is vulnerable to SQL Injection via specially crafted object

high@mikro-orm/core@6.6.6GHSA-qpfv-44f3-qqx6

MikroORM has Prototype Pollution in Utils.merge

high@opentelemetry/auto-instrumentations-node@0.72.0GHSA-q7rr-3cgh-j5r3

Prometheus exporter process crash via malformed HTTP request

highkysely@0.28.14GHSA-pv5w-4p9q-p3v2

Kysely: JSON-path traversal injection via unsanitized path-leg metacharacters in `JSONPathBuilder.key()` / `.at()`

highlodash@4.17.23GHSA-r5fr-rjxr-66jc

lodash vulnerable to Code Injection via `_.template` imports key names

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.
configAPP_SHA
configAPP_VERSION
configBASE_DOMAIN
configBETTER_AUTH_URL
🔐 secretDO_SPACES_KEY
🔐 secretDO_SPACES_SECRET
configDRAGONFLY_URL
configGOOGLE_CLIENT_ID
🔐 secretGOOGLE_CLIENT_SECRET
configIS_DEV
🔐 secretJWT_SECRET
🔐 secretMISTRAL_API_KEY
🔐 secretPOSTHOG_API_KEY
configRATE_LIMIT_ANON_CAPACITY
configRATE_LIMIT_ANON_LEAK_RATE
configRATE_LIMIT_AUTH_CAPACITY
configRATE_LIMIT_AUTH_LEAK_RATE
configRATE_LIMIT_ENABLED
configTEST_DATABASE_URL
configTRUSTED_PROXIES
🔐 secretTYPESENSE_API_KEY
configTYPESENSE_HOST
configWINDMILL_BASE_URL
🔐 secretWINDMILL_TOKEN
configWINDMILL_WORKSPACE
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployDATABASE_URL
deployPORT
// 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

9/9 tools missing one or more hints — begin_change (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); create_source (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); edit_change (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +6 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.

License file

No license file

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

Production dependencies are patched

1 critical, 7 high severity in production deps — @mikro-orm/core@6.6.6 (critical), @mikro-orm/core@6.6.6 (high)

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

Dev dependencies

1 critical/high in dev-only deps (does not ship to users)

Upgrade dev dependencies when convenient.

Dependency freshness

5/68 production deps abandoned (no release in 2+ years): @mikro-orm/sql-highlighter@2022-04-06 (4.4y), class-transformer@2022-12-09 (3.7y), dotenv-flow@2023-12-26 (2.7y)

Domain consistency

npm scope @sageleaf doesn't match GitHub owner sage-eco

Use the same org name across GitHub, npm, and your homepage so users can verify the publisher.

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 6 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/sage-eco/sageleaf?variant=verified)](https://m8ven.ai/mcp/sage-eco/sageleaf)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: fffbfc21c5c837cbf877cb563d1425a0e4ce1365
code hash: 3de97a83e61d4f10e9aa940009db85a87ae34c024ccc38a07cf461617cf22ec1
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