mcp-data-server (boettiger-lab/mcp-data-server) is an MCP server listed on the M8ven Trust Index. It scores 73 out of 100, grade C. It declares 4 tools. No publisher has claimed this listing.

C
Limited view
73/100

mcp-data-server

Duckdb-based MCP server for datasets

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

boettiger-lab

Source: Glama · also listed on github_repo_search

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 1 credential: MCP_AUTH_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.
configAPP_VERSION
configGIT_SHA
configMCP_QUERY_CONCURRENCY
configHOSTNAME
configTILE_BUILD_MAX_CONCURRENCY
configTILE_BUILD_INLINE_WAIT_SECONDS
configTILE_BUILD_THREADS
configTILE_LOCK_HEARTBEAT_SECONDS
🔐 secretMCP_AUTH_TOKEN
configSTAC_ALLOW_DEGRADED_START
configDUCKDB_MEMORY_LIMIT
configPOD_MEMORY_LIMIT
configS3_DEFAULT_ENDPOINT
configS3_DEFAULT_URL_STYLE
configS3_DEFAULT_USE_SSL
configS3_ENDPOINT_URL
configS3_SOURCES
configSTAC_PUBLIC_CATALOG_URL
configSTAC_ROOT_TIMEOUT
configSTAC_TIMEOUT
configSTAC_CHILD_TIMEOUT
configSTAC_FETCH_CONCURRENCY
configSTAC_CHILD_RETRY_TIMEOUT
configSTAC_REFRESH_INTERVAL
configMRE_GLOB
configMRE_THREADS
configMRE_MEM
configMRE_ENDPOINT
configMRE_BUCKET
configMRE_PREFIX
configMRE_FANOUT
configMRE_SSL
configMRE_N
configMRE_BOTO_CONC
configMRE_CONC
configMRE_CONCURRENCY
configMRE_OBJS_PER_LEVEL
configMRE_N_LATENCY
configMRE_FOOTER_BYTES
configMRE_ENDPOINTS
configPOD_NAME
configMRE_DATASET
configMRE_COLUMN
configMRE_N_STREAM
configMRE_AGG_OBJS
configMRE_AGG_CONC
configTILE_THREADS
configTILE_BUCKET_BASE
configTILE_TARGET_CELLS_PER_TILE
configTILE_LOCK_STALE_SECONDS
configMCP_PUBLIC_BASE_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

4/4 tools missing one or more hints — browse_stac_catalog (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_stac_details (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_collection (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +1 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/3 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/boettiger-lab/mcp-data-server)](https://m8ven.ai/mcp/boettiger-lab/mcp-data-server)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 96d0d91744e1f9df9a828a9d1e3743137425bd15
code hash: 7b3f6d8db4b106b3093ea508c301f6ad0962882c6cb9a143cfa0977e9a1ae33c
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