gantry (knacklabs/gantry) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it: we have no way to read this server ourselves. No publisher has claimed this listing.

C
Emerging
74/100
20 days ago

gantry

Self-hosted, provider-neutral agent runtime for teams: governed tools and permissions, Slack/Telegram/Teams channels, scheduled jobs, memory, Node SDK and APIs, audit-first on Postgres.

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

knacklabs

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: 1 critical
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 10 credentials: GANTRY_ATTACHMENT_IPC_AUTH_TOKEN, GANTRY_BROWSER_IPC_AUTH_TOKEN, GANTRY_BROWSER_TURN_TOKEN, GANTRY_IPC_AUTH_TOKEN, GANTRY_IPC_RESPONSE_VERIFY_KEY, GANTRY_JOB_RUN_LEASE_TOKEN, GANTRY_LIVE_STOP_ACTION_TOKEN, GANTRY_MEMORY_IPC_AUTH_TOKEN, GANTRY_WORKSPACE_KEY, LINEAR_ISSUE_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies1 critical

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

criticalvitest@4.0.18GHSA-5xrq-8626-4rwp

When Vitest UI server is listening, arbitrary file can be read and executed

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.
configAGENT_MAX_OUTPUT_SIZE
configAGENT_TIMEOUT
configGANTRY_ADMIN_MCP_TOOLS_JSON
configGANTRY_AGENT_ACCESS_PRESET
configGANTRY_AGENT_ID
configGANTRY_AGENT_RUN_HANDLE
configGANTRY_APP_ID
configGANTRY_ASYNC_TASK_TOOLS_ENABLED
🔐 secretGANTRY_ATTACHMENT_IPC_AUTH_TOKEN
🔐 secretGANTRY_BROWSER_IPC_AUTH_TOKEN
configGANTRY_BROWSER_PROFILE_NAME
🔐 secretGANTRY_BROWSER_TURN_TOKEN
configGANTRY_CALLABLE_AGENT_MANIFEST_JSON
configGANTRY_CHAT_JID
configGANTRY_CONFIGURED_ALLOWED_TOOLS_JSON
configGANTRY_DEEPAGENTS_FILESYSTEM_ENABLED
configGANTRY_DEEPAGENTS_MAX_INPUT_TOKENS
configGANTRY_DEEPAGENTS_MODEL_ID
configGANTRY_DEEPAGENTS_MODEL_PROVIDER
configGANTRY_DEEPAGENTS_OPENROUTER_PROVIDER_ROUTING
configGANTRY_DEEPAGENTS_SHELL_ENABLED
configGANTRY_DEPLOYMENT_MODE
configGANTRY_GROUP_FOLDER
configGANTRY_HOMERuntime home defaults to ~/gantry unless or --runtime-home is
🔐 secretGANTRY_IPC_AUTH_TOKEN
configGANTRY_IPC_RESPONSE_KEY_ID
🔐 secretGANTRY_IPC_RESPONSE_VERIFY_KEY
configGANTRY_JOB_ID
configGANTRY_JOB_RUN_ID
configGANTRY_JOB_RUN_LEASE_FENCING_VERSION
🔐 secretGANTRY_JOB_RUN_LEASE_TOKEN
🔐 secretGANTRY_LIVE_STOP_ACTION_TOKEN
configGANTRY_MCP_CONFIG_FILE
configGANTRY_MCP_SERVERS_JSON
configGANTRY_MCP_SERVER_PATH
configGANTRY_MCP_TOOL_NAMES_JSON
configGANTRY_MEMORY_DEFAULT_SCOPE
configGANTRY_MEMORY_IPC_ACTIONS_JSON
🔐 secretGANTRY_MEMORY_IPC_AUTH_TOKEN
configGANTRY_MEMORY_REVIEWER_IS_CONTROL_APPROVER
configGANTRY_MEMORY_USER_ID
configGANTRY_MODEL_INPUT_MODALITIES
configGANTRY_NO_PERMISSION_TOOLS
configGANTRY_PARENT_TASK_ID
configGANTRY_PERMISSION_LANE
configGANTRY_PROVIDER_ACCOUNT_ID
configGANTRY_RUNNER_LOG
configGANTRY_RUN_ID
configGANTRY_SELECTED_MCP_SERVERS_JSON
configGANTRY_SELECTED_SKILLS_JSON
configGANTRY_SELECTED_SKILL_DISPLAYS_JSON
configGANTRY_SEMANTIC_CAPABILITIES_JSON
configGANTRY_THREAD_ID
🔐 secretGANTRY_WORKSPACE_KEY
configIDLE_TIMEOUT
configMAX_MESSAGES_PER_PROMPT
configMESSAGE_FETCH_PAGE_SIZE
configGANTRY_RUNTIME_IMAGES
🔐 secretLINEAR_ISSUE_KEY
configMSYSTEM
configSHELL
// quality suggestions

Dependencies

51 dependencies, 1 flagged: playwright-core

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

76/76 tools missing one or more hints — mcp_list_tools (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); mcp_search_tools (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); mcp_describe_tool (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +73 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

52/75 tool handlers declare input schemas (69%)

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

Tool handlers catch errors

Only 1/75 tool handlers wrap calls in try/catch (1%)

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

Tool test coverage

Only 4/76 tools referenced in tests (5%)

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

Shell command execution

12 child_process calls — runs shell commands

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

Dev dependencies

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

Upgrade dev dependencies when convenient.

Domain consistency

npm scope @gantry doesn't match GitHub owner knacklabs

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 8 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/knacklabs-gantry-1e391i)](https://m8ven.ai/mcp/knacklabs-gantry-1e391i)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 9f3043a312b2a07d7b19ed19b41d09f8e2d950f6
code hash: 30df41212af9f229159b9a85e4fa80262a60d6b826d74c9863f97373fdccd4b9
verified: 8/8/2026, 7:24:00 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