D
Caution
42/100
11 days ago

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

Moos3p

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

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
⚠️
Known vulnerabilities in dependencies: 3 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
⚠️
Tests do not pass
Either the test suite is broken or the code regressed. Either way the published behaviour can’t be verified by the publisher’s own tests.
121 tools verified — handlers match their declared behaviour
7 read-only tools verified — handlers contain no write/delete/exec
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
// known CVEs in dependencies3 high

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

high@modelcontextprotocol/sdk@1.17.4GHSA-345p-7cg4-v4c7

@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse

high@modelcontextprotocol/sdk@1.17.4GHSA-8r9q-7v3j-jr4g

Anthropic's MCP TypeScript SDK has a ReDoS vulnerability

high@modelcontextprotocol/sdk@1.17.4GHSA-w48q-cv73-mx4w

Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default

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.
configGD3_ACTIVE_LOCAL_PROJECT_ROOT
configGD3_ACTIVE_MODE
configGD3_ACTIVE_SEASON
configGD3_ACTIVE_TID
configGD3_ALLOW_ORIGIN
configGD3_BUILD_LABEL
configGD3_CONTROLLING_SURFACE
configGD3_CREDENTIALS_FILE
configGD3_CURRENT_BLOCKERS
configGD3_CURRENT_WORKSTREAM
configGD3_DEBUG_LOGS
configGD3_DEEP_DEBUG_LOGS
configGD3_DEFAULT_SPREADSHEET_ID
configGD3_DRIVE_FILE_READ_MAX_BYTES
configGD3_DRIVE_FILE_WRITE_MAX_BYTES
configGD3_DRIVE_MIRROR_LABEL
configGD3_DRIVE_MIRROR_ROOT
configGD3_DRIVE_SEARCH_PAGE_SIZE
configGD3_ENABLE_DESTRUCTIVE_SHEET_OPS
configGD3_ENABLE_DRIVE_FILE_CREATE
configGD3_ENABLE_DRIVE_FILE_READ
configGD3_ENABLE_DRIVE_READ
configGD3_ENABLE_SCRIPT_EXECUTE
configGD3_ENABLE_SCRIPT_WRITES
configGD3_ENABLE_SHEET_WRITES
configGD3_HOME
configGD3_IDLE_SESSION_MS
configGD3_LEGACY_PATH_HINTS
configGD3_LOCAL_DISCOVERY_ROOTS
configGD3_LOCAL_FILE_READ_MAX_BYTES
configGD3_LOCAL_SEARCH_MAX_RESULTS
configGD3_MANAGED_DRIVE_FOLDER_ID
configGD3_MAX_SESSIONS_PER_CLIENT
configGD3_MCP_ENABLE_JSON_RESPONSE
configGD3_MCP_PATH
configGD3_NEXT_ADMISSIBLE_MOVE
configGD3_ORPHAN_INIT_TTL_MS
configGD3_PROJECT_ROOT
configGD3_RATINGS_SPREADSHEET_ID
configGD3_RELEASE_POSTURE
configGD3_REQUEST_BODY_LIMIT_BYTES
configGD3_RUNTIME_INSTANCE_ID
configGD3_RUNTIME_LINE
configGD3_RUNTIME_NAME
configGD3_SCRIPT_EXEC_VALIDATE_FUNCTION
configGD3_SCRIPT_ID
configGD3_SECRETS_DIR
configGD3_SESSION_SWEEP_MS
configGD3_SPREADSHEET_ID
configGD3_SYNC_CONFLICT_POLICY
configGD3_SYNC_ENABLED
configGD3_SYNC_LOG_PATH
configGD3_SYNC_MODE
configGD3_SYNC_STATE_PATH
configGD3_TOKEN_FILE
configGD3_TOPOLOGY_ROOT
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// quality suggestions

Tool annotations

9/121 tools have annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

119/121 tools missing one or more hints — get_project_control_status (missing: idempotentHint); gd3_list_local_roots (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); gd3_discover_local_files (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +116 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 inputs are validated

Only 47/121 tool handlers declare input schemas (39%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool handlers catch errors

Only 0/121 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 31/121 tools referenced in tests (26%)

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

Tests pass

npm test failed — tests do not pass

Make sure npm test runs cleanly. Common cause: missing build step or missing env vars.

Shell command execution

1 child_process call — runs shell commands

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

Production dependencies are patched

0 critical, 3 high severity in production deps — @modelcontextprotocol/sdk@1.17.4 (high), @modelcontextprotocol/sdk@1.17.4 (high)

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

Dependency freshness

1/5 production deps stale: @google-cloud/local-auth@2024-01-08 (2.6y)

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 9 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/moos3p-gd3-1pg8lu?variant=verified)](https://m8ven.ai/mcp/moos3p-gd3-1pg8lu)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: bd44c9a2cd9f20199a1bd95262ec665e26bf2411
code hash: 0312df45786eb01c7b86355d004a1e014bc83a4a9e17eaf638f449e8e5b5e5de
verified: 8/8/2026, 7:24:48 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