C
Emerging
74/100
2 days ago

vanth

Enables AI agents to launch, monitor, and manage background shell jobs with durable event tracking, live progress dashboards, and wake-on-attention for interactive sessions.

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

abhim-dv

Source: Glama

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
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.
// 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.
configVANTH_MAX_EVENT_BYTES64 KiB Single event payload cap
configAGENT_BG_MAX_EVENT_BYTES
configVANTH_MAX_EVENT_LINE_BYTES1 MiB AGENT_EVENT line cap
configVANTH_MAX_LOG_BYTES10 MiB Per-stream log cap (drain continues)
configVANTH_DELIVERY_LEASE_MARGIN5s Extra lease time beyond adapter timeout
configVANTH_RUNNER_HEARTBEAT_INTERVAL1s Runner liveness heartbeat
configVANTH_RUNNER_HEARTBEAT_STALE_AFTER10s Heartbeat staleness threshold
configVANTH_RECOVERY_KILL_TIMEOUT
configVANTH_DELIVERY_MAX_CONCURRENTare picked up on the next dispatch pass. Set
configVANTH_MAX_EVENTS_PER_JOB100000 Structured event cap per job
configVANTH_LOG_LEVELINFO Daemon log level
configVANTH_LOG_MAX_BYTES5 MiB Rotating daemon log size
configVANTH_LOG_BACKUP_COUNT3 Daemon log rotation count
configVANTH_DELIVERY_POLL_INTERVAL0.2s Maintenance loop cadence
configVANTH_SHUTDOWN_TIMEOUT
configCODEX_THREAD_ID
configVANTH_CODEX_BINcodex / C:\codex\codex.exe Codex binary
configVANTH_OPENCODE_BINopencode (via shutil.which) OpenCode binary
configVANTH_NO_SETUP_HINT
configPROCESSOR_ARCHITECTURE
configRERUN_MARK
configVANTH_HOME"vanth": { "command": "vanth", "env": { "": "C:/Users/you/.vanth" } }
configVANTH_SMOKE_TIMEOUT
configVANTH_SMOKE_CODEX_THREAD(set / VANTH_SMOKE_OPENCODE_SESSION);
configVANTH_SMOKE_OPENCODE_SESSION(set VANTH_SMOKE_CODEX_THREAD / );
configVANTH_DAEMON_HOST(127.0.0.1 / ::1 / localhost); a non-loopback is
configVANTH_DAEMON_PORT8765 Bind port
configVANTH_DAEMON_URL
configVANTH_MAX_RESPONSE_BYTES4 MiB HTTP response cap
configVANTH_MAX_REQUEST_BYTES1 MiB HTTP request body cap
configVANTH_BUSY_TIMEOUT_MS30000 SQLite write-lock wait
configVANTH_CACHE_DIR
configAGENT_BG_HOME(default %USERPROFILE%\.vanth on Windows, ~/.vanth on Unix;
// 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

21/21 tools missing one or more hints — job_start (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); job_rerun (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); job_status (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +18 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 test coverage

14/21 tools referenced in tests (67%)

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

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/abhim-dv-vanth-ooyjy1)](https://m8ven.ai/mcp/abhim-dv-vanth-ooyjy1)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: fabf0a26995d7368935a3d9f683335509eea611a
code hash: b4d85e58eab794798f75f0cdb1cbcd7c5de7f38eb54b96274f124f291387c350
verified: 8/19/2026, 9:17:54 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