geostudio (tlenenao/geostudio) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 22 tools. No publisher has claimed this listing.

C
Emerging
74/100
10 days ago

geostudio

GeoStudio — plateforme d'applications géospatiales open-source (no-code builder, cartes, OGC, MCP)

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

tlenenao

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 →

Install from

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
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 4 credentials: S3_ACCESS_KEY, S3_SECRET_KEY, CORE_EXPORT_TOKEN_SECRET, CORE_LLM_API_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.
configCORE_OIDC_ISSUERcœur — /CORE_OIDC_AUDIENCE validés côté
configCORE_BASE_URL
configS3_ENDPOINT_URL
🔐 secretS3_ACCESS_KEY
🔐 secretS3_SECRET_KEY
configS3_THUMBNAILS_BUCKET
configS3_UPLOADS_BUCKET
configS3_EXPORTS_BUCKET
configS3_APPEXPORTS_BUCKET
configS3_TILESET3D_BUCKET
configS3_TERRAIN3D_BUCKET
configCDC_DATABASE_URL
configS3_CDC_BUCKET
configAPPEXPORT_STANDALONE_DATA_DIR
configAPPEXPORT_STANDALONE_RUNTIME_DIR
configCORE_INTERNAL_BASE_URL
configCORE_OIDC_JWKS_URL
configCORE_AUTH_MODELe mode mock (VITE_AUTH_MODE=mock, =mock) suffit pour le
configCORE_MCP_AUDIENCEdécalage entre et l'audience réellement émise par le
configOTEL_EXPORTER_OTLP_ENDPOINT
configOTEL_SERVICE_NAME
configCORE_TEST_DATABASE_URL
configCORE_ADMIN_SUBSliste de subs OIDC (séparés par des virgules)
configSPIKE_DATABASE_URL
configS3_CDC_BUCKET_BASE_URI
configAPPEXPORT_RUNTIME_DIR
configCORE_ENV
configCORE_READ_ONLY_MODE
configCORE_ETL_ENABLED
configCORE_EXPORT_ENABLED
configCORE_APPEXPORT_ENABLED
configCORE_TILESET3D_ENABLED
configCORE_TERRAIN3D_ENABLED
configCORE_LLM_PROVIDER
configCORE_ANALYST_SUBSmême mécanique, miroir de CORE_ADMIN_SUBS,
configCORE_OIDC_AUDIENCEcœur — CORE_OIDC_ISSUER/ validés côté
🔐 secretCORE_EXPORT_TOKEN_SECRET
configCORE_LLM_API_URL
🔐 secretCORE_LLM_API_KEY
configCORE_LLM_MODEL
configSHELL_BASE_URL
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployDATABASE_URL
// 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

25/25 tools missing one or more hints — addWidget (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); updateWidgetProps (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); removeWidget (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +22 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.

Secrets not logged

1 secret value sent to logger.info

Redact or omit secret values from log output.

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 3 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/tlenenao/geostudio)](https://m8ven.ai/mcp/tlenenao/geostudio)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: eabc452305f2f8a0542211f0533e3547f291e321
code hash: b47b3406da85652ac7bdd5e0936a1cae783e4d276caa3f89dd9e5a730ed3ef65
verified: 9/2/2026, 6:49:33 PM
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